Please follow the below template, it will help us to help you!
Expected Behaviour:
Allow acess to NEST account and Apple App Store
Actual Behaviour:
I have two NEST thermostats - with PiHole specified as it's DNS, ONE of them would not communicate with the NEST server. Also, my new iPhone 10R and my wife's iPhone 8 returned "unable to access App Store" - DISABLING PiHole did NOT solve the issue; but, taking the PiHole out of my DNS spec altogether solved BOTH issues.
Your gravity list is empty (likely is corrupted). Rebuild gravity with pihole -g
This may not correct your NEST problem, but it will correct the gravity problem. After you do this, look at NEST performance.
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 1 Jan 27 10:18 /etc/pihole/gravity.list
-----head of gravity.list------
-----tail of gravity.list------
This empty gravity list resulted in this:
*** [ 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.75.5)
What are your upstream DNS servers in Pi-Hole? Both local IP addresses.
[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: 135381
[â] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 112751
[i] Number of whitelisted domains: 29
[i] Number of blacklisted domains: 0
[i] Number of regex filters: 0
[â] Parsing domains into hosts format
[â] Cleaning up stray matter
[â] Force-reloading DNS service
[â] DNS service is running
[â] Pi-hole blocking is Disabled
And now I see this:
pi@pihole:~ $ ls -lrt /etc/pihole/gravity*
-rw-r--r-- 1 root root 1 Jan 27 10:18 /etc/pihole/gravity.list
-rw-r--r-- 1 root root 2639430 Jan 28 07:20 /etc/pihole/gravity.list.bck
pi@pihole:~ $ file /etc/pihole/gravity*
/etc/pihole/gravity.list: very short file (no magic
/etc/pihole/gravity.list.bck: ASCII text
Just uploaded a new -d token 5pil1pl81f
Yes – I have two internal DNS servers. I think I (now – D’oh!) get why that might be problematic. I have a pretty complicated internal network, with 4 vLans, all managed by a SonicaWall TZ400, which is also currently my DHCP server, providing both static AND fixed IPs for all 4 vLans.
I did notice some “failed to resolve” messages at the top of the debug; but can’t figure those out. I did change my upstream DNS to Google and OpenDNS, and added all my local hosts to /etc/hosts.
These are showing that there was nothing in the gravity list. Pi-Hole randomly picks a known blocked domain (from your gravity list). If the list is empty, it can't find a known blocked domain and you see this output. It should show "... resolve [domain from your gravity list] ..."
*** [ 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.75.5)
[✓] doubleclick.com is 74.125.195.138 via a remote, public DNS server (8.8.8.8)
Do you still have the output of the gravity update command you ran?