Browsing along and suddenly Chrome throws up DNS_PROBE_FINISHED_NXDOMAIN and the site won't load? Don't panic. This is a very common problem and most of the time you can fix it yourself in a few minutes. This article covers the causes and step-by-step fixes you can actually follow, on every device.
We start by explaining what this error is and what causes it, then work through the fixes from easy to advanced — flushing the DNS cache, changing DNS to 8.8.8.8 or 1.1.1.1, restarting the device, checking the hosts file, and checking whether the problem is on the domain/hosting side. It includes separate steps for Windows, Mac, Android, iOS, and Chrome.
What Is DNS_PROBE_FINISHED_NXDOMAIN?
DNS_PROBE_FINISHED_NXDOMAIN is a browser error message (common in Chrome and Edge). The word NXDOMAIN stands for "Non-Existent Domain," meaning the browser tried to look up the IP address of the domain you typed through DNS but could not find it, so the site could not load.
Put simply, DNS responded with "I don't know this domain." This can happen for many reasons — from a typo, to a stale DNS cache, to a problem with your device's DNS settings, all the way to the domain itself being expired or not fully configured. The good news is that most of the time it is a problem on your own device that you can fix yourself.
Common Causes
Before diving into fixes, knowing the common causes helps you guess where the problem likely is and fix it more precisely.
- A mistyped URL or a misspelled domain name
- A stale DNS cache lingering on your device or in the browser
- A problem with your device/router DNS settings, or your ISP's DNS being down
- The hosts file being edited to block or misdirect the domain
- A VPN, proxy, or antivirus program interfering with the connection
- The domain side itself — such as an expired domain, a misconfigured DNS record, or being mid-propagation
Try the Basics First (Always Start Here)
Before going deep, try these simple steps first — often that is all it takes. They work on any device.
- Check that you typed the site name correctly; try retyping it or accessing it from a trusted link.
- Try opening another site. If other sites load fine, the problem is likely specific to that one domain.
- Try switching networks, such as from Wi-Fi to mobile data (or vice versa), to see whether the problem is with the network.
- Turn off any VPN/proxy and temporarily disable antivirus software to test.
- Restart your router and device — the classic move that works more often than you'd expect.
Flush the DNS Cache on Each Device
A stale DNS cache is one of the top causes. Flushing the cache forces your device to fetch fresh DNS data. Follow the command for your system.
| Device | How to flush the DNS cache |
|---|---|
| Windows | Open Command Prompt (Run as admin), type ipconfig /flushdns, then Enter |
| Mac | Open Terminal, type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder |
| Android | Toggle Airplane mode on briefly then off, or restart the device / clear the browser app cache |
| iOS | Toggle Airplane mode on briefly then off, or restart the device |
| Chrome | Go to chrome://net-internals/#dns and click Clear host cache |
Change DNS to 8.8.8.8 or 1.1.1.1
If your ISP's DNS is having problems, switching to a stable public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) often fixes NXDOMAIN. Here is how to set it up per device.
| Device | Where to set DNS |
|---|---|
| Windows | Settings → Network & Internet → select the connection → Edit DNS → enter 8.8.8.8 and 8.8.4.4 |
| Mac | System Settings → Network → select the network → Details → DNS → add 1.1.1.1 or 8.8.8.8 |
| Android | Wi-Fi → long-press the network → Modify → set IP settings to Static, then enter DNS (or use Private DNS) |
| iOS | Settings → Wi-Fi → tap (i) on the network → Configure DNS → Manual → add 8.8.8.8 / 1.1.1.1 |
Check the Hosts File and Restart Network Services
If the steps above didn't help, the hosts file may have been edited to misdirect or block the domain (sometimes by malware or an installed program). This file overrides DNS, so it can make certain sites unreachable even when DNS is fine.
On Windows, the file is at C:\Windows\System32\drivers\etc\hosts; on Mac/Linux it is at /etc/hosts. Open it with admin privileges and check whether there is a line specifying the domain you cannot reach. If there is a strange line pointing that domain to the wrong IP, remove it (comment it with # or delete the whole line) and save.
- Windows: open Notepad as administrator, open the hosts file, and check/remove any line misdirecting the domain
- Mac/Linux: in Terminal, type sudo nano /etc/hosts, check/edit, then save
- After editing the hosts file, flush the DNS cache again
- Windows extra: try resetting the network stack with netsh winsock reset and netsh int ip reset, then restart
When Is It a Domain/Hosting-Side Problem?
If you have tried everything and one site still shows NXDOMAIN while all others load fine — and other people or networks also can't reach that site — then the problem is likely on the domain/hosting side of that site, not on your device.
Common owner-side causes include an expired domain (forgot to renew), a misconfigured DNS record or nameserver, or a recent settings change that is still mid-propagation. If you are the site owner, check the following.
- Verify the domain has not expired and that renewal is complete
- Check that the nameservers and A record point to the correct hosting/VPS IP
- If you just changed DNS, wait for propagation (a few minutes to 24-48 hours) and try again
- Test with an online DNS checker, or ping/nslookup, to see whether the domain returns an IP
- If unsure, contact your hosting/domain provider to help investigate
Is your site unreachable because of the domain/hosting?
Prevent DNS problems and downtime with a stable domain + Web Hosting from Plusweb — LiteSpeed, NVMe, free SSL, 99.9% uptime, a data center in Thailand, and a support team to help check your DNS. Starting at ฿200/year.
Frequently Asked Questions
How do I fix DNS_PROBE_FINISHED_NXDOMAIN as fast as possible?
Start by flushing the DNS cache (Windows: ipconfig /flushdns), change DNS to 8.8.8.8 or 1.1.1.1, restart your router and device, and clear the host cache in Chrome at chrome://net-internals/#dns. Most cases are fixed in a few minutes.
What causes this error?
NXDOMAIN means the DNS system cannot find the domain you typed. It is usually caused by a typo, a stale DNS cache, a DNS settings problem, an edited hosts file, or the domain side itself — such as an expired domain or misconfigured DNS.
How do I flush the DNS cache on Windows?
Open Command Prompt as administrator, type ipconfig /flushdns, and press Enter, then try loading the site again. If it still fails, try netsh winsock reset and restart the device.
How do I fix NXDOMAIN on Android/iOS mobile?
Try toggling Airplane mode on briefly then off, or restart the device to flush the DNS cache. Switch between Wi-Fi and mobile data to test, and set DNS to 8.8.8.8 or 1.1.1.1 in the network settings.
What if only one site fails but all others load fine?
That means the problem is likely on that site's domain/hosting side — such as an expired domain, a misconfigured DNS record, or mid-propagation. If you are the site owner, check the domain renewal and DNS settings, or contact your provider.
GUIDES
Related articles
Keep reading on similar topics
What Is DNS? Explained Simply in 8 Minutes
A complete rundown of DNS — what it is, how it works (like the internet's phone book), what a DNS server is, the types of DNS records (A, AAAA, CNAME, MX, TXT, NS), how to point a domain to hosting, how to change DNS, and DNS propagation.
Read more
What Is a Domain? A Beginner-Friendly Guide
A complete, plain-English rundown — what a domain name is, the parts of a domain (TLD vs ccTLD vs subdomain), how domains work together with DNS and hosting, and everything you need to know before registering your first domain.
Read more
Where Should You Register a Domain? The Complete Guide
What should you actually look for when registering a domain? A full rundown of registrar selection criteria — renewal pricing, domain transfers, DNS management, and ownership — plus a step-by-step guide to registering a .com and the pricing traps to watch out for.
Read more