DNS_PROBE_FINISHED_NXDOMAIN: what it means and how to fix it

Published Sources checked By helps.wiki editorial team

DNS_PROBE_FINISHED_NXDOMAIN means a DNS server told your browser that the website's domain name does not exist. Check the spelling and try another device first; if the site loads elsewhere, clear the browser and system DNS caches, then change your DNS servers.

Applies to:Google ChromeMicrosoft Edge and other Chromium browsers (Brave, Opera)Windows, macOS, Linux, Android, ChromeOS
On this page

What it means

Your browser looks up a site's address by asking a DNS server. With this error, the server replied with the code NXDOMAIN ("Name Error"), which says that the domain name does not exist (the standard meaning is set out in RFC 8020). It is a definite "no such name" answer. It is not a timeout and not a failed connection. Chrome then ran a short DNS probe and ended with this result.

The same condition shows up under different wording in other browsers: Firefox says "Hmm. We're having trouble finding that site" and Safari says it can't find the server. Chrome's more generic version of the problem is ERR_NAME_NOT_RESOLVED. The codes DNS_PROBE_FINISHED_BAD_CONFIG, DNS_PROBE_FINISHED_NO_INTERNET and DNS_PROBE_TIMED_OUT are different errors with different causes.

The cause can sit in three places: the address you typed, the site's own domain settings, or something on your device or network that gives a wrong answer, such as a stale cache or a DNS filter. Google does not document this code separately, so the steps below are general DNS troubleshooting, ordered from the quickest check to the most involved.

Symptoms and causes

You are likely dealing with this problem if:

  • The page says "This site can't be reached" and "[domain]'s server IP address could not be found", with the code DNS_PROBE_FINISHED_NXDOMAIN.
  • Only one site fails: suggests a typo, a problem with that domain, or a bad local cache or hosts entry.
  • Every site fails: suggests the local network, router, DNS resolver or a VPN.
  • The site opens on another device or network: suggests the problem is on your device or your network.

The usual causes, most common first:

Typo, or the domain doesn't exist
The name may be misspelled, or the domain may have expired, been deleted, or never been registered.
A DNS problem on the site owner's side
A missing A, AAAA or CNAME record, wrong nameservers, an expired domain, or recent DNS changes that haven't propagated yet.
Stale cached answer
The browser, the operating system or the router may be holding an old or negative result.
Your ISP or router DNS is misbehaving, or filtering
The resolver may be failing or misconfigured. A DNS filter such as Pi-hole, a parental-control service or a security DNS can also return NXDOMAIN on purpose to block a name.
Local overrides
A bad entry in the hosts file, or leftover settings from a VPN, antivirus or content blocker.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Check the address and test on another device

Easy

This tells you whether the problem is the domain itself or your own setup.

  1. Read the address in the address bar letter by letter, including the ending (.com, .net and so on).
  2. Open the same address on another device, ideally one on mobile data instead of your Wi-Fi.
  3. If it fails everywhere, the domain is the problem and you can skip to the site-owner section or contact the site. If it loads elsewhere, continue with the steps below.

2.Restart Chrome and the router

Easy

Clears temporary glitches in the browser and in the router's DNS handling.

  1. Close Chrome completely and open it again, then retry the site.
  2. Unplug the modem and the router and wait 30 seconds.
  3. Plug in the modem and wait about a minute, then plug in the router.
  4. Retry the site once the connection is back.

3.Clear Chrome's host cache

Easy

Chrome keeps its own DNS cache, separate from the one in the operating system, so it can hold a bad answer on its own.

  1. Type this address into the Chrome address bar and press Enter.
    Text
    chrome://net-internals/#dns
  2. Click Clear host cache, then reload the site.

4.Flush the operating system DNS cache

Easy

Removes stale or negative answers stored by Windows or macOS.

  1. On Windows, open Command Prompt as administrator and run:
    Command Promptrun as administrator
    ipconfig /flushdns
  2. On macOS, open Terminal and run (it asks for your password):
    Terminal
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Retry the site.

5.Temporarily switch off VPN or web filtering

EasyChanges settings

A VPN, antivirus web filter or content blocker can override DNS answers or block the name.

