DEV Community

Creto Si
Creto Si

Posted on Originally published at dubydex-blog.wasmer.app

Private DNS Server Cannot Be Reached on Android: What to Do and How to Fix It

#android #privacy #tutorial

By Creto Si · 11 November 2026

You set up Private DNS on your Android phone to block ads and trackers, but suddenly your internet stops working and you see the dreaded message:

"Private DNS server cannot be reached"

Don't panic. This is one of the most common Private DNS errors, and it's usually easy to fix. It doesn't mean your phone is broken, and it doesn't mean you set up Private DNS wrong.

In this guide, you'll learn what that error means, why it happens, and every fix that works — from checking for a simple typo to switching networks, trying a different provider, and resetting your network settings.

What Does "Private DNS Server Cannot Be Reached" Mean?

That message means your phone tried to connect to the Private DNS provider you configured (for example dns.adguard-dns.com, one.one.one.one, or a custom host), but couldn't establish a secure connection.

In plain language: Android tried to talk to your chosen DNS server over an encrypted (TLS) connection, and the server didn't respond — or your network blocked it.

When this happens:

  • You may lose internet access entirely, or
  • The phone may silently fall back to your ISP's regular DNS — which is less private and may stop blocking ads, or
  • Some apps may fail to load while others work

The good news: the fix is usually simple.

Why Does This Error Happen? (Common Causes)

The error is usually caused by one of these 6 things:

1. A typo in the hostname

This is the most common cause. A tiny mistake will break it.

  • dns.adguard.com — wrong. It's dns.adguard-dns.com
  • dns.adguard-dns.com/ — has an extra trailing slash. Remove it
  • https://dns.adguard-dns.com — wrong. Don't include https://
  • dns.adguard-dns.com — has an invisible trailing space

Correct format: just the hostname and nothing else. dns.adguard-dns.com

2. The DNS provider is down or unreachable

Even major providers have occasional outages. If AdGuard, NextDNS, or Cloudflare is having an outage, your phone can't connect.

How to test: Try a different provider (e.g. one.one.one.one). If that works, the first provider is having an issue.

3. Your Wi-Fi network blocks Private DNS

Some networks — especially schools, offices, hotels, airports, libraries, and some public Wi-Fi — block encrypted DNS (DoT port 853) to enforce their own filtering or monitoring.

Remember: on a network like this, the error appears only on that Wi-Fi network. It works fine on mobile data or other networks.

4. VPN conflicts

Some VPNs take over DNS resolution and block Private DNS entirely. If you use a VPN, the conflict can cause this error.

5. A bug or stuck connection

Sometimes Android keeps trying to use a dead DNS connection after you disconnect from a network. Restarting your phone or toggling Airplane Mode often clears it.

6. The provider's hostname isn't a valid Private DNS hostname

Some DNS services are not compatible with Android Private DNS. A service might offer dedicated DNS addresses (94.140.14.14) but only a hostname works on Android Private DNS. Enter the exact hostname the provider lists for "Android Private DNS" or "DNS-over-TLS" — not an IP address.

Quick Fix: Try These First (in Order)

Try these quick checks first — most people fix the error within a few minutes.

Step 1: Check for typos

  1. Go to Settings → Network & Internet → Private DNS (or Connections → More connection settings → Private DNS on Samsung).
  2. Look at the hostname. It should be exactly:
    • dns.adguard-dns.com (AdGuard)
    • one.one.one.one (Cloudflare)
    • dns.google (Google)
    • family.adguard-dns.com (AdGuard Family)
  3. Make sure there are no spaces, no https://, no trailing slash.
  4. Re-enter it carefully if you're unsure.

Step 2: Toggle Airplane Mode

  1. Pull down the Quick Settings panel.
  2. Turn on Airplane Mode for 10 seconds.
  3. Turn it off.
  4. Wait for Wi-Fi / mobile data to reconnect.
  5. Check if the internet works again.

Step 3: Restart your phone

Sometimes a simple restart is the fix. Restart, wait for the phone to boot up, then try again.

Step 4: Switch networks (Wi-Fi ↔ mobile data)

  • If it only fails on Wi-Fi: The Wi-Fi network may be blocking Private DNS. Try mobile data. If mobile data works, you've found the culprit.
  • If it only fails on mobile data: Try Wi-Fi.

Step 5: Try another provider

Switch to a different hostname:

  1. Go back to the Private DNS setting.
  2. Enter one.one.one.one.
  3. Save and test.
  4. If that works, your original provider may be down or blocked on your network.

More Fixes If the Error Persists

Fix 1: Turn Private DNS off temporarily

If you're in a hurry and need internet now:

  1. Go to Settings → Private DNS.
  2. Select Off.
  3. Tap Save.

