Pi-hole not working network-wide

Help
1

I tried to search for similar issues but none helped me

Expected Behaviour:

Pi-hole should work network-wide as I configured it as the one and only DNS on my router

Actual Behaviour:

On the web interface none of the devices use my raspberry pi as DNS
I tried flushing dns, rebooting devices, pi, router, nothing seems to work

Debug Token:

https://tricorder.pi-hole.net/9u9p0ma0hv

2

Check all your PI Settings, Like the interfaces its listening to and its internet connectivity

3

Pi it's connected with ethernet cable, it's also connected through wifi but IDK, I've never had any problem with this. I have 4 telegram bots online 24/7 and they have no connection issues
I configured the ethernet interface with a static IP addres from the router so it's fixed 192.168.1.5
On the admin console of pi-hole I have "listen only on eth0"

4

Your debug log shows the following activity in the past 24 hours - some DNS traffic is reaching the Pi-hole.

   [2020-04-27 10:53:38.073 5838] Imported 2156 queries from the long-term database
   [2020-04-27 10:53:38.073 5838]  -> Total DNS queries: 2156
   [2020-04-27 10:53:38.073 5838]  -> Cached DNS queries: 303
   [2020-04-27 10:53:38.073 5838]  -> Forwarded DNS queries: 1718
   [2020-04-27 10:53:38.073 5838]  -> Exactly blocked DNS queries: 135
   [2020-04-27 10:53:38.073 5838]  -> Unknown DNS queries: 0
   [2020-04-27 10:53:38.073 5838]  -> Unique domains: 436
   [2020-04-27 10:53:38.073 5838]  -> Unique clients: 3
   [2020-04-27 10:53:38.073 5838]  -> Known forward destinations: 5

Run this command from the Pi terminal.

echo ">top-clients withzero (50) >quit" | nc localhost 4711

If there are devices in the list that show zero requests, then on one of those devices (from either the terminal or command prompt on that device), run and post the output of the following commands:

nslookup pi.hole

nslookup pi.hole 192.168.1.5

5

this is the result of the first command
of course I cannot execute the other two as there are no other devices

0 1957 192.168.1.1 fritz.box
1 424 127.0.0.1 localhost
2 2 192.168.1.5 raspberrypi
6

There are other devices on your network, but due to the way the FritzBox is serving DNS, all the queries from those clients appear to originate at the Fritzbox.

The other clients on your network are showing in the network table, but don't show as using Pi-hole because their DNS traffic is routed through the Fritzbox.

Just as a check, on a client on the network which is shown in the network table as not using Pi-hole, run the two nslookup commands to determine whether Pi-hole is answering the DNS queries.

7

well, this is the result of the two commands from my pc

C:\Users\erics>nslookup pi.hole
Server:  fritz.box
Address:  192.168.1.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Tempo scaduto per la richiesta a fritz.box

C:\Users\erics>nslookup pi.hole 192.168.1.5
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.5

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Tempo scaduto per la richiesta a UnKnown

C:\Users\erics>

I also have enabled conditional forwarding with domain name fritz.box and IP 192.168.1.1

8

From the same PC, what is the output of:

ipconfig /all

9

I report the only network interface that is actually connected, so I only translate one thing, tell me if you need anything else

Wi-Fi interafce 2:

   DNS Suffix specific for the connection: fritz.box
   Description . . . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205
   Physical Address. . . . . . . . . . . : **my mac address**
   DHCP enabled. . . . . . . . . . . . : Yes
   Automatic configuration enabled: Yes
   IPv6 local address. : fe80::9cbe:82d3:e599:c7e2%4(preferential)
   IPv4 address. . . . . . . . . . . . : 192.168.1.18(preferential)
   Subnet mask . . . . . . . . . . . . . : 255.255.255.0
   Lease obtained. . . . . . . . . . . . : monday 27 april 2020 12:09:37
   Lease expiring. . . . . . . . . . .  : thursday 7 may 2020 15:08:55
   Default Gateway . . . . . . . . . : 192.168.1.1
   Server DHCP . . . . . . . . . . . . . : 192.168.1.1
   IAID DHCPv6 . . . . . . . . . . . : 856166806
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-22-7B-A8-93-60-EB-69-83-18-D0
   Server DNS . . . . . . . . . . . . .  : 192.168.1.1
   NetBIOS over TCP/IP . . . . . . . . . . : Enabled
10

Manually map this client to use Pi-hole DNS (and not the DNS assigned from the router). This should take the router out of the DNS process.

Clear the DNS cache on that client with ipconfig /flushdns, then rerun nslookup pi.hole

11

still

C:\Users\erics>nslookup pi.hole
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.5

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Tempo scaduto per la richiesta a UnKnown
14

Let's see if the client can reach any DNS resolver. Run the following from the client:

nslookup pi-hole.net 1.1.1.1

15 
Server:  one.one.one.one
Address:  1.1.1.1

Reply from non authoritative server:
Name:    pi-hole.net
Addresses:  2604:a880:400:d0::1071:1
          206.189.252.21
16

It appears that something on your network is interfering with port 53 traffic flow.

Try without conditional forwarding enabled, as a first step.

17

still give request timed out

18

Please provide a new debug token.

19

https://tricorder.pi-hole.net/ii8ndc3fv5

20

Your debug log shows some irregularities.

Is 192.168.1.1 indeed your gateway, i.e. commonly your router? (click for details) 
*** [ DIAGNOSING ]: Networking
[i] Default IPv4 gateway: 192.168.1.1
   * Pinging 192.168.1.1
[✗] Gateway did not respond.
Your Pi-hole's actual upstream servers are contradicting your configuration. (click for details) 
*** [ DIAGNOSING ]: Setup variables
    PIHOLE_DNS_1=1.1.1.1
    PIHOLE_DNS_2=1.0.0.1
    CONDITIONAL_FORWARDING=false

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
/etc/dnsmasq.d/01-pihole.conf
   server=1.1.1.1
   server=1.0.0.1

*** [ DIAGNOSING ]: contents of /var/log
-----tail of pihole-FTL.log------
   New forward server: 1.0.0.1 (0/512)
   New forward server: 1.1.1.1 (1/512)
   New forward server: 192.168.1.1 (2/512)
   New forward server: 8.8.4.4 (3/512)
   New forward server: 8.8.8.8 (4/512)

Let's take a closer look at your configuration.
What's the output of

grep -vR '^[[:blank:]]*#\|^[[:blank:]]*$' /etc/dnsmasq.d/
21 
pi@raspberrypi:~ $ grep -vR '^[[:blank:]]*#\|^[[:blank:]]*$' /etc/dnsmasq.d/
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/gravity.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/black.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:log-queries
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:server=1.1.1.1
/etc/dnsmasq.d/01-pihole.conf:server=1.0.0.1
/etc/dnsmasq.d/01-pihole.conf:domain-needed
/etc/dnsmasq.d/01-pihole.conf:bogus-priv
/etc/dnsmasq.d/01-pihole.conf:interface=eth0
/etc/dnsmasq.d/01-pihole.conf:server=/use-application-dns.net/
22

I'd suspected some backup files to contain the stray DNS servers, but that doesn't seem to be the case.

Edit: There is one more file to check that Pi-hole would never write to.
What's in

cat /etc/dnsmasq.conf

Did you configure the following DNS servers somewhere?
Did you perhaps only recently remove them?

 New forward server: 192.168.1.1 (2/512)
 New forward server: 8.8.4.4 (3/512)
 New forward server: 8.8.8.8 (4/512)