*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via localhost (127.0.0.1)
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via Pi-hole (10.141.165.247)
[✓] doubleclick.com is 172.217.7.14 via a remote, public DNS server (8.8.8.8)
My Arris router doesn't have much flexibility so I disabled UDP port 53, in order to let the Pi Hole take over. I set the Pi Hole as DNS via the Arris, the WAN and Local IP Network:
Your gravity list is empty, as shown in your debug log. Run pihole -g to rebuild; or better yet, run pihole -r and select repair. This will repair Pi -Hole and rebuild gravity.
Will any of the logs show why this may have happened?
Also why does this error show:
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found... not backing up
Isn't is just lighthttpd.html? And then:
[✗] Pi-hole blocking is Disabled
* Using openssl for transmission.
/opt/pihole/piholeDebug.sh: line 1144: warning: command substitution: ignored null byte in input
Still showing Offline in Status. New debug token is p0msautiqq. pinhole.log is still logging:
Mar 1 00:05:33 dnsmasq[5992]: reply d3p8zr0ffa9t17.cloudfront.net is 52.85.93.24
Mar 1 00:05:33 dnsmasq[5992]: reply d3p8zr0ffa9t17.cloudfront.net is 52.85.93.152
Mar 1 00:05:33 dnsmasq[5992]: reply d3p8zr0ffa9t17.cloudfront.net is 52.85.93.162
Some other errors in the debug:
2019-02-21 22:03:26: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2019-02-21 22:17:12: (log.c.217) server started
2019-02-21 22:17:12: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2019-02-21 23:17:13: (log.c.217) server started
2019-02-21 23:17:13: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2019-02-21 23:21:13: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14
2019-02-21 23:21:20: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice: Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14
2019-02-22 01:17:14: (log.c.217) server started
These ouptuts show that pihole-FTL is running (for the last 42 minutes), pihole is resolving DNS queries (but not properly blocking flurry.com, which is found on the standard blocklists).
Did you rebuild gravity? If not, then Pi-Hole will not block anything, as the gravity list is the master list of domains to be blocked.
Gravity is normally rebuilt from either the web GUI > tools > rebuild gravity, or from the command line with pihole -g.
It may not complete, as there may be other problems. But, if we can get this rebuilt and problems still remain, we have eliminated at least one problem.
[i] Pi-hole blocking is disabled
[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: No changes detected
[i] Target: sysctl.org (hosts)
[✓] Status: No changes detected
[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[✓] Status: No changes detected
[i] Target: s3.amazonaws.com (simple_tracking.txt)
[✓] Status: No changes detected
[i] Target: s3.amazonaws.com (simple_ad.txt)
[✓] Status: No changes detected
[i] Target: hosts-file.net (ad_servers.txt)
[✓] Status: No changes detected
[✓] Consolidating blocklists
[✓] Extracting domains from blocklists
[i] Number of domains being pulled in by gravity: 135325
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 112862
[i] Number of whitelisted domains: 2
[i] Number of blacklisted domains: 2
[i] Number of regex filters: 1
[✓] Parsing domains into hosts format
[✓] Cleaning up stray matter
[✓] DNS service is running
[✗] Pi-hole blocking is Disabled
Any clues here?
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via localhost (127.0.0.1)
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via Pi-hole (10.141.165.247)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Fri 2019-03-01 10:04:28 EST; 8h ago
Docs: man:systemd-sysv-generator(8)
Process: 1669 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 1719 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
Mar 01 10:04:26 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Mar 01 10:04:27 raspberrypi pihole-FTL[1719]: Not running
Mar 01 10:04:27 raspberrypi su[1761]: Successful su for pihole by root
Mar 01 10:04:27 raspberrypi su[1761]: + ??? root:pihole
Mar 01 10:04:27 raspberrypi su[1761]: pam_unix(su:session): session opened for user pihole by (uid=0)
Mar 01 10:04:28 raspberrypi pihole-FTL[1719]: FTL started!
Mar 01 10:04:28 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
These aren't domain names, so they won't be requested from Pi-Hole. if the client already has the IP address, they just ask the router to connect them to that address.
Also, let's reset the nameserver for the Pi to ensure it can get to the internet, then update Pi-Hole. You are one version behind and the previous version had a few crash issues that should now be resolved. The update will also fix your gravity list.
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
Stop. The problem is in your configuration, which I missed in your debug log but see in this output. You have disabled blocking, thus the empty gravity list, Status of offline, etc.
From your debug log:
*** [ DIAGNOSING ]: Setup variables
....
BLOCKING_ENABLED=false
Success. Is there a way to see what may have caused this? I sure don't recall running pihole stop or anything of the like.
But thanks so much for your help. This is such a great tool. I'm using it as well to write a paper in my IOT course, as a part of my M.S. in Cybersecurity.
