The “Private DNS server cannot be accessed” message on Android usually means the phone can not reach the Private DNS provider configured in its network settings. If a custom Private DNS hostname is being used, the fastest test is to temporarily switch the setting to Automatic. If internet access immediately returns, the custom hostname, DNS provider, or its connection through the current network is the main place to investigate.
Google provides three Private DNS choices on supported Android devices: Off, Automatic and Private DNS provider hostname. Google also recommends keeping Private DNS enabled rather than permanently switching it off simply to solve a connection problem.
What Does “Private DNS Server Can not Be Accessed” Mean?
DNS helps a device translate website and service names into the network addresses needed to reach them. Android’s Private DNS feature can protect compatible DNS queries using an encrypted connection.
When a user manually enters a Private DNS provider hostname, Android needs to establish a working connection with that provider. Google’s explanation of DNS over TLS support in Android notes that Android can mark a network as having no internet access when a manually configured Private DNS server cannot be reached.
This is why the Wi-Fi icon may still appear connected while websites and apps struggle to load.
First, Switch Private DNS to Automatic
Open the Android settings and search for Private DNS. On many phones, Google lists the path as:
Settings → Network & internet → Private DNS
Menu names can differ between manufacturers.
Before changing the setting, save or write down the custom provider hostname. Then select Automatic, save the change, and test several websites or apps.
If the connection now works, the test has already narrowed the problem considerably. The custom hostname may be incorrect, the DNS provider may be temporarily unreachable, or the current network may be preventing the phone from reaching it.
Google’s Private DNS settings guide recommends keeping Private DNS turned on. Therefore, if Automatic works, there is usually no reason to leave the feature completely disabled while investigating the custom provider.
If switching to Automatic makes no difference and the phone still can not access the internet normally, Private DNS may not be the main problem.
What If Private DNS Works on Mobile Data but Not Wi-Fi?
Turn Wi-Fi off temporarily and test the phone using mobile data with the same Private DNS configuration.
If the custom Private DNS works normally on mobile data but fails as soon as the phone reconnects to one particular Wi-Fi network, that strongly points toward the Wi-Fi network or the route between that network and the DNS provider rather than a general problem with the phone.
Restart the router, reconnect the phone, and test again. Google also recommends comparing Wi-Fi and mobile data when diagnosing Android internet connection problems.
If the whole home network repeatedly disconnects, disappears, or fails across several devices, do not keep changing Private DNS settings. That indicates a broader network problem, and the separate ItsLatest guide on why home Wi-Fi keeps dropping is a more relevant troubleshooting path.
If Private DNS fails on both Wi-Fi and mobile data but Automatic works on both, the custom provider or its hostname becomes a stronger suspect.
Can a VPN Interfere With the Test?
An active VPN can use its own network routes or DNS configuration, so temporarily disconnecting the VPN can help determine whether the problem is tied to the VPN rather than Android’s Private DNS setting.
Android’s VPN developer documentation confirms that VPN applications can configure DNS servers and route traffic through a VPN interface.
This does not mean a VPN automatically causes the Private DNS error. The useful test is simply to change one variable at a time. If Private DNS starts working immediately after the VPN is disconnected, check that VPN provider’s DNS and networking documentation before permanently changing Android’s system settings.
The same principle applies if the problem began after enabling a parental-control, firewall or network-filtering application.
What If Automatic Mode Does Not Fix the Problem?
If Automatic mode does not restore connectivity, test whether ordinary internet access is failing more broadly.
Reconnect Wi-Fi, try mobile data, restart the phone, and check whether other devices can use the same network. If multiple devices cannot access the internet, the router or internet connection deserves attention before Private DNS.
If only one phone is affected on several different networks, device-level network settings or software become more relevant.
Avoid changing several settings simultaneously. Resetting the router, replacing the DNS provider, disabling a VPN and changing Android network settings at the same time may restore the connection, but it will not reveal which change actually solved the problem.
Should You Turn Private DNS Off?
Turning Private DNS off briefly can be useful as a diagnostic test, but it should not be the automatic permanent solution.
Google’s Android Private DNS documentation recommends keeping Private DNS enabled. It also clarifies that Private DNS protects DNS questions and answers rather than encrypting every type of traffic on the phone.
If Automatic works while Private DNS provider hostname does not, leaving the phone on Automatic is generally more sensible while checking the provider hostname or service.
Also avoid copying unknown DNS hostnames from random troubleshooting posts. Android’s security guidance on DNS configuration recommends relying on the operating system’s DNS protections rather than unnecessarily introducing insecure custom configurations.
The most useful troubleshooting sequence is therefore straightforward: test Automatic mode first, compare Wi-Fi with mobile data, temporarily test without an active VPN, verify the provider hostname from its official documentation, and investigate the wider network only if those checks do not isolate the problem.
