Pi-hole only working when connected to VPN

Hello All,

I’ve had my Pi-hole set up for about 2 years in combination with wireguard VPN so I can use it on the go. since last week in noticed it is not blocking any ads anymore if I’m not connected to the VPN. I can also see it on the bar chart on the dashboard. It only shows permitted DNS queries and when I connect to the Wireguard VPN, Only then, the denied DNS queries will show and ADs are blocked. I’ve updated the Pi-hole to the newest version but this didn’t help. Been using my Pi-hole as DNS server for my router that had DHCP turned on so it used to work network wide. I’ve tried setting the interface settings to permit all origins but that also doesnt work. Does anyone know what could be causing this problem.

Been using my Pi-hole as DNS server for my router that had DHCP turned on so it used to work network wide.

So, when you use the VPN that forces use of Pihole, Pihole works, but when using the DHCP-provided setting it doesn’t? Sounds like the issue is the DHCP configuration in the router.

Did you try with a static configuration?

Somehow it was not using my pinhole as DNS anymore. Switching off IPv6 on my router and rebooting, as suggested by pihole Devs, has resolved my issue.

Please generate a debug log, upload it when prompted and post the token URL here.

Is this while on Mobile?

I tried turing off DHCP on my router and turning it on, on my Pi-Hole but that also didn’t work. Haven’t tried static yet.

Thanks for the reply. The token is https://tricorder.pi-hole.net/w7tyhwPn/

I tried turing off DHCP on my router and turning it on, on my Pi-Hole but that also didn’t work.

… Did you force the lease’s renewal before the test? Easy to forget that changing DHCP shouldn’t affect clients instantly.

Your debug log shows that Pi-hole is listening on the local port and is able to resolve DNS queries through that port:

[✓] d2ubbq736gg74q.cloudfront.net is 0.0.0.0 on wlan0 (192.168.2.5)

Your log also shows that Pi-hole is receiving local DNS queries. Your router is at 254, so it doesn’t appear to be the router.

   Oct 18 00:09:53 dnsmasq[1400]: query[A] webhook.logentries.com from 192.168.2.1
   Oct 18 00:09:53 dnsmasq[1400]: gravity blocked webhook.logentries.com is 0.0.0.0

   Oct 18 13:35:09 dnsmasq[673]: query[A] d2ubbq736gg74q.cloudfront.net from 192.168.2.5
   Oct 18 13:35:09 dnsmasq[673]: gravity blocked d2ubbq736gg74q.cloudfront.net is 0.0.0.0

From a client on your LAN (and not one connected via VPN), and from the command prompt or terminal on that client (and not via SSH to the Pi terminal), what are the outputs of the following:

nslookup pi.hole

nslookup flurry.com

nslookup flurry.com 192.168.2.5

I’ve send you a direct message with the output :slight_smile: