From a8e1746476b98d361fd9dc7a5f997e91814186cb Mon Sep 17 00:00:00 2001 From: Adam Hill Date: Sun, 13 Jan 2019 13:02:12 -0600 Subject: [PATCH] FTLDNS Signed-off-by: Adam Hill --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1e4046123..a92127afa 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Starting with the v4.1.1 release your Pi-hole container may encounter issues starting the DNS service unless ran with the following settings: - `--cap-add=NET_ADMIN` This previously optional argument is now required or strongly encouraged - - Starting in a future version FTL DNS is going to check this setting automatically + - Starting in a future version FTLDNS is going to check this setting automatically - `--dns=127.0.0.1 --dns=1.1.1.1` The second server can be any DNS IP of your choosing, but the **first dns must be 127.0.0.1** - A WARNING stating "Misconfigured DNS in /etc/resolv.conf" may show in docker logs without this. @@ -104,7 +104,7 @@ Here is a rundown of the other arguments passed into the example `docker run`: | `-v /dir/for/pihole:/etc/pihole`
**Recommended** | Volumes for your Pi-hole configs help persist changes across docker image updates | `-v /dir/for/dnsmasq.d:/etc/dnsmasq.d`
**Recommended** | Volumes for your dnsmasq configs help persist changes across docker image updates | `--net=host`
*Optional* | Alternative to `-p :` arguments (Cannot be used at same time as -p) if you don't run any other web application. DHCP runs best with --net=host, otherwise your router must support dhcp-relay settings. -| `--cap-add=NET_ADMIN`
*Required* | FTL DNS will fail to start without this setting +| `--cap-add=NET_ADMIN`
*Required* | FTLDNS will fail to start without this setting | `--dns=127.0.0.1`
*Recommended* | Sets your container's resolve settings to localhost so it can resolve DHCP hostnames from Pi-hole's DNSMasq | `--dns=1.1.1.1`
*Optional* | Sets a backup server of your choosing in case DNSMasq has problems starting