
There are few things more frustrating than sitting down to work, browse, or stream, only to be met with a stark white screen and a confusing error message. If you are using Google Chrome, one of the most common culprits is the DNS_PROBE_FINISHED_NXDOMAIN error.
It sounds technical and intimidating, but don’t panic. This error rarely means your computer is broken or that the website you are visiting is gone forever. In most cases, it is a simple miscommunication between your computer and the internet’s address book.
In this guide, we will explain exactly what this error means and walk you through the most effective methods to fix it, ranging from simple quick fixes to slightly more advanced solutions.
To understand the fix, it helps to understand the problem.
The Internet relies on DNS (Domain Name System). Think of DNS as the phonebook of the internet. Humans remember domain names (like google.com or facebook.com), but computers rely on IP addresses (complex strings of numbers like 192.168.1.1) to locate servers.
When you type a URL into your browser, your computer sends a request to a DNS server to look up the IP address associated with that name.
Essentially, your browser is saying, "I looked for this website in the phonebook, but I couldn't find an entry for it."
This usually happens for one of three reasons:
Let's get into the solutions, starting with the easiest.
Before diving into settings, we need to rule out the basics. Often, the error is caused by a temporary glitch in your router or modem.
If this worked, it was likely a temporary IP conflict. If not, move on to the next step.
This is one of the most successful fixes for the NXDOMAIN error. This process clears out your current IP configuration and requests a fresh one from your router.
For Windows Users:
cmd.ipconfig /release ipconfig /renew ipconfig /flushdns
For Mac Users:
Once you have done this, restart your browser and try the website again.
By default, you use the DNS servers provided by your Internet Service Provider (ISP). While generally fine, ISP DNS servers can sometimes be slow, unreliable, or overly aggressive with filtering.
Switching to a public DNS server, like those provided by Google or Cloudflare, is often faster and can instantly fix NXDOMAIN errors.
How to change DNS on Windows:
8.8.8.88.8.4.4Click OK and close the windows.
How to change DNS on Mac:
8.8.8.8 and 8.8.4.4.Refresh your browser. If the error was caused by your ISP’s DNS struggling to find the site, it should load immediately now.
Even if you flush your computer's DNS (as we did in Fix 2), Google Chrome keeps its own internal DNS cache. We need to ensure Chrome isn't holding onto the "error" version of the website.
chrome://net-internals/#dnsThis doesn't give you a "success" message popup; it just clears the data silently. Once clicked, try visiting the website again.
This is a slightly more advanced step. Every computer has a "Hosts" file—a local file that can manually override DNS settings. Sometimes, malware or accidentally changed settings can block specific websites here.
C:\Windows\System32\drivers\etc\You will see a file with some text about IP addresses. Look for the website you are trying to visit. If you see a line like 127.0.0.1 example.com (where example.com is the site giving you the error), delete that entire line.
Save the file and close it.
The DNS_PROBE_FINISHED_NXDOMAIN error is essentially a navigational error—your browser knows where it wants to go, but the map is broken.
To recap, here is your checklist for fixing it:
In 99% of cases, one of these steps will get you back online. If you have tried all of these and the site still won't load, the issue is likely on the website owner's end (such as an expired domain), and there is nothing left to do but wait for them to fix it.