Pi hole enabled but not blocking ads

#1

A clean install of Pi Hole on a new Pi 3 B+, if I check the pi hole admin page it says it’s enabled, but doesn’t block things. I see a number of things that cause concern on the debugging script, but I’m new enough at this that I don’t know what to do about them.

Debug Log

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] 2018-05-22:18:53:41 debug log has been initialized.

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

*** [ DIAGNOSING ]: Core version
[i] Core: v3.3.1 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3.1-0-gfbee18e

*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0

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

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

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

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

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

*** [ DIAGNOSING ]: Processor

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

[✓] IPv6 address(es) bound to the eth0 interface:
fe80::aa45:1f39:1064:92d5 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ 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.11.1

  • Pinging 192.168.11.1…
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[] is in use by
[4711] is in use by pihole-FTL

*** [ 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.11.249)
[✓] doubleclick.com is 216.58.218.174 via a remote, public DNS server (8.8.8.8)

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

*** [ DIAGNOSING ]: Setup variables
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
CONDITIONAL_FORWARDING=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.11.249/24
IPV6_ADDRESS=
PIHOLE_DNS_1=208.67.222.222
PIHOLE_DNS_2=208.67.220.220
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1

*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Tue, 22 May 2018 18:53:58 GMT
Server: lighttpd/1.4.45

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

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

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

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

-rw-r–r-- 1 root root 633 May 22 18:01 /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 50 May 22 18:35 /etc/pihole/local.list
192.168.11.249 raspberrypi
192.168.11.249 pi.hole

-rw-r–r-- 1 root root 234 May 22 18: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 1547 May 22 18: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
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=208.67.222.222
server=208.67.220.220
domain-needed
bogus-priv
interface=eth0

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

-rw-r–r-- 1 root root 3027 May 22 18: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” )
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 1496 May 22 18:31 /etc/cron.d/pihole
24 3 * * 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
52 18 * * * 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 577 May 22 18:32 /var/log/lighttpd/error.log
2018-05-22 17:56:12: (log.c.217) server started
2018-05-22 18:01:05: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-22 18:01:07: (log.c.217) server started
2018-05-22 18:13:56: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined index: HTTP_HOST in /var/www/html/pihole/index.php on line 10
2018-05-22 18:13:56: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined index: HTTP_HOST in /var/www/html/pihole/index.php on line 10
2018-05-22 18:32:13: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-22 18:32:16: (log.c.217) server started

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

-rw-r–r-- 1 pihole pihole 10390 May 22 18:49 /var/log/pihole-FTL.log
[2018-05-22 18:01:18.852]
[2018-05-22 18:01:18.852] FTL branch: v3.0
[2018-05-22 18:01:18.853] FTL version: v3.0
[2018-05-22 18:01:18.853] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d7
[2018-05-22 18:01:18.853] FTL date: 2018-02-14 12:45:47 -0800
[2018-05-22 18:01:18.853] FTL user: pihole
[2018-05-22 18:01:18.854] Notice: Found no readable FTL config file
[2018-05-22 18:01:18.854] Using default settings
[2018-05-22 18:01:18.854] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2018-05-22 18:01:18.855] SOCKET_LISTENING: only local
[2018-05-22 18:01:18.855] QUERY_DISPLAY: Show queries
[2018-05-22 18:01:18.855] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2018-05-22 18:01:18.856] MAXDBDAYS: max age for stored queries is 365 days
[2018-05-22 18:01:18.856] RESOLVE_IPV6: Resolve IPv6 addresses
[2018-05-22 18:01:18.856] RESOLVE_IPV4: Resolve IPv4 addresses
[2018-05-22 18:01:18.856] DBINTERVAL: saving to DB file every minute
[2018-05-22 18:01:18.857] DBFILE: Using /etc/pihole/pihole-FTL.db
[2018-05-22 18:01:18.857] MAXLOGAGE: Importing up to 24.0 hours of log data
[2018-05-22 18:01:18.857] Finished config file parsing
[2018-05-22 18:01:18.870] Found no other running pihole-FTL process
[2018-05-22 18:01:18.901] PID of FTL process: 13610
[2018-05-22 18:01:18.902] Error: failed to read /etc/pihole/list.preEventHorizon
[2018-05-22 18:01:18.902] Gravity list entries: -1
[2018-05-22 18:01:18.902] No blacklist present
[2018-05-22 18:01:18.903] No wildcard blocking list present

