I have a home network with an internal DNS resolver. I have some subdomains (public) that maps to a real world IP address, and maps to the home server private address when inside home.
In short, i use unbound and have added some local-data entries so that when at home, those subdomains points to 192.168.x.y instead.
All works perfectly fine from Windows and from Linux PCs.
Android, instead, doesnt work.
With dynamic DHCP allocation on android, the names cannot be resolved (ping will fail…) from the android devices. With specific global DNS servers (like dns.adguard.com) of course will always resolve to the public IP.
The only solution i found is to disable DHCP for the Wifi on android and set a static IP with the 192.168.x.y as DNS server, in this case it will work.
But why? Aynbody has any hints?
It’s like Android has some kind of DNS binding protection enabled by default, but i cannot find any information at all.
It’s blatantly ignoring the DNS i set via DHCP it seems. Only if i set it manually (static) it will use it! I have no subnets
Does a PC connected to the same wifi network as the phone get the proper DNS servers and work like it should?
Yes, perfectly… My guess is android bypass local resolver and goes via DoH l, which sucks hard
If you have private DNS turned off it doesn’t, unless maybe you have some manufacturer specific weirdness going on with extra software.
Well, my experience is that unless you set static IP+DNS in android WiFi advanced networks, it will not obey the dhcp option 6.
LineageOS, vanilla with mind the gapps
Odd, I’ve had a Pixel, Oneplus 7 pro, and now a Galaxy S21 and they all pick up my DNS server from DHCP without any issues.