Changing a DNS setting is only half the job. If you want to know which DNS server Android is actually using, verify the result after configuration—especially when a VPN, browser-level encrypted DNS or filtering app is installed.
Start with the Android Private DNS setting
Open Settings and search for Private DNS. If a provider hostname is selected, note it. Common examples are dns.google, one.one.one.one and dns.quad9.net.
This tells you what Android is configured to use, but it does not prove another app is not overriding the resolver.
Check provider-specific status pages
Some DNS providers publish a verification endpoint. Quad9, for example, tells Android users to visit on.quad9.net after setup. Provider pages are useful because they can confirm whether requests are reaching that service.
Test with Wi-Fi and mobile data separately
To understand where a DNS change applies:
- Test with Wi-Fi connected.
- Turn Wi-Fi off and test on 4G/5G.
- Compare the results.
A per-Wi-Fi DNS edit normally affects only that saved network. Android Private DNS is designed to work more broadly across networks.
Disconnect the VPN for a clean baseline
VPN applications may provide their own DNS and can make system settings misleading. First test with the VPN disconnected. Then reconnect it and test again. If the resolver changes, check the VPN’s DNS settings.
See Private DNS vs VPN on Android for why this happens.
Browsers can use their own encrypted DNS
Some browsers can enable DNS-over-HTTPS independently of Android’s system resolver. That means a browser test and an app test may produce different DNS paths. If you are troubleshooting system DNS, temporarily use a browser configuration that follows the operating system or verify with more than one app.
Do not rely on a single IP shown by a DNS test
Large DNS providers use distributed infrastructure. The resolver IP or location reported by a test may not look exactly like the public address you typed, and caches or network relays can complicate interpretation. What matters is whether the intended service is handling the query and whether the connection is stable.
Use an Android DNS testing workflow
If you are comparing multiple resolvers rather than only checking one, record latency across repeated tests on the same network. SSM APP’s DNS Changer & Net Speed Test is built around Android DNS and network testing.
If the configured resolver is not being used
- Check whether a VPN is active.
- Check whether the browser has its own Secure DNS/DoH setting.
- Confirm Private DNS saved successfully.
- Switch to mobile data to rule out a router DNS policy.
- Temporarily return to Automatic, then re-enter the hostname.
For connection errors, use the Private DNS troubleshooting checklist.
Official references
Featured image credit: Back of server.jpg by Tseilorin, licensed under CC BY-SA 4.0, via Wikimedia Commons.
Start the conversation
Corrections, useful experiences and focused questions are welcome. Keep discussion respectful and on topic.