*** [ DIAGNOSING ]: Pi-hole log
-rw-r–r-- 1 dnsmasq root 254394 May 22 18:53 /var/log/pihole.log
-----head of pihole.log------
May 22 18:00:59 dnsmasq[13431]: started, version 2.76 cachesize 10000
May 22 18:00:59 dnsmasq[13431]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
May 22 18:00:59 dnsmasq[13431]: warning: ignoring resolv-file flag because no-resolv is set
May 22 18:00:59 dnsmasq[13431]: using nameserver 8.8.4.4#53
May 22 18:00:59 dnsmasq[13431]: using nameserver 8.8.8.8#53
May 22 18:00:59 dnsmasq[13431]: read /etc/hosts - 5 addresses
May 22 18:00:59 dnsmasq[13431]: failed to load names from /etc/pihole/local.list: No such file or directory
May 22 18:00:59 dnsmasq[13431]: failed to load names from /etc/pihole/black.list: No such file or directory
May 22 18:00:59 dnsmasq[13431]: failed to load names from /etc/pihole/gravity.list: No such file or directory
May 22 18:01:26 dnsmasq[13431]: 1 127.0.0.1/46458 query[AAAA] raw.githubusercontent.com from 127.0.0.1
May 22 18:01:26 dnsmasq[13431]: 1 127.0.0.1/46458 forwarded raw.githubusercontent.com to 8.8.4.4
May 22 18:01:26 dnsmasq[13431]: 1 127.0.0.1/46458 forwarded raw.githubusercontent.com to 8.8.8.8
May 22 18:01:26 dnsmasq[13431]: 1 127.0.0.1/46458 reply raw.githubusercontent.com is
May 22 18:01:26 dnsmasq[13431]: 1 127.0.0.1/46458 reply github.map.fastly.net is NODATA-IPv6
May 22 18:01:26 dnsmasq[13431]: 2 127.0.0.1/47401 query[A] raw.githubusercontent.com from 127.0.0.1
May 22 18:01:26 dnsmasq[13431]: 2 127.0.0.1/47401 cached raw.githubusercontent.com is
May 22 18:01:26 dnsmasq[13431]: 2 127.0.0.1/47401 forwarded raw.githubusercontent.com to 8.8.4.4
May 22 18:01:26 dnsmasq[13431]: 2 127.0.0.1/47401 reply raw.githubusercontent.com is
May 22 18:01:26 dnsmasq[13431]: 2 127.0.0.1/47401 reply github.map.fastly.net is 151.101.0.133
May 22 18:01:26 dnsmasq[13431]: 2 127.0.0.1/47401 reply github.map.fastly.net is 151.101.64.133



[✓] ** FINISHED DEBUGGING! **

0 Likes

#2

Run a pihole -g and paste the output here.

0 Likes

#3

[i] Neutrino emissions detected…
[✓] Pulling blocklist source list into range

[i] Target: raw.githubusercontent.com (hosts)
[✓] Status: Retrieval successful

[i] Target: mirror1.malwaredomains.com (justdomains)
[✓] Status: Retrieval successful

[i] Target: sysctl.org (hosts)
[✓] Status: Retrieval successful

