Ever since upgrading to Pi-hole v4, I've been seeing this issue crop up from time to time. In addition, I will see the "Domains on Blocklist" set to 0.
In addition, any local name resolution attempt fails. Therefore, I am unable to upload my debug log file.
x054ygj00g
What is the output of the following command from the Linux terminal:
echo ">stats" | nc localhost 4711
pi@raspberrypi:~ $ echo ">stats" | nc localhost 4711
domains_being_blocked 130557
dns_queries_today 24261
ads_blocked_today 4943
ads_percentage_today 20.374264
unique_domains 5094
queries_forwarded 0
queries_cached 0
clients_ever_seen 3
unique_clients 3
dns_queries_all_types 25206
reply_NODATA 0
reply_NXDOMAIN 0
reply_CNAME 0
reply_IP 4943
status enabled
---EOM---
I was able to edit /etc/resolv.conf and set nameserver to 8.8.8.8, temporarily so at least my debug file could upload.
debug token is: x054ygj00g
According to your debug log, you are able to resolve blocked domains, right? And you are unable to resolve unblocked domains, or ping 8.8.8.8?
I believe what happened is that when I upgraded Pi-hole from v3 to v4, it overwrote/etc/dnsmasq.d/01-pihole.conf.
Once I added server=127.0.0.1#54 back into 01-pihole.conf, everything started working again.
I believe this was root cause and I'll be monitoring over the next several days to make sure.
You shouldn't modify the generated dnsmasq configs directly. Instead, go to the web interface and enter the upstream servers you want.
I should have stated earlier on that I am running Cloudflared.
Then the loopback IP and port should be entered in custom 1 or 2 IPv4.
Yes it will.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
