Android says Private DNS cannot connect: what to check
Check the provider hostname, compare Automatic mode and test another connection before resetting Android network settings.
In brief
If a connection stopped working after you entered a Private DNS provider, check the provider hostname first. Android’s field expects a hostname, not a full web address with https:// or a path.
A DNS failure can make websites seem offline even while Wi-Fi remains connected. The Wi-Fi icon alone does not prove names are being resolved successfully.
Prepared from the linked primary documentation. Examples explain a procedure or calculation; they are not a device benchmark or a hands-on product review.
Check the text you entered
Compare the hostname character by character with the provider’s official setup page. Remove a copied web scheme or trailing path if the provider only specified a hostname. Do not substitute a random server suggested by an advertisement.
Write down the old value before testing. That gives you a clear way back and avoids forgetting which setting was originally working.
Documentation for these steps: Android Help — advanced network settings ↗ · Google Public DNS — Android Private DNS hostname ↗
Separate the provider from the network
Switch temporarily to Automatic and retry the same ordinary page. If it works, that points toward the explicit provider, its configuration or that network’s ability to reach it; it does not prove the provider itself is malicious.
Compare Wi-Fi with mobile data if available. A captive portal may need you to complete the network’s sign-in page, while a managed network may require its own settings. Ask its administrator rather than bypassing a workplace control.
Know when a wider reset is unnecessary
If one provider setting caused the issue, changing it is more targeted than resetting all saved networks and Bluetooth settings. If Automatic fails on several networks too, inspect the broader connection or service issue.
When contacting support, provide the selected DNS mode, nonsecret hostname, connection type and error wording. Do not send passwords, account tokens or a complete browsing history.
A hostname example and a simple decision table
For Google Public DNS, the documented Android hostname is dns.google. The Private DNS field takes that hostname, not https://dns.google/ and not a DNS server’s numeric IP address. This is an example of the required format, not a requirement to change your provider.
After each test, try the same ordinary website and record the result. If a workplace or school manages the connection, follow its support process. Do not reset Wi-Fi, Bluetooth and mobile settings together just to test one DNS field.
| Result | Next check |
|---|---|
| Automatic works; specified hostname fails | Typing, provider instructions and reachability on this network |
| Specified provider works on mobile data only | Wi-Fi sign-in portal or network restrictions |
| Neither mode works on multiple networks | Broader connection, VPN or device configuration |
| Only one website fails | That site or its app, rather than assuming all DNS is broken |
Documentation for these steps: Android Help — advanced network settings ↗ · Google Public DNS — Android Private DNS hostname ↗
Before you act
Private DNS protects DNS queries where supported; it is not a VPN and does not hide all traffic. A work network may have its own rules, and a provider can also have an outage.
What to do next
- Record the current Private DNS option and provider hostname.
- Open Settings > Network & internet > Private DNS; use settings search if the manufacturer places it elsewhere.
- Check the hostname against the provider’s official instructions, without https:// or a slash.
- Temporarily compare Automatic mode and try the same harmless page.
- Test another connection and restore your intended configuration once the cause is understood.
