Fix "Server DNS Address Could Not Be Found"

The call usually goes like this: "The internet is broken, but only for one website." Chrome shows a grey page, a small dinosaur, and the words Server DNS address could not be found, with DNS_PROBE_FINISHED_NXDOMAIN in smaller print underneath. Everything else loads fine. The person on the phone has already restarted the router twice.

I've fixed this error more times than I can count, and it almost never means what people fear. Nothing is wrong with Chrome, and the website usually hasn't vanished. Your computer asked for the site's address, and somewhere along the chain the answer came back as "no such place." That chain — your browser's cache, your operating system's cache, your router, your provider's resolver — has several links, and any one of them can be the liar. The whole job is finding which one.

First question: is it down for everyone, or just you?

Before touching a single setting, pick up your phone. Turn Wi-Fi off so the phone uses mobile data, and open the site. You just ran the most useful test in this entire guide, because you changed the whole network path in five seconds.

• The site loads on mobile data. The website is fine. Something between your computer and your provider's resolver is giving you a bad answer, and everything below will fix it.
• The site fails there too. Try one more site you use daily. If that loads, the problem is probably at the website's end — a lapsed domain registration, a botched DNS change, a host that pulled the plug. You can't fix that from your chair.
• Everything fails everywhere. That's not this error any more; that's your connection itself. Different problem, different guide.

If you want the same answer with more reach than your phone gives you, the DNS propagation checker queries public resolvers in several countries and shows whether they agree on the site's address. If resolvers around the world return NXDOMAIN, the site has a genuine DNS problem. If they all return an address happily, the bad answer is being produced somewhere close to you.

What the error actually means

DNS is the lookup that turns a name like example.com into the numeric address your browser actually connects to. This error means the lookup didn't come back empty by accident — the resolver actively reported that the name doesn't exist. That's what NXDOMAIN stands for, and our explainer on what NXDOMAIN means covers the response itself in depth.

Here's the part that trips people up: "doesn't exist" can be a true answer about a site that was deleted, or a stale answer your own equipment cached earlier and keeps repeating. The error message looks identical either way. That's why the fixes below go after caches and resolvers rather than the browser itself — reinstalling Chrome for this is like buying a new phone because one contact's number changed.

Match the symptom to the cause

The fixes, in the order I actually try them

1. 1

   Flush your DNS cache

   On Windows, open Command Prompt and run ipconfig /flushdns. On a Mac, it's sudo dscacheutil -flushcache in Terminal. This throws away your computer's stored answers, including the bad one, and forces a fresh lookup. It takes ten seconds and harms nothing, which is why it's always my first move.

2. 2

   Switch to a public resolver

   If the flush changed nothing, the bad answer is coming from upstream. Change your computer's DNS servers to a public resolver such as 1.1.1.1 or 8.8.8.8 and reload. If the site springs to life, your provider's resolver was the liar — leave the setting, or keep it until your provider sorts itself out.

3. 3

   Check the hosts file

   The hosts file overrides DNS completely. If a line in it maps the site's name to an old address — left there by old software, a past experiment, or something you pasted in years ago and forgot — no resolver change will matter, because your computer never asks. Open the file, look for the site's name, and remove or comment out any line you find.

4. 4

   Restart the router, once

   Routers cache answers too, and cheap ones do it badly. A single restart clears that cache and renegotiates the connection. I say once because restarting it four times in a row, which callers often confess to, does exactly what restarting it once does.

5. 5

   Turn the VPN off and retest

   A VPN reroutes your DNS queries to its own servers. If those are down, misconfigured, or the tunnel half-died while your connection stayed up, name lookups fail while everything looks connected. Disconnect fully — not pause, disconnect — and reload the page.

Two things people swear by that rarely help

Reinstalling the browser. The browser holds a small cache of its own, sure, but this error is generated by the system-level lookup failing, and a fresh install inherits the same resolver, the same hosts file, the same router. You'll spend twenty minutes restoring your bookmarks to arrive back at the dinosaur.

The other one is "wait 48 hours," repeated like a spell. Waiting does genuinely fix one scenario: the site really did change its DNS recently, and the old answer is still draining out of caches worldwide. Our guide to diagnosing "this site can't be reached" separates that waiting game from the faults you can fix yourself. But if the site loads on your phone today, waiting won't fix your network — the five steps above will, usually inside ten minutes.

When only one browser shows the error

Here is a variation that sends people down the wrong path for hours: the site fails in Chrome but loads fine in another browser on the same machine, same network, same minute. That one fact rules out your router, your provider, and the website in a single stroke. The difference lives inside the browser itself.

Modern browsers increasingly do their own lookups instead of trusting the system. Chrome has a Secure DNS setting that can send queries over an encrypted connection to a resolver the browser chooses, bypassing the one your computer is configured with; Firefox has a similar feature with its own defaults. If that browser-chosen path is broken — or simply holds a stale answer the rest of your system has already forgotten — you get this error in exactly one program while everything else works. Setting the browser's secure DNS to use the system resolver, or switching it off, is the two-minute test that settles it.

The reverse split is just as informative: every browser fails but a command-line lookup succeeds, which points back at something the browsers share — the system resolver settings, the hosts file, the network itself. One program versus all programs is the fastest way I know to locate which layer is holding the bad answer, and it is why my first question on these calls is never about settings. It is “does it fail everywhere, or only here?”

You can also interrogate resolvers one at a time instead of guessing. A command like nslookup example.com 1.1.1.1 asks one specific resolver for its answer, ignoring your defaults. Ask your usual resolver, then ask a public one. If the public resolver returns an address while yours returns NXDOMAIN, you have caught the liar in the act — and you know whether the remaining job is flushing, waiting, or changing the setting for good.

The same fault wears different costumes elsewhere, which confuses people searching for help. Android's Chrome calls it ERR_NAME_NOT_RESOLVED, Firefox says the server was not found, and Safari reports that it can't find the server. Different words, same event underneath: a lookup came back saying the name does not exist. If a fix in a guide for any of those messages is really about caches or resolvers, it applies to yours too — translate the error name, keep the method.

When it's genuinely not your problem

Sometimes my answer on these calls is: it's them, not you. A domain whose registration lapses gets its nameservers pulled, and every resolver on earth starts answering NXDOMAIN — the exact same error, now telling the truth. A site owner mid-migration can also publish a broken record and take the name down for everyone at once.

The giveaway is consistency. Your phone fails, your neighbour fails, and the local tricks in our guide to fixing the Windows DNS_PROBE_FINISHED errors change nothing — while public resolvers worldwide agree there is no address. At that point, close the settings tabs. There's nothing left to repair at your end; the site will come back when its owner fixes the record, or it won't come back at all.