Please follow the below template, it will help us to help you!
[After installing pi-hole and configuring it to work with unbound, the pi-hole system should be able to resolve domain names so the system can install updates, install packages, update the pi-hole blocklists, and browse the Internet in general. pinging a domain name should return a reply.]
_[Ported from a question I sent a user:
Hey just wondering if you could help me with an issue. I just set up unbound to work with my pi-hole using this guide: https://docs.pi-hole.net/guides/unbound/
I have had this issue in the past but previously it was just with setting up a regular pi-hole instance in a VM and also an instance using DNS over https.
My issue is after I install pihole, the system that I install it on loses the ability to resolve IPs. I installed pi-hole on a linux box on my local network, 192.168.0.11.
DNS settings in my router are set to that IP. All other machines on my LAN can resolve IPs, but the box I installed the pi-hole on and set up unbound cannot resolve IPs. The dig commands work though.
Looking into the issue I found this thread: Unbound and IPv6 DNS
I am unable to ping domains from the pi-hole linux box but ping6 works for some reason. I can even run the dig commands and they resolve correctly. But trying to browse the web via web browser, update pihole blocklists, or update the system all fail due to dns not resolving.
I cannot ssh into the linux box to copy text bc I can’t get openssh to install and didn’t have it set up beforehand so I’ll have to copy some pics into here:
As you can see in the last one, for some reason ping ipv4 isnt working but ping6 is. Destination host unreachable message I have seen before when I have set up other pi-hole instances.
I have a hunch this is due to the linux machine (192.168.0.11) being set in the router DNS settings, so the linux box is assigned DNS settings from my router via DHCP, and then it is asking itself to resolve DNS. I’m not sure if that’s the issue but it’s happened to me before and I’ve never been able to resolve (punny) it.
Here is the unbound/pi-hole.conf:
[Replace this text with the debug token provided from running
pihole -d (or running the debug script through the web interface]