FTL not starting

Help docker
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

DNS to start and block ads

Actual Behaviour:

Worked fine for 2 weeks then FTL randomly stopped working. No server reboot or service resets had been performed. /etc/resolv.conf only has 1.1.1.1 and is locked via "sudo chattr +i /etc/resolv.conf"
Lubuntu 18.10 via Docker image: pihole/pihole:latest

Debug Token:

bn5bgcxxkg

2

Do these notes help with the situation?

3

Yes it's now up BUT after the config changes I'm seeing:

WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server,
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11),

And for every list:

[i] Target: mirror1.malwaredomains.com (justdomains),
  [i] Status: Pending...
  [✗] Status: mirror1.malwaredomains.com is blocked by https://v.firebog.net/hosts/lists.php?type=nocross. Using DNS on 192.231.203.132 to download https://mirror1.malwaredomains.com/files/justdomains,
  [i] Status: Pending...
  [✓] Status: No changes detected,
,
  [i] Target: sysctl.org (hosts),
  [i] Status: Pending...
  [✗] Status: sysctl.org is blocked by https://v.firebog.net/hosts/lists.php?type=nocross. Using DNS on 192.231.203.132 to download http://sysctl.org/cameleon/hosts,
  [i] Status: Pending...
  [✓] Status: No changes detected,
,
  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist),
  [i] Status: Pending...
  [✗] Status: zeustracker.abuse.ch is blocked by https://v.firebog.net/hosts/lists.php?type=nocross. Using DNS on 192.231.203.132 to download https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist,
  [i] Status: Pending...
  [✗] Status: https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist (500000),
  [✗] List download failed: using previously cached list,
,
  [i] Target: s3.amazonaws.com (simple_tracking.txt),
  [i] Status: Pending...
  [✓] Status: No changes detected,

etc.

EDIT: changes added to docker-compose.yml:

cap_add:
  - NET_ADMIN
dns:
  - 127.0.0.1
  - 1.1.1.1
4

With the file chattr'd it will not be updated with the two dns lines or the cli command shown in the readme.

5

I locked it as network-manager would auto edit the file.
After unlock I still receive the same errors, even if I manually add 1.1.1.1 and 127.0.0.1.

6

Thanks, @diginc, can you help me out on this?

7

Note, I locked the host Lubuntu OS /etc/resolv.conf, not the one located within the docker image.
Looking at the complaint, it actually looks like it's the docker image /etc/resolv.conf that's the issue:

root@pihole:/# cat /etc/resolv.conf
nameserver 127.0.0.11
options ndots:0

Not sure what to do about this file.

8 
dns:
  - 127.0.0.1
  - 1.1.1.1

Adding these should modify your /etc/resolv.conf inside the container assuming you're not using --net=host.

Check with docker run pihole cat /etc/resolv.conf

9

I've removed container and image and then redownloaded the docker image with no change. I'm not using net=host.

10

A small update that if I swap the DNS lines around the list updates now work, but the WARNINGS still occur.

cap_add:
  - NET_ADMIN
dns:
  - 1.1.1.1
  - 127.0.0.1

WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server
WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11)
nameserver 127.0.0.11
options ndots:0

So yeah, Pihole isn't configuring the container's /etc/resolv.conf

EDIT: New debug if interested: 2z244wxvgd

11

That's been done (see above and below), but errors still remain.

12