DNS_PROBE_FINISHED_NXDOMAIN on Android: 5 Fixes (2026)

Seeing DNS_PROBE_FINISHED_NXDOMAIN on Android in Chrome and unable to open any website? The quick answer: this error means your phone’s DNS lookup failed — your device could not translate the website’s name into an address. It is almost always caused by a bad Wi-Fi connection, wrong DNS settings, or a stale browser cache, and you can fix it in under five minutes.

This 2026 guide explains what DNS_PROBE_FINISHED_NXDOMAIN means on Android and walks you through five tested fixes, from the 30-second airplane-mode toggle to changing your DNS servers. Every method below is written for current Android versions (Android 12 through 16) with exact menu paths.

What does DNS_PROBE_FINISHED_NXDOMAIN mean on Android?

DNS stands for Domain Name System — the phone-book of the internet that converts names like google.com into numeric addresses your phone can actually reach. When Chrome on Android shows DNS_PROBE_FINISHED_NXDOMAIN, it means the DNS “probe” finished with an “NXDOMAIN” result: the domain name could not be resolved to an address.

On Android, this almost never means the website is down. It means something between your phone and the DNS server broke the lookup. The most common culprits are:

A stale or dropped Wi-Fi connection. Your phone shows full signal bars but the underlying connection to the router is half-dead.
Bad DNS servers. Your ISP’s default DNS servers may be slow, misconfigured, or temporarily down.
Corrupted browser cache. Chrome’s stored DNS and site data can conflict with fresh lookups.
VPN or ad-blocker interference. VPN apps and DNS-filtering ad blockers reroute your DNS traffic and sometimes break it.
Router problems. An overloaded or long-running router stops forwarding DNS queries correctly.

The fixes below address each cause in order of likelihood. Start at the top — most users never get past Method 3.

How to fix DNS_PROBE_FINISHED_NXDOMAIN on Android: 5 methods

Method 1: Toggle airplane mode on and off

This 30-second reset forces your phone to drop every network connection and re-establish them cleanly, which clears most transient DNS failures.

Swipe down from the top of the screen twice to open the full Quick Settings panel.
Tap the Airplane mode icon to turn it on. Wait 15–20 seconds.
Tap it again to turn airplane mode off.
Wait for your Wi-Fi or mobile data icon to reappear, then reopen Chrome and retry the website.

If the site loads, you are done. If the error persists only on Wi-Fi but mobile data works, the problem is your Wi-Fi network — continue to Method 2.

Method 2: Forget and reconnect to the Wi-Fi network

Saved Wi-Fi profiles can hold onto stale DNS and gateway settings. Forgetting the network wipes them and forces a completely fresh connection.

Open Settings > Network & internet > Internet (on Samsung: Settings > Connections > Wi-Fi).
Tap the gear icon next to your connected Wi-Fi network.
Tap Forget (or “Forget network”) and confirm.
Wait 10 seconds, then tap the network name in the available list and re-enter the Wi-Fi password.
Once reconnected, open Chrome and test the website.

Still failing? The DNS servers themselves are the likely problem — Method 3 replaces them with fast, reliable public servers.

Method 3: Change your DNS servers

Switching from your ISP’s default DNS to Google’s (8.8.8.8) or Cloudflare’s (1.1.1.1) servers fixes DNS_PROBE_FINISHED_NXDOMAIN in a large share of cases, and it often makes browsing noticeably faster too. Android offers two ways to do this.

Option A — Private DNS (recommended, works on all networks):

Open Settings > Network & internet > Private DNS (on Samsung: Settings > Connections > More connection settings > Private DNS).
Select Private DNS provider hostname.
Type dns.google (for Google DNS) or one.one.one.one (for Cloudflare DNS) and tap Save.
Reopen Chrome and retry the site.

Option B — Per-network DNS (Wi-Fi only):

Go to Settings > Network & internet > Internet, tap the gear icon on your Wi-Fi network.
Tap the pencil/edit icon, then Advanced options.
Change IP settings from DHCP to Static.
In the DNS 1 field enter 8.8.8.8 and in DNS 2 enter 8.8.4.4 (or 1.1.1.1 and 1.0.0.1 for Cloudflare).
Tap Save and test.

Private DNS (Option A) is simpler and follows you between Wi-Fi and mobile data, so prefer it unless you have a reason to configure one network manually.

Method 4: Clear Chrome’s cache and data

