Pi Hole does not receive any queries

Expected Behaviour:

PiHole should get queries and block ads

Actual Behaviour:

Web-dashboard is working fine but my PiHole doesnt get any queries.


  • ssh with putty
  • dietpi
  • Raspberry Pi 3b+

What I already tried:

  • I restarted my clients
  • I rebooted the raspberry-pi
  • i specifically ping the my raspberry pi
  • set my windows prefered dns to the raspberry pi's ip-adress
  • set my Routers prefered dns to the raspberry pi's ip-adress
  • the Pi has a static IP adress
  • having no clue what the heck im doing

Debug Token:

i replaced the at symbol with (at)

debug log removed by moderator and made private

We ask that you post the debug token only. This keeps your debug log private - only the Pi-hole team can access the log at the URL you provide and it auto-expires in 48 hours.

Your DHCP server is passing out the IP of itself for DNS, rather than the Pi-hole IP:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   * Received 356 bytes from eth0:
     Offered IP address:
     Server IP address: N/A
     Relay-agent IP address: N/A
     BOOTP server: Speedport-Pro-Plus/120141.
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      lease-time: 1814400 ( 21d )
      renewal-time: 907200 ( 10d 12h )
      rebinding-time: 1587600 ( 18d 9h )
         domain-name: "speedport.ip"
      --- end of options ---
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0: 1

Your P-hole is configured at a different IP:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] info.my-chatprogram.xyz is on lo (
[✓] info.my-chatprogram.xyz is on eth0 (
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (

From a client that you believe should be connected to the Pi-Hole for DNS (the PC in this case), from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

nslookup flurry.com

Are you running any firewall software that would be blocking port 53 traffic? Something is preventing the Pi from connecting to the Google DNS server and to our nameserver:

*** [ DIAGNOSING ]: Operating system
[i] dig return code:  10
[i] dig response:  dig: couldn't get address for 'ns1.pi-hole.net': failure

The Pi nameserver is also set to the router IP. I recommend that you change this to any public DNS like Cloudflare, Quad9, Google, etc. This allows the device to continue to reach the internet in the case of a problem like you are having now.

-rw-r--r-- 1 root root 63 Aug  3 18:16 /etc/resolv.conf
   domain speedport.ip
   search speedport.ip