DNS resolution
Returns SERVFAIL
[i] Checking for existing FTL binary...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed
[✓] man pages installed and datab
there was an error
I'll add that my pihole was running flawlessly for months prior to this issue popping up last Sunday.
What command were you running that resulted in this error?
Were you able to run debug and generate the log? If so, upload the log here, we'll make it private and look at it.
Since I was having DNS issues I ran nslookup cnn.com which used my pihole as a DNS server
Here's the log:
[Removed by moderator and converted to private].
As expected, the debug log shows some errors.
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
** [ 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.1.3)
[✓] doubleclick.com is 172.217.9.78 via a remote, public DNS server (8.8.8.8)
Run the following command from the Pi linux terminal and paste results. This will query your stats.
echo ">stats" | nc localhost 4711
Also run this command, paste results and verify that the time matches your local time. DNSSEC needs an accurate time to work properly.
date
domains_being_blocked 0
dns_queries_today 85763
ads_blocked_today 44
ads_percentage_today 0.051304
unique_domains 459
queries_forwarded 85457
queries_cached 17
clients_ever_seen 13
unique_clients 13
dns_queries_all_types 85851
reply_NODATA 19269
reply_NXDOMAIN 75
reply_CNAME 621
reply_IP 129061
status disabled
---EOM---
Date is WAYYYYYY off time wise by 36 minutes I'll run a clock re-sync
This should not be the case. Zero domains blocked = zero domains in gravity, so the only things being blocked are in your black list and regex list.
Your debug log shows you are using the seven block lists provided at install, which should get about 130K domains on the block list.
You can temporarily reset your name server for the Pi to a commercial DNS and run pihole repair. That may fix the problem.
sudo nano /etc/resolv.conf
Change 127.0.0.1 to 1.1.1.1, save and exit
pihole -r and select repair
that was it my time was WAY off no wonder it didn't work!!
Lesson learned: never assume ntp is installed & working.
#close
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.