Android says Private DNS cannot connect? Check the custom provider first

If your Android phone connects to Wi-Fi but reports that its Private DNS server cannot be reached, check whether you configured a custom DNS provider before resetting the phone or router. This guide focuses on that warning; an ordinary Wi-Fi outage needs a broader diagnosis.

The steps below follow Google’s documentation. Menu names vary by manufacturer and Android version; these are documentation-based instructions, not a claim of hands-on testing on your phone.

1. Record the warning and compare the connection

Write down the exact message and which network is affected. Try loading two familiar websites, then check whether another device can load them on the same Wi-Fi. Do not enter passwords into a page displaying a certificate warning.

If your mobile plan allows it, briefly turn Wi-Fi off and retry those sites using mobile data. Data charges and roaming limits still apply; avoid downloads or speed tests. Re-enable Wi-Fi afterward.

What you observe	Useful next branch
Several devices fail on the same Wi-Fi	Investigate the network first using our connected-but-no-internet guide.
Only this phone fails, and the warning names Private DNS	Inspect its Private DNS selection below.
The phone works on mobile data but fails on one Wi-Fi network	A network-specific problem is possible. This comparison alone does not prove that DNS is the cause.
Only one website or app fails	Keep the scope narrow; do not reset every network setting for a single failing service.

2. Inspect the selected Private DNS option

Open Settings → Network & internet → Private DNS. If that route is absent, search Settings for Private DNS. Google’s advanced Android network settings guide lists Automatic, Off and Private DNS provider hostname as the available choices.

Record the current choice and, if present, the full custom hostname so you can restore it. Keep account-specific hostnames private when sharing screenshots. If the phone is managed by work, school or a parent, ask the administrator before changing a required setting.

If a provider hostname is selected, compare it character by character with that provider’s official setup instructions. This field expects a hostname, not a website URL with https:// or an ordinary numeric DNS address. Correct a confirmed typo using the provider’s documented value, save, and repeat the same two-site check. Do not copy an unfamiliar resolver from a forum.

3. Understand the tradeoff before comparing Automatic

Changing from a custom provider can remove its filtering and change who handles DNS requests. Automatic does not guarantee the same encrypted connection as a working explicit provider configuration. If you rely on that provider for parental controls, required filtering or privacy, stop and contact its support team rather than bypassing it.

On a personal phone where you understand that tradeoff, you can compare the custom setting with Automatic: record the original hostname first, choose Automatic, tap Save, and retry the same sites on the same Wi-Fi. Do not change the VPN, browser settings and router at the same time.

If sites now load and the warning disappears, the result points toward the custom DNS configuration or its connection path. It does not establish whether the provider is down, the network blocks the connection, or the original value was wrong. If nothing improves, restore your recorded setting and investigate beyond DNS. Google recommends keeping Private DNS enabled where supported; turning it Off is not the routine fix here.

4. Resolve the cause and verify the final setup

Check the DNS provider’s official service notices or ask support about the exact hostname and affected network. If only one Wi-Fi network fails, give its administrator the warning and comparison results. An active VPN or DNS app is also relevant evidence; report it without disabling required protection.

When the underlying issue is resolved, restore your intended provider if appropriate and test both sites again. A successful page load does not prove that filtering or DNS encryption is working. Use your provider’s documented verification method for those separate checks.

Google’s Public DNS setup documentation explains Android’s hostname-based configuration and the need to preserve original settings. Private DNS protects DNS exchanges, not all phone traffic. For shared networks, also follow our public Wi-Fi safety checklist.

Useful support notes: phone model, Android version, exact warning, affected Wi-Fi network, whether mobile data worked, and whether a custom hostname was selected. These observations are more useful than a factory reset performed before the cause is understood.