Pi-hole resolves but sometimes won't update gravity and sometimes will; FTL 6.2.2 did not fix

Help
1

Please follow the below template, it will help us to help you!

standard install on bare metal pi 4B, no docker or vm or other containerization

Expected Behaviour:

gravity always updates rather than only update infrequently; host machine (pi 4B) can access internet and update)

Actual behaviour: Pi-hole resolves but sometimes won't update gravity and sometimes will; pi-hole running on bare metal Raspberry Pi 4B, and Pi 4B does not have internet access; when running "sudo pi-hole -up" I receive the following error message:

"[i] Checking for updates...
fatal: unable to access 'GitHub - pi-hole/pi-hole: A black hole for Internet advertisements': Could not resolve host: github.com

Error: Unable to update local repository. Contact Pi-hole Support."

I changed DNS servers from pi-hole to a third-party and was able to update to FTL 6.2.2, but that did not fix the issues

my network is running on Ubiquiti equipment (UDM Pro) with firewalls configured so that there were no issues with p-hole prior to updating to FTL 6.2

Debug Token:

https://tricorder.pi-hole.net/GhEeU0pV/

1 Like
2

That indicates that the server running Pi-hole was not able to resolve that domain name. We do not suggest that Pi-hole use itself as a resolver (set in /etc/resolv.conf typically). If you change the DNS server in /etc/resolv.conf to a known working DNS resolver does that improve the situation?

It is also possible that your IPv6 configuration is causing problems. There doesn't appear to be remote IPv6 connectivity as shown by the failing check on the last line:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] rtlog-ru.tiktokv.com is NOERROR on lo (127.0.0.1)
[✓] rtlog-ru.tiktokv.com is NOERROR on eth0 (192.168.13.207)
[✓] No IPv4 address available on wlan0
[✓] doubleclick.com is 142.250.80.46 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] extlog.snssdk.com is NOERROR on lo (::1)
[✓] extlog.snssdk.com is NOERROR on eth0 (fe80::f1a:3bca:86a7:a76f%eth0)
[✓] No IPv6 address available on wlan0
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
4

Thanks for the quick reply. I think I fixed the issues. At the time that I suddenly started experiencing this issue after upgrading to FTL 6.2, my default gateway (UDM Pro with a default network subnet of (as an example) 192.168.1.1 was set so that DNS pointed to my Pi 4B's (running Pi-hole on bare metal) static local IP address (as an example, 192.168.1.13). When I changed the specific DNS setting of the subnet network that the Pi 4B is on to the specific local IP address of the Pi 4B (192.168.1.13) rather than merely to the default gateway (192.168.1.1, which then points to 192.168.1.13), all issues were resolved. This isn't the exact fix that DanSchaper identified, and I'm not sure why removing one hop seems to matter, but it seems to be fixed. Any "post-mortem" insight as to why my approach fixed this issue and why my previous setup worked before upgrading to FTL 6.2 would be appreciated!

5

I think I am running into this same strange issue. I have two PiHoles (Raspberry Pi 4's) in my home network, primary (192.168.53.51) and secondary (192.168.53.52). As a side note, I use keepalive for HA (192.168.53.53). My primary unit has been having fits resolving DNS inquiries. Restarts fix the issue temporarily, but then it becomes unresponsive. They are both on the most current PiHole releases. I debug'd the primary (https://tricorder.pi-hole.net/8UtGVG2L/) and secondary (https://tricorder.pi-hole.net/73XseyqK/). Interestingly, the only difference in settings between the two are the network configs is the nameservers line. The primary is:

interface eth0
static ip_address=192.168.53.51/24
static routers=192.168.53.1
static domain_name_servers=192.168.53.52 1.1.1.1

denyinterfaces wlan0

The secondary is:

interface eth0
static ip_address=192.168.53.52/24
static routers=192.168.53.1
static domain_name_servers=127.0.0.1 192.168.53.51 1.1.1.1

denyinterfaces wlan0