Issue with the Pi hole functionality.
Issue with the Pi hole functionality.
I attempted to configure Pi Hole with your ISP DNS, but it didn’t work and I couldn’t determine the issue. It’s possible your ISP is blocking forwarding requests. Your DNS settings look correct—Google DNS, Open DNS, and Cloudflare are all enabled.
It's conceivable, though improbable, the problem stems from the initial setup.
The Pi-hole is functioning correctly, indicating the problem occurs before it. Is IPv6 active on your router? Have you activated IPv6 within the Pi-hole configuration?
Additionally, certain Android devices support configuring multiple DNS servers. If this option is available, adjust both settings to the Pi-Hole address and observe the results.
So, if I set both - nothning changes. No internet. Router supports IPv6, should have been enabled during the set up. Its a bit long haha, but here goes: *** [ INITIALIZING ] [i] 2019-09-19:11:13:21 debug log has been initialized. *** [ INITIALIZING ] Sourcing setup variables [i] Sourcing /etc/pihole/setupVars.conf... *** [ DIAGNOSING ]: Core version [i] Core: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i...i-hole/249) [i] Branch: master [i] Commit: v4.3.2-0-ge41c4b5 *** [ DIAGNOSING ]: Web version [i] Web: v4.3 (https://discourse.pi-hole.net/t/how-do-i...i-hole/249) [i] Branch: master [i] Commit: v4.3-0-g44aff72 *** [ DIAGNOSING ]: FTL version [✓] FTL: v4.3.1 *** [ DIAGNOSING ]: lighttpd version [i] 1.4.53 *** [ DIAGNOSING ]: php version [i] 7.3.4 *** [ DIAGNOSING ]: Operating system [✓] Raspbian GNU/Linux 10 (buster) *** [ DIAGNOSING ]: SELinux [i] SELinux not detected *** [ DIAGNOSING ]: Processor [✓] armv6l *** [ DIAGNOSING ]: Networking [✗] No IPv4 address(es) found on the wlan0 interface. [✗] No IPv6 address(es) found on the wlan0 interface. [i] Default IPv4 gateway: 192.168.2.254 * Pinging 192.168.2.254... [✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a...-hole/3546) *** [ DIAGNOSING ]: Ports in use *:22 sshd (IPv4) *:22 sshd (IPv6) [*:80] is in use by lighttpd [*:80] is in use by lighttpd [*:53] is in use by pihole-FTL [*:53] is in use by pihole-FTL [127.0.0.1:4711] is in use by pihole-FTL [[::1]:4711] is in use by pihole-FTL *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain [✓] vgtre.000webhostapp.com is 0.0.0.0 via localhost (127.0.0.1) [✗] Failed to resolve vgtre.000webhostapp.com via Pi-hole (192.168.2.2) [✓] doubleclick.com is 172.217.168.238 via a remote, public DNS server (8.8.8.8) *** [ DIAGNOSING ]: Pi-hole processes [✓] lighttpd daemon is active [✓] pihole-FTL daemon is active *** [ DIAGNOSING ]: Setup variables BLOCKING_ENABLED=true PIHOLE_INTERFACE=wlan0 IPV4_ADDRESS=192.168.2.2/24 IPV6_ADDRESS= QUERY_LOGGING=true INSTALL_WEB_SERVER=true INSTALL_WEB_INTERFACE=true LIGHTTPD_ENABLED=true DNSMASQ_LISTENING=single PIHOLE_DNS_1=8.8.8.8 PIHOLE_DNS_2=8.8.4.4 PIHOLE_DNS_3=8.26.56.26 PIHOLE_DNS_4=8.20.247.20 PIHOLE_DNS_5=9.9.9.11 PIHOLE_DNS_6=1.1.1.1 PIHOLE_DNS_7=1.0.0.1 DNS_FQDN_REQUIRED=true DNS_BOGUS_PRIV=true DNSSEC=false CONDITIONAL_FORWARDING=false DHCP_START=192.168.2.1 DHCP_END=192.168.2.251 DHCP_ROUTER=192.168.2.1 DHCP_LEASETIME=24 PIHOLE_DOMAIN=lan DHCP_IPv6=false DHCP_rapid_commit=false DHCP_ACTIVE=false *** [ DIAGNOSING ]: Dashboard and block page [✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements. [✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working! *** [ DIAGNOSING ]: Gravity list -rw-r--r-- 1 root root 2703822 Sep 19 10:32 /etc/pihole/gravity.list -----head of gravity.list------ 0.0.0.0 0.nextyourcontent.com 0.r.msn.com 0.start.bz -----tail of gravity.list------ zzz.clickbank.net zzzezeroe.fr zzzpooeaz-france.com zzzrtrcm2.com *** [ DIAGNOSING ]: contents of /etc/pihole -rw-r--r-- 1 root root 381 Sep 14 21:07 /etc/pihole/adlists.list https://raw.githubusercontent.com/Steven...ster/hosts https://mirror1.malwaredomains.com/files/justdomains http://sysctl.org/cameleon/hosts https://zeustracker.abuse.ch/blocklist.p...nblocklist https://s3.amazonaws.com/lists.disconnec...acking.txt https://s3.amazonaws.com/lists.disconnec...ple_ad.txt https://hosts-file.net/ad_servers.txt -rw-r--r-- 1 root root 44 Sep 19 10:32 /etc/pihole/local.list 192.168.2.2 raspberrypi 192.168.2.2 pi.hole -rw-r--r-- 1 root root 234 Sep 19 10:31 /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 } *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d -rw-r--r-- 1 root root 1496 Sep 19 10:42 /etc/dnsmasq.d/01-pihole.conf addn-hosts=/etc/pihole/gravity.list addn-hosts=/etc/pihole/black.list addn-hosts=/etc/pihole/local.list localise-queries no-resolv cache-size=10000 log-queries log-facility=/var/log/pihole.log local-ttl=2 log-async server=8.8.8.8 server=8.8.4.4 server=8.26.56.26 server=8.20.247.20 server=9.9.9.11 server=1.1.1.1 server=1.0.0.1 domain-needed bogus-priv interface=wlan0 *** [ DIAGNOSING ]: contents of /etc/lighttpd -rw-r--r-- 1 root root 3499 Sep 19 10:31 /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" ) mimetype.assign = ( ".png" => "image/png", ".jpg" => "image/jpeg", ".jpeg" => "image/jpeg", ".html" => "text/html", ".css" => "text/css; charset=utf-8", ".js" => "application/javascript", ".json" => "application/json", ".txt" => "text/plain", ".svg" => "image/svg+xml" ) include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port 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 1704 Sep 19 10:31 /etc/cron.d/pihole 37 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log 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 21 14 * * * 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 2011 Sep 19 10:31 /var/log/lighttpd/error.log 2019-09-14 21:11:16: (server.c.1464) server started (lighttpd/1.4.53) 2019-09-14 21:12:55: (server.c.2059) server stopped by UID = 0 PID = 1 2019-09-14 21:12:56: (server.c.1464) server started (lighttpd/1.4.53) 2019-09-14 21:12:56: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 2019-09-14 21:14:54: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-14 21:14:54: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-14 21:15:23: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-14 21:15:23: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-15 22:40:40: (server.c.1464) server started (lighttpd/1.4.53) 2019-09-15 22:40:40: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 2019-09-19 09:52:36: (server.c.1464) server started (lighttpd/1.4.53) 2019-09-19 09:52:36: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 2019-09-19 10:13:24: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:13:24: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:13:24: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:13:25: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:25:37: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:25:37: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:25:37: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:25:37: (response.c.404) uri-path does not begin with '/': pihole/index.php -> 400 2019-09-19 10:31:41: (server.c.2059) server stopped by UID = 0 PID = 1 2019-09-19 10:31:42: (server.c.1464) server started (lighttpd/1.4.53) 2019-09-19 10:31:42: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) *** [ DIAGNOSING ]: contents of /var/log -rw-r--r-- 1 pihole pihole 57192 Sep 19 10:43 /var/log/pihole-FTL.log -----head of pihole-FTL.log------ [2019-09-19 00:12:09.907 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.910 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.912 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.915 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.922 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.924 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.927 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.929 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.937 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.939 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.942 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.944 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.951 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.953 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.956 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:12:09.958 545] WARN: getOverTimeID(1568848500): 589 is too large: 1568495100 [2019-09-19 00:46:18.157 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.160 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.162 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.165 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.172 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.174 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.177 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.179 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.187 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.189 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.192 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.194 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.201 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.204 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.206 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 00:46:18.209 545] WARN: getOverTimeID(1568850300): 592 is too large: 1568495100 [2019-09-19 01:00:00.808 545] WARN: getOverTimeID(1568851500): 594 is too large: 1568495100 [2019-09-19 01:00:00.817 545] WARN: getOverTimeID(1568851500): 594 is too large: 1568495100 [2019-09-19 01:00:00.827 545] WARN: getOverTimeID(1568851500): 594 is too large: 1568495100 -----tail of pihole-FTL.log------ [2019-09-19 10:43:08.941 3802] SOCKETFILE: Using /var/run/pihole/FTL.sock [2019-09-19 10:43:08.941 3802] WHITELISTFILE: Using /etc/pihole/whitelist.txt [2019-09-19 10:43:08.942 3802] BLACKLISTFILE: Using /etc/pihole/black.list [2019-09-19 10:43:08.942 3802] GRAVITYFILE: Using /etc/pihole/gravity.list [2019-09-19 10:43:08.942 3802] REGEXLISTFILE: Using /etc/pihole/regex.list [2019-09-19 10:43:08.943 3802] SETUPVARSFILE: Using /etc/pihole/setupVars.conf [2019-09-19 10:43:08.943 3802] AUDITLISTFILE: Using /etc/pihole/auditlog.list [2019-09-19 10:43:08.943 3802] MACVENDORDB: Using /etc/pihole/macvendor.db [2019-09-19 10:43:08.944 3802] PARSE_ARP_CACHE: Active [2019-09-19 10:43:08.944 3802] Finished config file parsing [2019-09-19 10:43:08.950 3802] Database version is 3 [2019-09-19 10:43:08.951 3802] Database successfully initialized [2019-09-19 10:43:08.954 3802] New forward server: 8.8.4.4 (0/512) [2019-09-19 10:43:08.964 3802] New forward server: 8.8.8.8 (1/512) [2019-09-19 10:43:08.964 3802] New forward server: 1.0.0.1 (2/512) [2019-09-19 10:43:08.965 3802] New forward server: 1.1.1.1 (3/512) [2019-09-19 10:43:08.966 3802] Imported 729 queries from the long-term database [2019-09-19 10:43:08.966 3802] -> Total DNS queries: 729 [2019-09-19 10:43:08.967 3802] -> Cached DNS queries: 33 [2019-09-19 10:43:08.967 3802] -> Forwarded DNS queries: 64 [2019-09-19 10:43:08.967 3802] -> Exactly blocked DNS queries: 0 [2019-09-19 10:43:08.967 3802] -> Unknown DNS queries: 632 [2019-09-19 10:43:08.968 3802] -> Unique domains: 23 [2019-09-19 10:43:08.968 3802] -> Unique clients: 1 [2019-09-19 10:43:08.968 3802] -> Known forward destinations: 4 [2019-09-19 10:43:08.968 3802] Successfully accessed setupVars.conf [2019-09-19 10:43:09.000 3804] PID of FTL process: 3804 [2019-09-19 10:43:09.001 3804] Listening on port 4711 for incoming IPv4 telnet connections [2019-09-19 10:43:09.010 3804] Listening on port 4711 for incoming IPv6 telnet connections [2019-09-19 10:43:09.010 3804] Listening on Unix socket [2019-09-19 10:43:09.024 3804] Received SIGHUP, reloading cache [2019-09-19 10:43:09.025 3804] Blocking status is enabled [2019-09-19 10:43:09.025 3804] INFO: No whitelist file found [2019-09-19 10:43:09.026 3804] Compiled 0 Regex filters and 0 whitelisted domains in 0.4 msec (0 errors) [2019-09-19 10:43:12.848 3804] /etc/pihole/gravity.list: parsed 115962 domains (took 3820.5 ms) *** [ DIAGNOSING ]: contents of /dev/shm -rw------- 1 pihole pihole 323584 Sep 19 10:43 /dev/shm/FTL-clients -rw------- 1 pihole pihole 108 Sep 19 10:43 /dev/shm/FTL-counters -rw------- 1 pihole pihole 65536 Sep 19 10:43 /dev/shm/FTL-domains -rw------- 1 pihole pihole 12288 Sep 19 10:43 /dev/shm/FTL-forwarded -rw------- 1 pihole pihole 28 Sep 19 10:43 /dev/shm/FTL-lock -rw------- 1 pihole pihole 53248 Sep 19 10:43 /dev/shm/FTL-overTime -rw------- 1 pihole pihole 196608 Sep 19 10:59 /dev/shm/FTL-queries -rw------- 1 pihole pihole 12 Sep 19 10:43 /dev/shm/FTL-settings -rw------- 1 pihole pihole 4096 Sep 19 10:43 /dev/shm/FTL-strings *** [ DIAGNOSING ]: Locale LANG= *** [ DIAGNOSING ]: Pi-hole log -rw-r--r-- 1 pihole pihole 75923 Sep 19 11:13 /var/log/pihole.log -----head of pihole.log------ Sep 19 00:12:09 dnsmasq[545]: query[A] 0.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[AAAA] 0.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[A] 0.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[AAAA] 0.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[A] 1.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[AAAA] 1.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[A] 1.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[AAAA] 1.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[A] 2.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED Sep 19 00:12:09 dnsmasq[545]: query[AAAA] 2.debian.pool.ntp.org from 127.0.0.1 Sep 19 00:12:09 dnsmasq[545]: config error is REFUSED ******************************************** ******************************************** [✓] ** FINISHED DEBUGGING! ** * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only. * For more information, see: https://pi-hole.net/2016/11/07/crack-our...erry-pi-3/ * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat. [i] Debug script running in automated mode * Using curl for transmission.
It seems the Pi-hole isn't able to ping your router, and its IP address is 192.168.2.254. Make sure that's correct. Also verify the WAN interface on the Pi-hole is named wlan0. You might want to revisit the setup and manually configure the forwarding DNS servers instead of selecting from the default list. I'd suggest using 1.1.1.1 and 1.0.0.1 as alternatives.