Chrome stores DNS results and site data that can go stale and keep producing DNS_PROBE_FINISHED_NXDOMAIN even after the network is fixed. Clearing it forces completely fresh lookups.

Open Settings > Apps > See all apps > Chrome (on Samsung: Settings > Apps > Chrome).
Tap Storage & cache.
Tap Clear cache first and test the site.
If the error remains, return to the same screen and tap Clear storage (labeled “Manage space” > “Clear all data” on some phones). This signs you out of websites in Chrome but does not delete bookmarks if sync is on.
Reopen Chrome and retry.

To clear only the DNS cache without touching anything else, you can also type chrome://net-internals/#dns in Chrome’s address bar and tap Clear host cache.

Method 5: Restart the router and check your VPN

If every device on your Wi-Fi shows DNS errors, the router is the problem. And if only your phone is affected while a VPN or ad-blocker app is active, that app is intercepting your DNS.

Restart the router: unplug the router’s power cable, wait a full 30 seconds, plug it back in, and wait 2–3 minutes for all lights to stabilize. Reconnect your phone and test.
Check your VPN: open your VPN app and disconnect it completely, then test the website. If it loads, the VPN’s DNS servers were at fault — switch to a different VPN server location or enable the VPN’s own private DNS option.
Check ad-blocker apps: apps like Blokada or DNS66 filter DNS traffic. Pause them temporarily and retest. If the error clears, add your browser to the app’s bypass list or switch its upstream DNS to dns.google.
Test with mobile data: turn Wi-Fi off and load the site over mobile data. If it works there, the issue is isolated to your Wi-Fi network or router — consider the Private DNS setting from Method 3 as a permanent fix.

How to prevent DNS errors on Android

Keep Private DNS on permanently. Setting it to dns.google or one.one.one.one once prevents most ISP DNS outages from ever affecting you.
Restart your router monthly. Routers accumulate stale DNS cache over weeks of uptime; a monthly reboot keeps lookups fresh.
Keep Chrome updated. DNS handling bugs get fixed in updates — enable auto-updates in the Play Store.
Audit VPN and ad-blocker apps. After any VPN app update, quickly verify a website loads — updates sometimes reset DNS settings.
Avoid “DNS changer” apps you do not trust. Random DNS apps from the Play Store can hijack your traffic; use Android’s built-in Private DNS instead.

DNS problems and general connectivity problems often overlap — if your phone shows Wi-Fi connected but nothing loads at all, our guide to Windows 11 Wi-Fi connected but no internet explains the same troubleshooting logic for PCs, and most steps translate directly.

FAQs

What does NXDOMAIN actually stand for?

NXDOMAIN means “non-existent domain” — the DNS server’s way of saying it has no address record for the name you asked about. In the context of this error on Android, it rarely means the site does not exist; it means your phone never got a proper answer because the lookup itself failed.

Is DNS_PROBE_FINISHED_NXDOMAIN caused by a virus?

Almost never. It is a network configuration issue — bad DNS servers, a stale connection, or a corrupted browser cache. The one exception is malicious “DNS changer” malware or rogue apps that redirect your DNS; if the error appeared right after installing a suspicious app, uninstall it and reset your Private DNS setting.

Why does the error happen only on Wi-Fi and not mobile data?

Because Wi-Fi and mobile data use different DNS servers. Your mobile carrier’s DNS works fine while your home router or ISP’s DNS is failing. Setting Private DNS to dns.google fixes it on both, since it overrides whichever DNS your connection would otherwise use.

Will changing DNS to 8.8.8.8 make my browsing faster?

Often yes, slightly. Google’s and Cloudflare’s DNS servers typically answer faster than ISP defaults, so pages start loading sooner. The bigger win is reliability — public DNS servers have far less downtime than most ISP resolvers.

Does this error affect apps other than Chrome?

Yes, potentially. Any app that resolves domain names uses the same DNS settings, so a broken DNS configuration can break apps, email sync, and app updates too. The Private DNS fix in Method 3 repairs DNS for the entire phone, not just Chrome. If an app still fails after DNS is fixed, the app itself may have a separate issue — for example, see our guide on the “App Not Installed” error on Android.

Conclusion

DNS_PROBE_FINISHED_NXDOMAIN on Android sounds technical, but it is just a failed address lookup — and the fix is usually simple. Toggle airplane mode, forget and reconnect to Wi-Fi, switch to a reliable public DNS like dns.google, clear Chrome’s cache, and check your router and VPN. Set Private DNS once and leave it on, and this error should never bother you again.