PiHole can't resolve DNS for itself

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

Expected Behaviour:

PiHole is able to update itself, get blacklists/whitelists/etc. Instead, it is unable to resolve any DNS requests.

Actual Behaviour:

Can ping 8.8.8.8. Cannot ping google.com or GitHub, etc.

Debug Token:

I can't send the debug token, but I have generated a debug log in the web interface. If there's someone I can send it to (or I can upload it here). From looking at the results, dnsmasq is inactive. I've tried to get it to run, but no dice…

This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations.  This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected.  Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2019-05-02:03:38:47 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.0-0-gddbdb51

*** [ DIAGNOSING ]: Web version
[i] Web: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.0-0-gaf8c926

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.2.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)

*** [ DIAGNOSING ]: dnsmasq version
[i] 340:

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45

*** [ DIAGNOSING ]: php version
[i] 7.0.30

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[✓] armv7l

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.0.19/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
   2601:646:3:d40:c71f:ddd9:52fc:3016 matches the IP found in /etc/pihole/setupVars.conf
   fe80::4029:ad3d:ab3f:a318 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.0.1
   * Pinging 192.168.0.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: fe80::ce40:d0ff:fe25:2ac2
   * Pinging fe80::ce40:d0ff:fe25:2ac2...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)
*:53 pihole-FTL (IPv4)
*:53 pihole-FTL (IPv6)
127.0.0.1:4711 pihole-FTL (IPv4)
[::1]:4711 pihole-FTL (IPv6)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  via localhost (127.0.0.1)
[✗] Failed to resolve  via Pi-hole (192.168.0.19)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  via localhost (::1)
[✗] Failed to resolve  via Pi-hole (2601:646:3:d40:c71f:ddd9:52fc:3016)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is inactive
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.0.19/24
    IPV6_ADDRESS=2601:646:3:d40:c71f:ddd9:52fc:3016
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    PIHOLE_DNS_1=1.1.1.1
    PIHOLE_DNS_2=1.0.0.1
    PIHOLE_DNS_3=2606:4700:4700::1111
    PIHOLE_DNS_4=2606:4700:4700::1001
    DNS_FQDN_REQUIRED=false
    DNS_BOGUS_PRIV=false
    DNSSEC=true
    CONDITIONAL_FORWARDING=false
    DNSMASQ_LISTENING=local

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Thu, 02 May 2019 03:41:59 GMT
Server: lighttpd/1.4.45

