Debug token: r4qjfi1p8q
- Raspberry Pi 4
- Ubuntu-Mate 20.04.
- Standard Pi-Hole installation.
- Router: dd-wrt
- Dnsmaq: enabled (all other dnsmasq options disabled)
- Additional dnsmasq options:
- Router local DNS: 0.0.0.0
- Router Static DNS: 0.0.0.0 in all fields
- Static leases assigned on router for all devices.
Pi-Hole functions as expected blocking ads on all attached network devices.
However, it doesn't block ads when browsing on the Raspberry Pi that hosts Pi-Hole.
Standard Mozilla Firefox browser:
- I've turned off all the features that might interfere with Pi-Hole.
- Enhanced Tracking Protection": fully disabled.
- Deceptive Content and Dangerous Software Protection": disabled
- HTTPS-Only Mode": disabled.
Also checked using Chromium browser with all 'protection' features turned off: same result.
Pi-Hole Dashboard: under Tools > Network: the Pi-Hole displays in the Green area as an active device - albeit with very few queries.
I notice in the de-bug log that DNS server 126.96.36.199 is being used... but i've no idea where that's set from? Unless Firefox is somehow causing that?
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] x-us.appbaqend.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] x-us.appbaqend.com is 0.0.0.0 via Pi-hole (192.168.49.142)
[✓] doubleclick.com is 188.8.131.52 via a remote, public DNS server (184.108.40.206)
Is there anything obvious I'm missing, or doing wrong? Or is this expected behaviour - that the Pi-Hole server doesn't effectively block ads on itself. Thanks for looking.