Before you start: This is only a test. Turn the VPN or protection back on straight after, whatever the result. If the site only works with it off, look for a setting in that program that allows the site instead of leaving it disabled.

  1. Disconnect the VPN, or pause the web-filtering feature of your third-party security software.
  2. Retry the site.
  3. Turn the VPN or protection back on.

6.Check the hosts file

ModerateChanges settings

An entry in the hosts file overrides DNS for that name, so a wrong line can cause this error for one site.

Before you start: Make a copy of the hosts file before editing it. Only remove lines that mention the affected domain and leave the lines starting with # alone.

  1. On Windows, open Notepad as administrator and open C:\Windows\System32\drivers\etc\hosts. On macOS, the file is /private/etc/hosts and needs an editor run with administrator rights.
  2. Look for a line containing the domain that fails. If you find one you did not add on purpose, delete it and save the file.
  3. Flush the DNS cache again (see the earlier fix) and retry.

7.Switch to a different DNS server

Moderate

If your ISP's or router's resolver is failing or filtering, a public DNS service usually answers correctly. Google DNS is 8.8.8.8 and 8.8.4.4. Cloudflare is 1.1.1.1 and 1.0.0.1.

  1. On Windows, open Network and Sharing Center, click Change adapter settings, right-click your adapter and choose Properties.
  2. Select Internet Protocol Version 4 (TCP/IPv4), click Properties, choose Use the following DNS server addresses and enter one of the pairs above.
  3. On macOS, open System Settings, then Network, pick your connection, click Details and open the DNS tab to add the servers.
  4. Retry the site.

8.Renew the IP address and restart the DNS client (Windows)

ModerateChanges settings

Refreshes the network lease and the Windows DNS service if the quicker steps did not help.

Before you start: You may lose your network connection for a few seconds. If you are connected remotely, do this from the machine itself.

  1. Open Command Prompt as administrator and run these two commands one after the other:
    Command Promptrun as administrator
    ipconfig /release
ipconfig /renew
  2. To restart the DNS client, restart the PC. The command net stop dnscache (followed by net start dnscache) is sometimes suggested, but on current Windows 10 and 11 it is often refused with an access-denied or "requested pause, continue, or stop is not valid for this service" message because that service is protected. A normal restart also renews the network lease.
  3. Retry the site. Some community threads also suggest resetting the TCP/IP stack, but that is community advice rather than a documented fix, so treat it as a last resort.

9.If it is your own site: check the domain

Advanced

When the name really is missing in DNS, only the domain owner can fix it.

  1. Confirm the domain has not expired in your registrar account.
  2. Check that the nameservers set at the registrar match the ones your hosting provider gave you.
  3. Check that the A record points to the right IP address. Changes can take 24 to 48 hours to propagate.
  4. If you use a CDN such as Cloudflare, pause it temporarily to see whether the origin name resolves, and look through the hosting dashboard for DNS warnings.

Check that it worked

  • The site loads in Chrome without the DNS_PROBE_FINISHED_NXDOMAIN page.
  • Other sites you usually visit still load normally.
  • If you changed DNS servers or turned off a VPN or filter, it is back on or set the way you want.

If it still fails

  • If the site fails on every device and network, the domain itself is missing or misconfigured. Contact the site owner or support, or wait if the owner recently changed DNS, since changes can take 24 to 48 hours.
  • If only your network fails, contact your internet provider and mention that the resolver returns NXDOMAIN for a domain that works elsewhere.
  • If a DNS filter such as Pi-hole or a parental-control service is in use, check its block list and logs for the domain.

Questions

Is DNS_PROBE_FINISHED_NXDOMAIN a virus or a sign of hacking?

No. It only means the DNS lookup returned "this name does not exist". The usual causes are a typo, a domain problem or a stale cache.

Does the error mean the website is down?

Not in the usual sense. A down server would give a connection error. NXDOMAIN means the name itself could not be found in DNS.

Sources

  1. NXDOMAIN: There Really Is Nothing Underneath (RFC 8020) · IETF / RFC Editor
  2. How to fix the DNS_PROBE_FINISHED_NXDOMAIN error · Hostinger
  3. Fix connection and loading errors in ChromeOfficial · Google Chrome Help

Browse