ISP DNS served

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

My setup consists of - Raspberry Pi5 - ISP Router - WISP Router (main - connected wirelessly to the ISP router)

I've successfully installed PiHole and connected it to my WISP router wirelessly 192.168.16.105 and through cable 192.168.16.107

I've configured my WISP router to by default serve those local IPs to my Raspberry Pi and in the LAN settings i've set both DNS1 and DNS2 respectively to the Pi's Local IPs. I've also set pihole's upstream to quad9 solely (ipv4).

After a quick reboot pi.hole resolved and i logged in and queries were being logged and blocked as per the list provided everything worked well as i've tested "doubleclick.net" multiple times on and off and PiHole was blocking queries it flagged.

Actual Behaviour:

The PiHole's Behaviour is fine it's doing it's job blocking queries and all. My issue is with dnsleaktest.com or any other dns checker/lookup which pulls the dns through a test i'm not familiar how it works. My ISP dns shows up on those tests even tho i'm connected to my WISP router with pihole configured and working.

I've tested it multiple times i tried as usual "doubleclick.net" and it was being blocked then went to dnschecker.com and my ISP dns kept showing up instead of Quad9's.

To note: My devices were being served the following dns: 192.168.16.1 and 8.8.8.8 which i suspect are my ISP DNS with 192.168.16.1 forwarding the request to DNS1 of my isp and 8.8.8.8 was the isp's 2nd DNS set. But this is all speculation i don't know for sure. Plus the option to change or edit ISP dns is greyed out in router's config i was never able to change my ISP DNS.

What i know is i changed the DNS manually to only use 192.168.16.1 on my Linux computer. On my android phone i've turned off private dns and using the router DNS.

Finally:

What could be the issue. My wisp router? When connected to my wisp router should the dns served to my device be the pi's IP or the router's gateway that is already being served along side 8.8.8.8

Is the DNS being served from my WISP router being pushed from the ISP router since 8.8.8.8 seems to appear as DNS2 in both scenarios and i've never configured 8.8.8.8 ever it came by default as my ISP's secondary dns.

Debug Token:

I'm currently at work i don't have access to my pi. It can be provided in roughly 10h.

set your DHCP server (router) to serve only the pihole-IP as DNS server.
In pihole, set your desired DNS provider, or even better, install unboundto do local DNS resolution.

Now all your clients query pihole for DNS.

from your linux computer, test which dns is in use

dig iana.org @192.168.16.1 #if that's your router IP
dig iana.org @192.138.16.107

My experience is that tools like dnschecker.com often don't work.

Update: I hacked my ISP router to setup PiHole on it directly. I then tested dnsleak and it still outputted the dns of the isp. I installed unbound and forwarded Quad9 over tls and setup unbound on my PiHole. Dnsleaktest.com now outputs Unbound's DNS (Quad9 dns tls) successfully fixing my issue.

In short unbound is great and having unbound forward quad9 or any upstream of my choice over TLS was crucial step to have no dns leaks and a fully secure network.

Thanks. Look for reply above i've managed to fix the issue myself. Thanks for making me look into unbound that was helpful :heart: