DNS Resolution Failures on 5.2.4

Help
1

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the [Community Help] category.

Expected Behaviour:

DNS Resolution occurs quickly.

Actual Behaviour:

Getting unresolved DNS issues on all devices. Even for simple requests like Google or things definitely not a block list.

Debug Token:

tricorder.pi-hole.net/uy6mdnwro1

BTW it wouldn't let me submit this because it said I couldn't submit more that 5 links as a new user. Realized this is stemming from your template. I had only provided 1 link via debug token.

2

Please provide some examples from your log at /var/log/pihole.log.

3

Your debug log indicates your router's DHCP server isn't distributing Pi-hole's, but rather its own IP address as local DNS server:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   
   * Received 548 bytes from eth0:192.168.1.1
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.1.1
      router: 192.168.1.1
      dns-server: 192.168.1.1
      --- end of options --

Accordingly, Pi-hole doesn't seem to have received any DNS traffic so far:

*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 10520 Apr 12 16:31 /var/log/pihole-FTL.log
   -----tail of pihole-FTL.log------
   [2021-04-12 16:15:05.672 1384M] Imported 0 queries from the long-term database
   [2021-04-12 16:15:05.672 1384M]  -> Total DNS queries: 0
   [2021-04-12 16:15:05.672 1384M]  -> Cached DNS queries: 0
   [2021-04-12 16:15:05.672 1384M]  -> Forwarded DNS queries: 0
   [2021-04-12 16:15:05.672 1384M]  -> Blocked DNS queries: 0
   [2021-04-12 16:15:05.672 1384M]  -> Unknown DNS queries: 0
   [2021-04-12 16:15:05.672 1384M]  -> Unique domains: 0
   [2021-04-12 16:15:05.672 1384M]  -> Unique clients: 0
   [2021-04-12 16:15:05.672 1384M]  -> Known forward destinations: 0
4

That's my fault on the logs. I reconfigured the raspberry Pi based on other user suggestions on forums. However, because of the issues since upgrading, I can't really leave it as the DHCP source for long.

5

Does that mean you no longer observe the issue?

If you still do, please provide a debug token where Pi-hole is actually receiving DNS; and also please comply with jfb's request for log file samples for failing domain resolutions.

6

No it means that it doesnt work. So I can leave it as the DNS resource for the house very long I need to wait until the evening when no one is working.

7

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.