[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[✓] Status: Retrieval successful

[i] Target: s3.amazonaws.com (simple_tracking.txt)
[✓] Status: Retrieval successful

[i] Target: s3.amazonaws.com (simple_ad.txt)
[✓] Status: Retrieval successful

[i] Target: hosts-file.net (ad_servers.txt)
[✓] Status: Retrieval successful

[✓] Consolidating blocklists
[✓] Extracting domains from blocklists
[i] Number of domains being pulled in by gravity: 145129
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 122172
[i] Nothing to whitelist!
[✓] Parsing domains into hosts format
[✓] Cleaning up stray matter

[✓] Force-reloading DNS service
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

0 Likes

#4

How’s you Pi-hole now? Is it working ?

The above command pulled in the blocklists and compiled them under one.

0 Likes

#5

Unfortunately, my pi hole is still not working. I double checked that I set my pi as my router’s primary DNS server (in LAN, not WAN), and it is. When I run pihole -d it resolved the name resolution issues, but it still isn’t blocking any ads. Here’s the new debug log:

*** [ INITIALIZING ]
[i] 2018-05-23:04:30:25 debug log has been initialized.

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

*** [ DIAGNOSING ]: Core version
[i] Core: v3.3.1 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3.1-0-gfbee18e

*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0

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

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

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

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

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

*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 470: $’[\E[32m✓\E[0m] \E[32marmv6l\E[0m’: command not found

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

[✓] IPv6 address(es) bound to the eth0 interface:
fe80::aa45:1f39:1064:92d5 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ 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.11.1

  • Pinging 192.168.11.1…
    [✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[] is in use by
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] galaxyinvi.com is 192.168.11.249 via localhost (127.0.0.1)
[✓] galaxyinvi.com is 192.168.11.249 via Pi-hole (192.168.11.249)
[✓] doubleclick.com is 216.58.218.174 via a remote, public DNS server (8.8.8.8)

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

*** [ DIAGNOSING ]: Setup variables
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
CONDITIONAL_FORWARDING=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.11.249/24
IPV6_ADDRESS=
PIHOLE_DNS_1=208.67.222.222
PIHOLE_DNS_2=208.67.220.220
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1

*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r–r-- 1 root root 4600869 May 22 23:01 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.11.249 0.0.0.0
192.168.11.249 0.r.msn.com
192.168.11.249 0.start.bz
192.168.11.249 000.gaysexe.free.fr

-----tail of gravity.list------
192.168.11.249 zzsyw.com
192.168.11.249 zztxdown.com
192.168.11.249 zzz.clickbank.net
192.168.11.249 zzzrtrcm2.com

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

-rw-r–r-- 1 root root 633 May 22 18:01 /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 50 May 22 23:01 /etc/pihole/local.list
192.168.11.249 raspberrypi
192.168.11.249 pi.hole

-rw-r–r-- 1 root root 234 May 22 18: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 1547 May 22 18: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
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=208.67.222.222
server=208.67.220.220
domain-needed
bogus-priv
interface=eth0

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

-rw-r–r-- 1 root root 3027 May 22 18: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” )
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 1496 May 22 18:31 /etc/cron.d/pihole
24 3 * * 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
52 18 * * * 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 577 May 22 18:32 /var/log/lighttpd/error.log
2018-05-22 17:56:12: (log.c.217) server started
2018-05-22 18:01:05: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-22 18:01:07: (log.c.217) server started
2018-05-22 18:13:56: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined index: HTTP_HOST in /var/www/html/pihole/index.php on line 10
2018-05-22 18:13:56: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined index: HTTP_HOST in /var/www/html/pihole/index.php on line 10
2018-05-22 18:32:13: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-22 18:32:16: (log.c.217) server started

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

-rw-r–r-- 1 pihole pihole 2214 May 23 02:42 /var/log/pihole-FTL.log
[2018-05-23 00:00:02.669] NOTICE: pihole.log has been flushed
[2018-05-23 00:00:02.670] Resetting internal data structure
[2018-05-23 00:00:02.670] Queries in memory before flushing: 851
[2018-05-23 00:00:02.671] FATAL: Trying to free NULL pointer in pihole_log_flushed() (flush.c:61)
[2018-05-23 00:00:03.240] Gravity list entries: 122172
[2018-05-23 00:00:03.240] No blacklist present
[2018-05-23 00:00:03.241] No wildcard blocking list present
[2018-05-23 00:00:03.244] Notice: Increasing queries struct size from 0 to 10000 (440.35 KB)
[2018-05-23 00:00:03.245] Notice: Increasing domains struct size from 0 to 1000 (460.35 KB)
[2018-05-23 00:00:03.245] Notice: Increasing clients struct size from 0 to 10 (460.51 KB)
[2018-05-23 00:00:03.246] New client: 127.0.0.1 localhost (0/10)
[2018-05-23 00:00:03.246] Notice: Increasing forwarded struct size from 0 to 4 (460.62 KB)
[2018-05-23 00:00:03.312] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
[2018-05-23 00:00:03.313] Notice: Increasing overTime struct size from 0 to 100 (464.65 KB)
[2018-05-23 00:00:03.371] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
[2018-05-23 00:00:03.380] New client: 192.168.11.238 (1/10)
[2018-05-23 00:00:03.396] New client: 192.168.11.112 (2/10)
[2018-05-23 00:00:03.406] New client: 192.168.11.237 (3/10)
[2018-05-23 00:00:03.423] New client: 192.168.11.131 (4/10)
[2018-05-23 00:00:03.433] New client: 192.168.11.187 (5/10)
[2018-05-23 00:00:03.442] New client: 192.168.11.250 (6/10)
[2018-05-23 00:00:03.455] New client: 192.168.11.228 (7/10)
[2018-05-23 00:00:03.514] New forward server: 208.67.220.220 resolver2.opendns.com (2/4)
[2018-05-23 00:00:03.588] New forward server: 208.67.222.222 resolver1.opendns.com (3/4)
[2018-05-23 00:00:03.590] Notice: Increasing forwarded struct size from 4 to 8 (472.72 KB)

*** [ DIAGNOSING ]: Pi-hole log
-rw-r–r-- 1 dnsmasq root 20264 May 23 04:30 /var/log/pihole.log
-----head of pihole.log------
May 23 00:00:03 dnsmasq[16175]: 1496 127.0.0.1/37961 query[PTR] 4.4.8.8.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1496 127.0.0.1/37961 forwarded 4.4.8.8.in-addr.arpa to 208.67.220.220
May 23 00:00:03 dnsmasq[16175]: 1496 127.0.0.1/37961 forwarded 4.4.8.8.in-addr.arpa to 208.67.222.222
May 23 00:00:03 dnsmasq[16175]: 1496 127.0.0.1/37961 reply 8.8.4.4 is google-public-dns-b.google.com
May 23 00:00:03 dnsmasq[16175]: 1497 127.0.0.1/54790 query[PTR] 8.8.8.8.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1497 127.0.0.1/54790 forwarded 8.8.8.8.in-addr.arpa to 208.67.220.220
May 23 00:00:03 dnsmasq[16175]: 1497 127.0.0.1/54790 reply 8.8.8.8 is google-public-dns-a.google.com
May 23 00:00:03 dnsmasq[16175]: 1498 127.0.0.1/35803 query[PTR] 238.11.168.192.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1498 127.0.0.1/35803 config 192.168.11.238 is NXDOMAIN
May 23 00:00:03 dnsmasq[16175]: 1499 127.0.0.1/56977 query[PTR] 112.11.168.192.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1499 127.0.0.1/56977 config 192.168.11.112 is NXDOMAIN
May 23 00:00:03 dnsmasq[16175]: 1500 127.0.0.1/39032 query[PTR] 237.11.168.192.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1500 127.0.0.1/39032 config 192.168.11.237 is NXDOMAIN
May 23 00:00:03 dnsmasq[16175]: 1501 127.0.0.1/34091 query[PTR] 131.11.168.192.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1501 127.0.0.1/34091 config 192.168.11.131 is NXDOMAIN
May 23 00:00:03 dnsmasq[16175]: 1502 127.0.0.1/54056 query[PTR] 187.11.168.192.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1502 127.0.0.1/54056 config 192.168.11.187 is NXDOMAIN
May 23 00:00:03 dnsmasq[16175]: 1503 127.0.0.1/41817 query[PTR] 250.11.168.192.in-addr.arpa from 127.0.0.1
May 23 00:00:03 dnsmasq[16175]: 1503 127.0.0.1/41817 config 192.168.11.250 is NXDOMAIN
May 23 00:00:03 dnsmasq[16175]: 1504 127.0.0.1/54680 query[PTR] 228.11.168.192.in-addr.arpa from 127.0.0.1



[✓] ** FINISHED DEBUGGING! **

0 Likes

#6

Been messing around with it a bit today and still clueless as to why it’s not working. I may just take the nuclear option and start over to see if that fixes it…

0 Likes

#7

what’s the output of nslookup google.com on your device ?

0 Likes

#8

connection timed out, no servers could be reached.

0 Likes

#9

This part of the debug log shows that pi-hole is actually working AND blocking.

I think there’s something else going on there.

How about a dig flurry.com on the raspberry. What’s the output of that?

0 Likes

#10

The results of a dig flurry:

; <<>> DiG 9.10.3-P4-Raspbian <<>> flurry.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16627
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;flurry.com. IN A

;; ANSWER SECTION:
flurry.com. 2 IN A 192.168.11.249

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed May 23 23:39:58 UTC 2018
;; MSG SIZE rcvd: 55

Additional info: looking at the web interface, it says it’s been able to block 30% of ads recently.

0 Likes

#11

query resolved to your Pi-hole IP

Server used was localhost, the correct one.

This does show that adblocking/pi-hole works.

0 Likes

#12

Okay, so it’s blocking ads, but not most of them. Any suggestions for where to look as to why it’s missing so many?

0 Likes

#13

You are probably using a secondary DNS (a public one) and queries leak through that secondary one. Either at router level or client level.

Also your query might be going through IPV6 and your raspberry pi does not have an IPV6 that can be used as DNS.

Check your devices and see if they use IPV6 and if the have an IPV6 DNS.

You could also disable the secondary DNS wherever you have it enabled.

1 Like

#14

Okay, I’ll start investigating that route and see what I can turn up. Thank you!

0 Likes

#15

Do you think flushing the router’s DNS cache would do anything?

0 Likes

#16

Just an update:
I haven’t been able to fix it so it successfully blocks ads across the network; even when I set the pi as the only DNS server, the router itself is still acting as a DNS and I can’t figure out how to stop it from doing so. I’ve just manually added the pi as my laptop’s DNS and it’s working fine for my laptop. I’ll save further investigation into the router for later, when I’m feeling inspired.

0 Likes

#17

You could disable the DHCP in your router and use the Pi-hole as your DHCP server.

That will push the correct settings (DNS server as Pi-hole included) to all the clients.

0 Likes

#18

In my router I had to set the secondary DNS server to 10.0.0.0 (a dummy address).

0 Likes

#19

I tried using the pi-hole’s DHCP once and the other members of the household were having problems with their laptops, but we’ll try it again.

My router recognizes it as a dummy address and refuses to accept it.

0 Likes

closed #20

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

0 Likes