Android Net Err_Name_Not_Resolved | Fix DNS And Get Back Online

You tap a link, the browser spins, then you get a message: this site can’t be reached. When the code reads net err_name_not_resolved, the problem is usually name lookup, not the website design, not your phone model, and not the app you opened. Your device asked a DNS resolver for the site’s IP number, and it didn’t get a usable answer.

The good news is that most fixes are simple. You’ll start with quick checks that catch typos and shaky connections. Then you’ll move into DNS settings that can break after a Wi-Fi change, a VPN toggle, or a router hiccup. By the end, you’ll know whether the issue sits on your phone, your network, or the site itself.

Why Android Net Err_Name_Not_Resolved Shows Up

URLs are names. Your phone still needs numbers to reach a server. DNS is the system that maps a hostname to an IP number. Chrome notes that ERR_NAME_NOT_RESOLVED appears when the hostname doesn’t exist or now points to a different IP number.

On Android, that can happen even when the site is fine. A cached record may be stale. Your Wi-Fi may be blocking or rewriting DNS. A Private DNS provider hostname may be mistyped. A VPN app can route DNS in a way that fails on one network but works on another. The browser only sees one thing: it can’t get a valid IP number for the name you typed.

Before you change settings, it helps to learn the pattern. If every site fails, the network path or DNS resolver is down. If only one site fails, the site’s DNS or your cached data for that site may be the trigger. If it fails on Wi-Fi but works on mobile data, your router or Wi-Fi DNS is the main suspect.

Fast Checks That Fix Most Cases

Start with moves that cost you a minute and don’t change anything permanent. These steps also help you narrow the cause, which saves time later.

• Check The URL — Re-type the domain, watch for extra dots, and check for a missing letter.
• Try Another Site — Open two unrelated sites. If both fail, treat it as a network or DNS issue, not a single-page issue.
• Switch Networks — Turn Wi-Fi off and use mobile data, or connect to a different Wi-Fi. A clean A/B test tells you where to aim next.
• Toggle Airplane Mode — Turn it on for 10 seconds, then turn it off. This forces a quick reconnect to cellular and Wi-Fi radios.
• Restart The Phone — A reboot clears temporary network state that can get stuck after long uptime.

If the problem started right after you joined a new Wi-Fi, open the Wi-Fi details page for that network. A proxy or a custom DNS entry can stick to one network and break lookups. Turn proxy off unless you know you need it.

• Turn Off Data Saver — Data Saver can restrict background traffic for some apps, which can make the first load fail after a restart.
• Pause Ad Blockers — DNS-based blockers or filtering apps can block a domain name and trigger the same error.

If the error appears only on public Wi-Fi, check for a sign-in page. Many hotspots require a browser login, and DNS may be limited until you accept terms. Open a plain http page, sign in, then retry the site.

Also check date and time. A wrong clock can break HTTPS, and that can look like “can’t reach” in some apps. Set date and time to automatic, then retry.

Fix Net Err_Name_Not_Resolved On Android With DNS Checks

When the quick checks don’t help, turn to DNS. On modern Android, Private DNS handles encrypted DNS on networks that can use it. Google’s Android help page notes that Private DNS is used by default on networks that can use it, and you can switch it off, keep it automatic, or set a provider hostname.

Run A Two-Step Test To Pinpoint DNS

A quick way to separate DNS from general connectivity is to test a hostname and then test a raw IP number. Google’s Public DNS guide suggests loading a normal hostname first, then trying a fixed IP number as a second test. If the IP number loads but the hostname does not, your data path works and DNS is the blocker.

1. Open A Normal Site Name — Load a site you trust by name in your browser.
2. Open A Fixed IP — If step one fails, try loading a known IP number in the browser to see if the network can reach servers at all.
3. Return To DNS Settings — If the IP test works, go back to Private DNS and router DNS settings.

Reset Private DNS To Automatic

If you set a custom provider in the past, a typo or a provider outage can trigger this error across many sites. Switching back to automatic is a safe first move.

1. Open Settings — Tap Settings, then go to Network & internet.
2. Find Private DNS — Tap Private DNS. If you can’t see it, use the Settings search and type Private DNS.
3. Select Automatic — Choose Automatic, then save.
4. Retry The Site — Close the browser tab, reopen it, and test again.

Set A Known Provider Hostname

