Hi, I'm a relative noob when it comes to PiHole, I just followed the user guide for installation 4 years ago and it worked like a charm at my old home. I also used unbound.
Now I've moved to a new house and am trying to set it up there. I got it to work - for one night. This morning all the ads were back. So I figured I'd run pihole -g to see if that helps but I get DNS resolve not available at the moment error.
Can someone please help me, in the most noob-friendly way possible? Debug log attached below.
First to fix the DNS resolve and second to fix PiHole not blocking ads...
Your debug log shows that Pi-hole is running and is able to process queries on the open interfaces. But, there is no connectivity (at minimum on port 53) from the Pi to the internet:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] shelvesandbookshops.tk is 0.0.0.0 on lo (127.0.0.1)
[✓] shelvesandbookshops.tk is 0.0.0.0 on wlan0 (192.168.1.203)
[✓] shelvesandbookshops.tk is 0.0.0.0 on wg0 (10.100.0.1)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Operating system
[i] Distro: Raspbian
[i] Version: 10
[✗] dig return code: 10
[✗] dig response: dig: couldn't get address for 'ns1.pi-hole.net': failure
[✗] Error: dig command failed - Unable to check OS
It means something is blocking or interfering with port 53 traffic. Are you running any firewall or other software on your LAN that will block or re-route port 53 (DNS) traffic?
This won't survive reboots - you haver to update your OS's network configuration.
That looks like a netmask, not like a proper gateway address.
Your router's private range IP address should show up there, i.e your 192.168.1.xxx.
Note that Raspberry Pi OS has switched to dhcpcd as its preferred network configuration tool with Raspbian Jessie in 2015. While it is still possible to configure your NICs via /etc/network/interfaces, it may interfere with your OS's dhcpcd configuration.
In addition, dhcpcd will probably be replaced by NetworkManager in one of the next releases. For the current 11/Bullseye, NM is still optional.
This is an OS level network configuration issue.
You should consider to consult other forums specialising in networking as well.
I am sure that for IPv4 it is yes. I think the issue is that the router auto-switched to IPv6 and I can't configure IPv6 to run via Pi - it's a Spectrum provided Router that only has limited functionality through an App, I couldn't find any IPv6 settings on there.
How do I do that? Do I simply put the gateway into the dhcpcd.conf?
With a current default Raspberry Pi OS 11/Bullseye, editing your /etc/dhcpcd.conf would suffice.
However, since you seem to have used /etc/network/interfaces in the past, the resulting overall configuration may not behave as expected.
You'd have to consolidate and adopt your network configuration according to the configuration steps you've applied in the past (which potentially may or may not involve further networking tools as well).
As said previously, this is an OS level network configuration issue.
You should consider to consult other forums specialising in networking as well.
Alternatively, instead of trying to repair your current mixed configuration, you could start with a fresh current OS image and install Pi-hole again.
If your RPi is just hosting Pi-hole, that may be your fastest and most hassle-free option.
