I have the phone added as a client with the Default group assigned. I couldn't change the DNS on my router, so I disabled the DHCP on it and enabled it on Pi-hole, this is working fine.
I have set both DNS1 and DNS2 entries on my Samsung S24 Ultra to the address of my pi-hole (192.168.1.253), it doesn't work, when i the an nslookup from the phone on ads.google.com it traces to its address instead of 0.0.0.0 using dns 8.8.8.8.
There's also an option for a private DNS, but I haven't enabled it, it's set to disabled. I tried pi-hole.lan but this didn't work, even though this is pingable and resolves to my pihole ip.
Actual Behaviour:
[ they disappear in my PC browser or even the TV, but not on my Samsung S24 Ultra phones]
Android devices are not the best platforms for analysing DNS issues.
Terminal apps often would use hardcoded DNS servers, ignoring the ones provided by your network.
If you open a browser on your phone and visit https://discourse.pi-hole.net, do your phone's corresponding DNS requests register in your Pi-hole's Query Log?
But then regular requests like to https://discourse.pi-hole.net, do not show up on the non-blocked or blocked list....
While they always show up when accessed from a PC....
Android devices have an option called Private DNS. When this option is enabled, they use DNS-over-HTTPS (DoH) DNS-over-TLS (DoT).
The DNS servers you set in your network settings are only used to resolve the DoT-Server and then devices uses the DoT server to resolve DNS queries instead of your Pi-hole.
Thank you stonerl!
That's what I found as well poking around a bit. There are excellent free private DNS addresses available and that's what I used for my android phones. Works great.
