From 6e38238dc1ce761f5331d69ce0c59a6fc864cfc4 Mon Sep 17 00:00:00 2001 From: Warren Fisher <40742485+warren-fisher@users.noreply.github.com> Date: Fri, 15 Nov 2019 12:11:49 -0400 Subject: [PATCH] Add to Ubuntu install section Add info about restarting systemd-resolved Signed-off-by: Warren Fisher Add to Ubuntu install section Signed-off-by: Warren Fisher --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 1b1b8a4..12490e7 100644 --- a/README.md +++ b/README.md @@ -151,6 +151,7 @@ The stub resolver should be disabled with: `sudo sed -r -i.orig 's/#?DNSStubList This will not change the nameserver settings, which point to the stub resolver thus preventing DNS resolution. Change the `/etc/resolv.conf` symlink to point to `/run/systemd/resolve/resolv.conf`, which is automatically updated to follow the system's [`netplan`](https://netplan.io/): `sudo sh -c 'rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf'` +After making these changes, you should restart systemd-resolved using `systemctl restart systemd-resolved` Once pi-hole is installed, you'll want to configure your clients to use it ([see here](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245)). If you used the symlink above, your docker host will either use whatever is served by DHCP, or whatever static setting you've configured. If you want to explicitly set your docker host's nameservers you can edit the netplan(s) found at `/etc/netplan`, then run `sudo netplan apply`. Example netplan: