selfhosted
/
selfhosted-apps-docker
mirror of https://github.com/DoTheEvo/selfhosted-apps-docker.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

update

This commit is contained in:
DoTheEvolution 2020-06-13 18:51:23 +02:00
parent 8362d15383
commit 28be709f53
1 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
dnsmasq/readme.md
View File

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