If your network’s DNS is flaky, setting a trusted resolver can help. Google Public DNS can be used with Android Private DNS via the hostname dns.google. Cloudflare’s docs list one.one.one.one as a Private DNS provider hostname on Android 9 or 10, and also list security.cloudflare-dns.com and family.cloudflare-dns.com for filtered modes.

• Use dns.google — Set Private DNS provider hostname to dns.google if you want Google Public DNS.
• Use one.one.one.one — Set Private DNS provider hostname to one.one.one.one if you want Cloudflare 1.1.1.1.
• Save And Test — Save, then open a couple of sites you trust.

If you use a VPN, test with it off. Google’s Public DNS guide notes that on Android 9, some VPN features can override Private DNS settings. If the error vanishes when the VPN is off, check the VPN’s DNS setting or try a different server.

Clear Browser And Network State Without Losing Data

DNS issues can live in more than one place. Android keeps network state, apps keep their own caches, and your router keeps a separate cache too. Clearing the right layer can fix the problem without wiping your phone.

Refresh Chrome’s Stored Data

If the error hits in Chrome only, clear Chrome’s cache first. This does not delete your phone photos or contacts. It may sign you out of some sites, so save any drafts in web forms before you clear.

1. Open App Info — Long-press Chrome, then tap App info.
2. Open Storage — Tap Storage & cache.
3. Clear Cache — Tap Clear cache, then restart Chrome.

If you use a different browser, do the same steps for that app. If all browsers fail, move on to network resets.

Reset Wi-Fi, Mobile, And Bluetooth Settings

Android includes a network reset that clears saved Wi-Fi networks, paired Bluetooth devices, and some cellular settings. It does not erase personal files, and it’s lighter than a factory reset. It’s a good step when DNS looks wrong across many apps.

1. Open Settings — Go to System, then Reset options.
2. Choose Network Reset — Tap Reset Wi-Fi, mobile & Bluetooth.
3. Reconnect — Join your Wi-Fi again and re-enter the password.
4. Test Two Sites — Try one big site and one smaller site to confirm name resolution works.

Router And Wi-Fi Fixes That Matter Most

If mobile data works but Wi-Fi fails, your phone is doing its job. The trouble is between your router and the DNS resolver it uses. Many routers ship with ISP DNS by default, and some ISP resolvers can be slow to update or block certain names.

Restart The Router The Right Way

• Power It Off — Unplug the router for 20 seconds.
• Power It On — Plug it back in and wait for Wi-Fi to return.
• Forget And Rejoin Wi-Fi — On Android, forget the network, then join again.

This clears many short-term glitches, including a stuck DNS forwarder inside the router.

• Disable Router Filters — Parental controls, DNS filtering, or “safe browsing” switches on the router can block names in a way that shows up as name lookup failure.

Change DNS On The Router

If you control the router, setting a public resolver can fix repeat issues for every device on that Wi-Fi. Google Public DNS lists 8.8.8.8 and 8.8.4.4 as its IPv4 resolver IP numbers. Cloudflare lists 1.1.1.1 and 1.0.0.1 as its IPv4 resolver IP numbers.

Symptom	Likely Cause	What To Try
Only one site fails	Site DNS issue or cached record	Try later, test on mobile data, clear browser cache
Wi-Fi fails, mobile works	Router DNS or hotspot login	Restart router, sign in to Wi-Fi, set Private DNS
All networks fail	Phone network stack or VPN DNS	Turn VPN off, reset Private DNS, run network reset

If you can’t edit the router, Private DNS on your phone can still route DNS through a provider hostname, so you get steady name resolution even on a messy Wi-Fi.

When The Problem Is Not On Your Android

Sometimes you do everything right and the site still won’t resolve. That usually means the site’s DNS is broken or the domain expired. Chrome’s own error help points out that the hostname may not exist, which can happen when a domain is dropped or a record is removed.

If you only see the error for a single domain on a single device, it can also be a stale record in one cache layer. Try waiting a few minutes, then try again after a phone restart. DNS records change over time, and caches refresh on their own once their timer expires.

To confirm, test the same site on a different device and a different network. If it fails everywhere, the site is the issue. If it fails only on your Wi-Fi, your network is blocking it. If it fails only on your phone, go back to DNS and VPN settings.

If you manage the site, check its DNS records at the registrar or DNS host and confirm the nameserver set is correct. If you don’t control it, your best move is to wait or message the site owner through another channel.

You’ll see android net err_name_not_resolved again at some point, because DNS is a shared system with caches at every layer. With the checks above, you can fix it fast and also spot when the fix is out of your hands.