[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 0 May  2 02:35 /etc/pihole/gravity.list
   -----head of gravity.list------

   -----tail of gravity.list------

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 381 May  2 03:31 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt

-rw-r--r-- 1 root root 0 May  2 02:34 /etc/pihole/blacklist.txt

-rw-r--r-- 1 root root 136 May  2 02:35 /etc/pihole/local.list
   192.168.0.19 raspberrypi
   2601:646:3:d40:c71f:ddd9:52fc:3016 raspberrypi
   192.168.0.19 pi.hole
   2601:646:3:d40:c71f:ddd9:52fc:3016 pi.hole

-rw-r--r-- 1 root root 234 May  2 03:32 /etc/pihole/logrotate
   /var/log/pihole.log {
   	su root root
   	daily
   	copytruncate
   	rotate 5
   	compress
   	delaycompress
   	notifempty
   	nomail
   }
   /var/log/pihole-FTL.log {
   	su root root
   	weekly
   	copytruncate
   	rotate 3
   	compress
   	delaycompress
   	notifempty
   	nomail
   }

-rw-r--r-- 1 root root 37 May  2 02:35 /etc/pihole/whitelist.txt
   github.com
   raw.githubusercontent.com

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1533 May  2 03:32 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/gravity.list
   addn-hosts=/etc/pihole/black.list
   addn-hosts=/etc/pihole/local.list
   domain-needed
   localise-queries
   bogus-priv
   no-resolv
   server=1.1.1.1
   server=1.0.0.1
   interface=eth0
   cache-size=10000
   log-queries=extra
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3027 May  2 03:32 /etc/lighttpd/lighttpd.conf
   server.modules = (
   	"mod_access",
   	"mod_accesslog",
   	"mod_auth",
   	"mod_expire",
   	"mod_compress",
   	"mod_redirect",
   	"mod_setenv",
   	"mod_rewrite"
   )
   server.document-root        = "/var/www/html"
   server.error-handler-404    = "pihole/index.php"
   server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
   server.errorlog             = "/var/log/lighttpd/error.log"
   server.pid-file             = "/var/run/lighttpd.pid"
   server.username             = "www-data"
   server.groupname            = "www-data"
   server.port                 = 80
   accesslog.filename          = "/var/log/lighttpd/access.log"
   accesslog.format            = "%{%s}t|%V|%r|%s|%b"
   index-file.names            = ( "index.php", "index.html", "index.lighttpd.html" )
   url.access-deny             = ( "~", ".inc", ".md", ".yml", ".ini" )
   static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
   compress.cache-dir          = "/var/cache/lighttpd/compress/"
   compress.filetype           = ( "application/javascript", "text/css", "text/html", "text/plain" )
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "/usr/share/lighttpd/create-mime.assign.pl"
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
   $HTTP["url"] =~ "^/admin/" {
       
       setenv.add-response-header = (
           "X-Pi-hole" => "The Pi-hole Web interface is working!",
           "X-Frame-Options" => "DENY"
       )
       $HTTP["url"] =~ ".ttf$" {
           
           setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
       }
   }
   $HTTP["url"] =~ "^/admin/\.(.*)" {
        url.access-deny = ("")
   }
   include_shell "cat external.conf 2>/dev/null"

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1495 May  2 03:32 /etc/cron.d/pihole
   23 4   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity
   00 00   * * *   root    PATH="$PATH:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate /etc/pihole/logrotate
   */10 *  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker local
   3 12  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
   @reboot root    PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 8519 May  2 03:26 /var/log/lighttpd/error.log
   2018-08-15 22:12:39: (log.c.217) server started 
   2018-08-15 22:13:51: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-08-15 22:13:51: (log.c.217) server started 
   2018-08-15 22:13:51: (server.c.1295) WARNING: unknown config-key: alias.url (ignored) 
   2018-08-15 22:19:26: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:19:26: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:19:36: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:19:46: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:19:56: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:20:07: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:20:31: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:21:13: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-08-15 22:21:14: (log.c.217) server started 
   2018-08-15 22:21:14: (server.c.1295) WARNING: unknown config-key: alias.url (ignored) 
   2018-08-15 22:21:17: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:21:28: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:21:39: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:21:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:22:00: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:22:06: (server.c.1828) server stopped by UID = 0 PID = 1 
   2018-08-15 22:22:07: (log.c.217) server started 
   2018-08-15 22:22:07: (server.c.1295) WARNING: unknown config-key: alias.url (ignored) 
   2018-08-15 22:22:11: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:22:22: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14
   2018-08-15 22:22:33: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning:  file_get_contents(/var/run/pihole-FTL.port): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/FTL.php on line 14

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 1120 May  2 03:41 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2019-05-02 03:26:37.565 763] Resizing "/FTL-queries" from 27754496 to 27983872
   [2019-05-02 03:27:49.468 763] Resizing "/FTL-queries" from 27983872 to 28213248
   [2019-05-02 03:29:00.601 763] Resizing "/FTL-queries" from 28213248 to 28442624
   [2019-05-02 03:30:15.502 763] Resizing "/FTL-queries" from 28442624 to 28672000
   [2019-05-02 03:31:26.022 763] Resizing "/FTL-queries" from 28672000 to 28901376
   [2019-05-02 03:32:37.023 763] Resizing "/FTL-queries" from 28901376 to 29130752
   [2019-05-02 03:33:43.107 763] Resizing "/FTL-queries" from 29130752 to 29360128
   [2019-05-02 03:34:55.075 763] Resizing "/FTL-queries" from 29360128 to 29589504
   [2019-05-02 03:36:06.890 763] Resizing "/FTL-queries" from 29589504 to 29818880
   [2019-05-02 03:37:18.063 763] Resizing "/FTL-queries" from 29818880 to 30048256
   [2019-05-02 03:38:25.449 763] Resizing "/FTL-queries" from 30048256 to 30277632
   [2019-05-02 03:39:37.206 763] Resizing "/FTL-queries" from 30277632 to 30507008
   [2019-05-02 03:40:48.794 763] Resizing "/FTL-queries" from 30507008 to 30736384
   [2019-05-02 03:41:58.569 763] Resizing "/FTL-queries" from 30736384 to 30965760

   -----tail of pihole-FTL.log------
   [2019-05-02 03:26:37.565 763] Resizing "/FTL-queries" from 27754496 to 27983872
   [2019-05-02 03:27:49.468 763] Resizing "/FTL-queries" from 27983872 to 28213248
   [2019-05-02 03:29:00.601 763] Resizing "/FTL-queries" from 28213248 to 28442624
   [2019-05-02 03:30:15.502 763] Resizing "/FTL-queries" from 28442624 to 28672000
   [2019-05-02 03:31:26.022 763] Resizing "/FTL-queries" from 28672000 to 28901376
   [2019-05-02 03:32:37.023 763] Resizing "/FTL-queries" from 28901376 to 29130752
   [2019-05-02 03:33:43.107 763] Resizing "/FTL-queries" from 29130752 to 29360128
   [2019-05-02 03:34:55.075 763] Resizing "/FTL-queries" from 29360128 to 29589504
   [2019-05-02 03:36:06.890 763] Resizing "/FTL-queries" from 29589504 to 29818880
   [2019-05-02 03:37:18.063 763] Resizing "/FTL-queries" from 29818880 to 30048256
   [2019-05-02 03:38:25.449 763] Resizing "/FTL-queries" from 30048256 to 30277632
   [2019-05-02 03:39:37.206 763] Resizing "/FTL-queries" from 30277632 to 30507008
   [2019-05-02 03:40:48.794 763] Resizing "/FTL-queries" from 30507008 to 30736384
   [2019-05-02 03:41:58.569 763] Resizing "/FTL-queries" from 30736384 to 30965760

*** [ DIAGNOSING ]: Locale
    LANG=

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 15959915 May  2 03:42 /var/log/pihole.log
   -----head of pihole.log------
   May  2 03:26:36 dnsmasq[763]: 101 192.168.0.1/40334 query[A] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 101 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1
   May  2 03:26:36 dnsmasq[763]: 101 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.1.1.1
   May  2 03:26:36 dnsmasq[763]: 102 192.168.0.1/40334 query[AAAA] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 102 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1
   May  2 03:26:36 dnsmasq[763]: 102 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.1.1.1
   May  2 03:26:36 dnsmasq[763]: 103 192.168.0.1/40334 query[AAAA] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 103 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1
   May  2 03:26:36 dnsmasq[763]: 103 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.1.1.1
   May  2 03:26:36 dnsmasq[763]: 104 192.168.0.1/40334 query[AAAA] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 104 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1
   May  2 03:26:36 dnsmasq[763]: 104 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.1.1.1
   May  2 03:26:36 dnsmasq[763]: 105 192.168.0.1/40334 query[AAAA] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 105 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1
   May  2 03:26:36 dnsmasq[763]: 105 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.1.1.1
   May  2 03:26:36 dnsmasq[763]: 106 192.168.0.1/40334 query[A] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 106 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1
   May  2 03:26:36 dnsmasq[763]: 106 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.1.1.1
   May  2 03:26:36 dnsmasq[763]: 107 192.168.0.1/40334 query[A] 2.debian.pool.ntp.org from 192.168.0.1
   May  2 03:26:36 dnsmasq[763]: 107 192.168.0.1/40334 forwarded 2.debian.pool.ntp.org to 1.0.0.1

Your gravity list is empty.

sudo nano /etc/resolv.conf

edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run `pihole -g’ to rebuild gravity.

1 Like

Thank you so much. That seemed to get it.

Just a heads up — I'm pretty basic at Linux, though understand the fundamentals of networking. I'm sure I'm continuing to do something wrong, but I've enabled the PiHole (I've also blocked domains using Wildcards), added additional Block Lists, have everything pointed at it from a DNS perspective… but it just doesn't seem to be blocking ads. There's a nice big one on the top of the NYT staring back at me right now.

Am I doing something wrong?

how are you testing? from an external device? laptop? you need to make sure the dns settings on the device you are using is pointing to the pihole or it will not block adds.

These tools can help you determine the source of ads you see:

Of note, I don't see ads when I load that site, so it may be a problem with your client having a DNS bypass around Pi-Hole:

You guys are the best. I'm slowly but surely killing these problems. Alas, a little like a game of whac-a-mole, I get one and another one comes up!

I've managed to get all the ads being blocked. In its place: super slow DNS queries. If I've been to the site it tends to speed up, but my usual wait for DNS resolution before the page begins to load is at least three seconds, oftentimes longer. I tried a few things: disabling the one blacklist I'd added, for example, but no joy. The forums perhaps suggested it was an IPv6 issue again but I'm not entirely sure what to do about it, if that's it?

Debug log:
https://tricorder.pi-hole.net/mh0n5x1udv!

Thank you again, really appreciate all the help :slight_smile:
-- james

What is the output of this command from the Pi-hole host terminal (this shows the activity in the last 24 hours):

echo ">stats" | nc localhost 4711

adblock@raspberrypi:~ $ echo ">stats" | nc localhost 4711

domains_being_blocked 111793
dns_queries_today 2967445
ads_blocked_today 4575
ads_percentage_today 0.154173
unique_domains 1749
queries_forwarded 2925495
queries_cached 35227
clients_ever_seen 5
unique_clients 5
dns_queries_all_types 2967445
reply_NODATA 55
reply_NXDOMAIN 7
reply_CNAME 96
reply_IP 169
privacy_level 0
status enabled
---EOM---

I tried changing some of the DNS settings in the DNS settings panel (switched over to Google; listen only on eth0; use DNSSEC) but it only made the problem worse. It got so slow the internet basically shut down and I had to go back to directly connecting to a DNS provider.

Thanks again for your help

This is likely the source of your problems with Pi-Hole performance. Almost 3 million queries in 24 hours. Let's look and see where all the queries are coming from and going to. What is the output of these commands from the Pi-Hole host terminal:

echo ">top-clients" | nc 127.0.0.1 4711

echo ">top-domains" | nc 127.0.0.1 4711

Sorry for the delay! And thank you again for all your help. Here's what we go:

adblock@raspberrypi:~ $ echo ">top-clients" | nc 127.0.0.1 4711
0 428 127.0.0.1 localhost
adblock@raspberrypi:~ $ echo ">top-domains" | nc 127.0.0.1 4711
0 48 1.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.4.0.0.7.4.6.0.6.2.ip6.arpa
1 48 1.1.1.1.in-addr.arpa
2 48 4.4.8.8.in-addr.arpa
3 48 1.1.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.4.0.0.7.4.6.0.6.2.ip6.arpa
4 48 4.4.8.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.8.4.0.6.8.4.1.0.0.2.ip6.arpa
5 48 8.8.8.8.in-addr.arpa
6 47 1.0.0.1.in-addr.arpa
7 24 api.github.com
8 23 1.0.168.192.in-addr.arpa
9 23 19.0.168.192.in-addr.arpa

Something doesn't match. Your first report for 24 hours showed almost 3 million queries. Here, about a day later the outputs show a few hundred queries. You must have changed something in the past 24 hours?

Run echo ">stats" | nc localhost 4711 again, please.

yes, i did. my bad. i had to turn route around the pihole in order to get the internet to work.

i set it back. here are the results again:

adblock@raspberrypi:~ $ echo ">stats" | nc localhost 4711

domains_being_blocked 111793

dns_queries_today 694571

ads_blocked_today 177

ads_percentage_today 0.025483

unique_domains 1846

queries_forwarded 681080

queries_cached 132

clients_ever_seen 5

unique_clients 2

dns_queries_all_types 694571

reply_NODATA 68

reply_NXDOMAIN 40

reply_CNAME 554

reply_IP 384

privacy_level 0

status enabled

---EOM---

adblock@raspberrypi:~ $ echo ">top-clients" | nc 127.0.0.1 4711

0 694309 192.168.0.1

1 454 127.0.0.1 localhost

adblock@raspberrypi:~ $ echo ">top-domains" | nc 127.0.0.1 4711

0 162942 init-p01st.push.apple.com

1 138055 push.apple.com

2 74853 pindorama.amazon.com

3 49099 ap.spotify.com

4 43482 d3p8zr0ffa9t17.cloudfront.net

5 35162 diagnostics.meethue.com

6 15962 aidc.apple.com

7 11880 dcp.dc1.philips.com

8 10993 init.itunes.apple.com

9 10413 (none).(null)

---EOM---

thanks again for your help btw. i realize you're doing this out of the goodness of your heart, and i really do appreciate it.

actually, one more question. is there any way to backtrack and see which of the devices is making these requests if they're (mostly) all pointing at my router itself? I think the #4 entry on the list is an Alexa but it'd be nice to be sure!

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