FixBrowsers

How to fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome

This Chrome error means the website's name could not be found. Check the address, then clear DNS caches and switch DNS servers to fix it.

Difficulty
Beginner
Time needed
5–10 minutes
Works on
Google Chrome on Windows and Mac (also Edge, Brave and other Chromium browsers)

Quick fix

DNS_PROBE_FINISHED_NXDOMAIN means your computer asked for a website's address and was told the name does not exist. First check the web address for typos and try another site. If only some sites fail, clear Chrome's DNS cache at chrome://net-internals/#dns, flush your computer's DNS, turn off VPN or ad-blocking DNS, and switch to a public DNS such as 1.1.1.1 or 8.8.8.8.

What you need

  • Google Chrome or another Chromium-based browser
  • Administrator access (Windows) or your Mac password for flushing DNS

What the error means

Every website name, such as example.com, has to be turned into a number (an IP address) before your browser can connect. That lookup is called DNS. DNS_PROBE_FINISHED_NXDOMAIN means the lookup finished and the answer was “this name does not exist”.

That can be true (a typo, or a website that has shut down) or it can be a problem on your side (a stuck cache, VPN, or a DNS server having trouble).

Step 1: Rule out the simple causes

  1. Check the address for typos, such as .con instead of .com.
  2. Open another website. If nothing loads, see our fix for Wi-Fi connected but no internet.
  3. Try the site on your phone using mobile data, not Wi-Fi. If it fails there too, the website itself is down or its domain has expired, and only the site owner can fix it.

Step 2: Clear Chrome’s DNS cache

  1. Type chrome://net-internals/#dns in the address bar and press Enter.
  2. Select Clear host cache.
  3. Go to chrome://net-internals/#sockets and select Flush socket pools.
  4. Reload the website.

Step 3: Flush your computer’s DNS cache

Windows: Right-click Start, open Terminal (Admin) and run:

ipconfig /flushdns

Mac: Open Terminal and run (enter your Mac password when asked; nothing appears as you type):

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Step 4: Turn off VPN, ad-blocking DNS and extensions

  • Disconnect your VPN and try again.
  • If you use a privacy or ad-blocking DNS service (or a Pi-hole at home), it may be blocking the domain. Pause it to test.
  • Open the site in an Incognito window (extensions are usually off there). If it works, turn off extensions one by one to find the culprit.

Step 5: Switch to a public DNS server

Your internet provider’s DNS might be failing. Switch to a free public DNS:

Windows 11: Settings > Network & internet > Wi-Fi (or Ethernet) > your network > Hardware properties > DNS server assignment > Edit > Manual > IPv4 on. Enter 1.1.1.1 and 8.8.8.8, then Save.

Mac: System Settings > Network > Wi-Fi > Details next to your network > DNS. Select + and add 1.1.1.1 and 8.8.8.8, then OK.

Chrome only: Settings > Privacy and security > Security > Use secure DNS, then choose a provider such as Cloudflare or Google.

Step 6: Check your hosts file (advanced)

Some apps add entries to the hosts file that send website names to the wrong place.

  • Windows: open Notepad as administrator and open C:\Windows\System32\drivers\etc\hosts.
  • Mac: run sudo nano /etc/hosts in Terminal.

Lines that do not start with # are active. If you see the website you are trying to visit, put # at the start of that line, save and try again. Only change lines you understand.

Step 7: Restart your router

Your router may also cache DNS. Unplug it for 30 seconds, plug it back in and wait two minutes.

How to prevent it

  • Use a reliable DNS provider.
  • Remove VPN or “speed booster” apps you no longer use, since some change DNS or hosts settings.
  • Keep Chrome updated.

Frequently asked questions

What does NXDOMAIN mean?

NXDOMAIN is short for "non-existent domain". The DNS server is saying it has no record for that name.

Can a website itself cause this error?

Yes. If the site's domain expired or its DNS settings are wrong, everyone will see this error. Try the site on your phone using mobile data. If it fails there too, the problem is with the website.

Sources

  1. Google Chrome Help: Fix connection errors
  2. Microsoft Learn: ipconfig command

We link to original sources wherever possible. Spotted an error? Tell us and we will fix it.