diff --git a/dnsmasq/readme.md b/dnsmasq/readme.md
index 85fbd00..b69f873 100644
--- a/dnsmasq/readme.md
+++ b/dnsmasq/readme.md
@@ -14,13 +14,13 @@ Lightweight DHCP and DNS server.
dnsmasq solves the problem of accessing self hosted stuff when you are inside
your network. As asking google's DNS for `example.com` will return your
very own public IP and most routers/firewalls wont allow this loopback,
-where your requests should go out and then right back.
+where your requests should go out and then right back.
Usual quick way to solve this issue is
[editing the `hosts` file](
https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/caddy_v2#--editing-hosts-file)
on your machine, adding `192.168.1.222 example.com` IP-hostname pair.
This tells your machine to fuck asking google's DNS, the rule is right there,
-`example.com` goes directly to the local server ip `192.168.1.222`.
+`example.com` goes directly to the local server ip `192.168.1.222`.
But if more devices should "just work" it is a no-go, since this just works
one the machine which `hosts` file was edited.
@@ -28,7 +28,7 @@ So the answer is running a DNS server that does this
paring of IPs with hostnames, and a DHCP server that tells the devices
on the network to use this DNS.
-*extra info*
+*extra info*
DNS servers run on port 53.
# Prerequisites
@@ -50,7 +50,7 @@ DNS servers run on port 53.
* `hosts` - a file that can provide additional hostname-ip mapping
`hosts` and `resolve.conf` are just normal system files always in use on any linux
-system.
+system.
`dnsmasq.conf` comes with the dnsmasq installation.
# Installation
@@ -111,15 +111,15 @@ dhcp-host=08:00:27:68:f9:bf,192.168.1.150
* `dnsmasq --help dhcp` - lists all the DHCP options
You can also run **just DNS server**, by deleting the DHCP section
-in the `dnsmasq.conf` to the end.
+in the `dnsmasq.conf` to the end.
Then on your router, in the DHCP>DNS settings, you just put in the ip address
of the dnsmasq host as the DNS server.
# resolv.conf
-A file that contains DNS nameservers to be used by the linux machine it sits on.
+A file that contains DNS nameservers to be used by the linux machine it sits on.
Since dnsmasq, a DNS server, is running right on this machine,
-the entries just point to localhost.
+the entries just point to localhost.
`resolv.conf`
```
@@ -129,16 +129,16 @@ nameserver 127.0.0.1
Bit of an issue is that `resolv.conf` belongs to glibc, a core linux library.
But there are other network related services that like to fuck with it.
-Like dhcpcd, networkmanager, systemd-resolved,...
+Like dhcpcd, networkmanager, systemd-resolved,...
Ideally you know what is running on your host linux system, but just in case
`resolv.conf` will be flagged as immutable.
This prevents all possible changes to it unless the attribute is removed.
Edit `/etc/resolv.conf` and set localhost as the DNS nameserver, as shown above.
-* Make it immutable to prevent any changes to it.
+* Make it immutable to prevent any changes to it.
`sudo chattr +i /etc/resolv.conf`
-* Check if the content is what was set.
+* Check if the content is what was set.
`cat /etc/resolv.conf`
# /etc/hosts
@@ -155,11 +155,11 @@ Edit `/etc/resolv.conf` and set localhost as the DNS nameserver, as shown above.
```
This is a file present on every system, linux, windows, mac, android,...
-where you can assign a hostname to an IP.
+where you can assign a hostname to an IP.
dnsmasq reads `/etc/hosts` for IP hostname pairs and adds them to its own
resolve records.
-Unfortunately no wildcard support.
+Unfortunately no wildcard support.
But as seen in the `dnsmasq.conf`, when domain is set it acts as a wildcard
rule. So `example.com` stuff here is just for show.
@@ -167,11 +167,11 @@ rule. So `example.com` stuff here is just for show.
`sudo systemctl enable --now dnsmasq`
-* Check if it started without errors
+* Check if it started without errors
`journalctl -u dnsmasq.service`
-* If you get "port already in use" error, check which service is using port 53
- `sudo ss -tulwnp`
- stop and disable that service, for example if it is `systemd-resolved`
+* If you get "port already in use" error, check which service is using port 53
+ `sudo ss -tulwnp`
+ stop and disable that service, for example if it is `systemd-resolved`
`sudo systemctl disable --now systemd-resolved`
* Make sure you **disable other DHCP servers** on the network,
usually a router is running one.
@@ -180,7 +180,7 @@ rule. So `example.com` stuff here is just for show.
#### DHCP
-Set some machine on the network to use DHCP for its network setting.
+Set some machine on the network to use DHCP for its network setting.
Network connection should just work with full connectivity.
You can check on the dnsmasq host, file `/var/lib/misc/dnsmasq.leases`
@@ -200,18 +200,18 @@ but also available on windows.
### Troubleshooting
-* **ping fails from windows when using hostname**
- windows ping does not do dns lookup when just plain hostname is used
- `ping meh-pc`
+* **ping fails from windows when using hostname**
+ windows ping does not do dns lookup when just plain hostname is used
+ `ping meh-pc`
it's a [quirk](https://superuser.com/questions/495759/why-is-ping-unable-to-resolve-a-name-when-nslookup-works-fine/1257512#1257512)
of windows ping utility.
Can be solved by adding dot, which makes it look like domain name and this
- forces the dns lookup before pinging
- `ping meh-pc.`
+ forces the dns lookup before pinging
+ `ping meh-pc.`
-* **slow ping of a hostname, but fast nslookup on a linux machine**
- for me it was `systemd-resolved` running on the machine I was doing ping from.
- It can be stopped and disabled.
+* **slow ping of a hostname, but fast nslookup on a linux machine**
+ for me it was `systemd-resolved` running on the machine I was doing ping from.
+ It can be stopped and disabled.
`sudo systemctl disable --now systemd-resolved`
# Update