Pi-hole works for 2-3 minutes then becomes unreachable until stopping & restarting docker container

Help Synology
,
1

Container launches, I can access the admin page and it showed queries begin blocked. Within 5 minutes, the web access stops working..."Unable to connect, Firefox can't establish a connection at x.x.x.x

If I stop, then restart the container the admin page becomes accessible again for only a few minutes.

Any suggestions on what may cause this?

Debug token: https://tricorder.pi-hole.net/n8kg3QhK/

2

How did you start the container? Did you use a docker run command? A compose file?

Please, post your compose file or command used to start the container.

3

I use docker on a Synology so I click the toggle to start the container. I don't know what a compose file is. I don't type any commands.

4

Your debug log shows your Pi-hole is aware of two network interfaces, both of which are operational for DNS:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain

[✓] www.propergrass.com is 0.0.0.0 on eth0 (192.168.1.198)
[✓] www.propergrass.com is 0.0.0.0 on eth1 (192.168.10.2)

However, your DHCP server is dishing out three IPv4 addresses as DNS servers:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   
   * Received 322 bytes from eth0:192.168.1.1
     Offered IP address: 192.168.1.181
     DHCP options:
      Message type: DHCPOFFER (2)
      router: 192.168.1.1
      dns-server: 192.168.1.30
      dns-server: 1.1.1.1
      dns-server: 8.8.8.8

Two of those IPs belong to public DNS resolvers, allowing clients to by-pass Pi-hole at their discretion. And what device is listening on 192.168.1.30?

Pi-hole has to be the sole DNS server for your network.

Currently, none of those DNS server addresses matches any of your Pi-hole host's IPs.

6

Thank you for pointing this out. I have updated the 192.x.x.30 to the address assigned to the pi-hole container 192.x.x.198.

If I remove the two public DNS servers and my container doesn't work then my whole network loses connectivity. I thought the public servers were used as backup in the event the primary goes down.

Even with the DNS pointing to the container, I am able to start it, then access the admin panel for no more than 1 minute. After 1 minute the server returns an "unreachable" error until I stop then restart it again (via the docker GUI).