Your internet will work instantly using your network's default DNS. You can re-enable Private DNS later once you've diagnosed it.

Fix 2: Try a different DNS-over-TLS provider

Some providers have better uptime than others.

Provider Hostname Notes
Cloudflare one.one.one.one Fast, very reliable
AdGuard dns.adguard-dns.com Blocks ads and tracking
Google dns.google Reliable, no ad blocking
NextDNS xxxxxx.dns.nextdns.io Requires your unique ID
ControlD freedns.controld.com Blocks ads and trackers

Fix 3: Clear the DNS cache

Android doesn't have a manual "clear DNS cache" button, but a restart clears the cache. For browsers:

  • Chrome: Go to chrome://net-internals/#dns and tap Clear host cache.

Fix 4: Update your phone

Go to Settings → System → System update and install any pending updates. Android updates sometimes fix Private DNS bugs.

Fix 5: Forget and rejoin the Wi-Fi network

  1. Go to Settings → Wi-Fi.
  2. Long-press your network → Forget.
  3. Reconnect (enter the password again if needed).
  4. This clears any stale DNS settings tied to that network.

Fix 6: Reset network settings

This is the nuclear option — it will erase all Wi-Fi passwords and Bluetooth pairings.

  1. Go to Settings → System → Reset Options (on Samsung go to Settings → General Management → Reset).
  2. Tap Reset Wi-Fi, mobile & Bluetooth (or Reset network settings).
  3. Confirm and restart your phone.
  4. Reconnect to Wi-Fi.
  5. Re-enter your Private DNS hostname.

Should I use this? Only if you've tried everything else.

Fix 7: Contact your network admin

If the error appears only on your work, school, or public-Wi-Fi network, the network may be deliberately blocking Private DNS. Ask the network admin if there's a permitted DNS hostname or policy.

Should I Turn Off Private DNS?

It's worth keeping Private DNS on if you've got it working — it encrypts your DNS traffic and (with an ad-blocking provider) blocks trackers.

But there are legitimate cases for turning it off:

  • Using a specific network that blocks encrypted DNS (school/work)
  • Using a VPN that conflicts with Private DNS
  • Troubleshooting — turn it off temporarily to test
  • Some banking or corporate apps detect Private DNS and block access (rare)

The bottom line: it's not permanent. You can toggle it on/off at any time.

Private DNS vs. Automatic vs. Off

Setting What it means When to use
Off No encryption; uses your ISP's regular DNS. Temporary troubleshooting, or networks that block encrypted DNS
Automatic Tries to use encrypted DNS if your network offers it — most networks don't. Default if you don't want to choose a provider
Private DNS provider hostname Uses your chosen provider (AdGuard, Cloudflare, etc.). Best privacy and ad-blocking — the recommended setting

Frequently Asked Questions (FAQ)

What does "Private DNS server cannot be reached" mean?

It means your phone couldn't connect to the Private DNS provider's server over an encrypted connection. It's usually one of these: a typo in the hostname, the provider being down, your Wi-Fi blocking Private DNS, or a VPN conflict.

Why does it say "cannot be reached" when my internet works fine without Private DNS?

Private DNS uses encryption (TLS on port 853) to talk to the provider. If that port or the provider is blocked, you get this error — even though your normal internet (regular DNS) works.

Will I lose internet if Private DNS fails?

You may lose some or all internet access, or your phone may fall back to your default DNS. To restore instantly, switch Private DNS to Off.

Do I need to restart my phone after changing Private DNS?

Usually not. Changes take effect immediately. But if you've had connection issues, a restart can clear stuck connections.

Which DNS provider should I use?

Start with Cloudflare (one.one.one.one) for speed and reliability, or AdGuard (dns.adguard-dns.com) if you want ad and tracker blocking.

Can a VPN cause "Private DNS server cannot be reached"?

Yes. Some VPNs take over DNS and conflict with Private DNS. If you see the error while the VPN is on, try turning the VPN off — or disable Private DNS while the VPN is active.

Final Thoughts

The "Private DNS server cannot be reached" error looks scary, but it is almost never a serious problem. In most cases it's a small typo, a temporary outage, or a network blocking encrypted DNS.

Quick recap:

  1. Check the hostname letter by letter.
  2. Toggle Airplane Mode or restart your phone.
  3. Try a different network.
  4. Try a different provider (e.g. one.one.one.one).
  5. Turn Private DNS off temporarily if you need internet now.

That five-step process should resolve the issue for nearly everyone.

Originally published on Dubydex Blog: https://dubydex-blog.wasmer.app/private-dns-server-cannot-be-reached-android-fix/

Top comments (0)