Network · medium

How to fix DNS_PROBE_FINISHED_NXDOMAIN (site can't be reached)

Network troubleshooting guide

What this error means

Chrome or Edge shows "This site can't be reached" with DNS_PROBE_FINISHED_NXDOMAIN. The browser asked a DNS server for the website's address, and the answer was NXDOMAIN, which means the name does not exist. Sometimes the address is simply mistyped or the site is gone. When many sites fail, the DNS server, the PC's DNS cache or settings, the hosts file, a VPN or a security program is giving wrong answers. Chrome's own help lists ERR_NAME_NOT_RESOLVED for the same situation.

Updated

Applies to
Windows 11 and Windows 10, Chrome and Edge
Difficulty
Beginner
Before changes
Low

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Chrome's error help and Microsoft's network troubleshooting article; not tested on every network.

Before you begin

Note whether the error appears for one website or for every website. One site usually means a typo or a problem with that site; every site means a DNS problem on your PC or network. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Check the address and another device

NXDOMAIN literally means the name does not exist, so a typo is the simplest explanation.

  1. Check the web address for spelling mistakes and reload the page.
  2. Open the same site on a phone using mobile data, and on another device on your Wi-Fi.
What to expect

You know whether the site, your PC or your network is the problem.

If it does not help

If the site fails everywhere, it is probably down or gone. If only your PC fails, continue with step 3. If all devices on your Wi-Fi fail, continue with step 2.

Browse related errors
02Restart the router

The router usually forwards DNS lookups, and restarting it clears a stuck DNS service.

  1. Unplug the router and modem, wait at least 30 seconds, plug the modem in, wait for its lights, then plug in the router.
  2. Try the site again.
What to expect

Websites load on all devices.

If it does not help

If all devices still fail, the provider's DNS may be down; contact your internet provider or try step 4.

Browse related errors
03Flush the DNS cache

Windows and the browser remember DNS answers, including wrong ones.

  1. Search for cmd, right-click Command Prompt and choose Run as administrator.
  2. Run ipconfig /flushdns.
  3. Close all browser windows and open the site again.
What to expect

The site loads.

If it does not help

If it still fails, check the DNS servers in step 4.

Browse related errors
04Check the DNS servers the PC uses

Microsoft's network troubleshooting includes checking which DNS servers are in use; a broken or filtering server returns wrong answers.

  1. In Command Prompt, run ipconfig /all and look at the DNS Servers lines.
  2. Run nslookup followed by the site's address (for example nslookup example.com) to see what the DNS server answers.
  3. If unknown DNS servers are set manually, open Settings > Network & internet > your connection > DNS server assignment > Edit and set it to Automatic (DHCP). To test, you can temporarily enter a well-known public DNS server.
What to expect

nslookup returns an address and the site loads.

If it does not help

If the site works only with another DNS server, your router's or provider's DNS is the problem.

Browse related errors
05Check proxy, VPN and the hosts file

These can redirect or block DNS lookups for specific sites or for everything.

  1. Open Settings > Network & internet > Proxy and turn off a proxy you do not use.
  2. Disconnect any VPN and test again.
  3. Open Notepad as administrator, open C:\Windows\System32\drivers\etc\hosts and look for lines (without # at the start) that contain the site's name. Remove them if you did not add them, and save.

Keep a copy of the hosts file before editing it.

What to expect

The site loads after removing the redirect.

If it does not help

If a program added the hosts entries, change its settings, or it may add them again.

Browse related errors
06Check browser extensions and security software

Chrome's connection troubleshooting includes Incognito mode, disabling extensions and checking firewall or antivirus.

  1. Open the site in an Incognito or InPrivate window, which runs without most extensions.
  2. If it works there, disable extensions one by one (chrome://extensions or edge://extensions).
  3. Pause third-party antivirus, web protection or parental control software and test again.

Turn protection back on after testing.

What to expect

You find the extension or program that blocks the site.

If it does not help

Add an exception for the site in that program, or remove it.

Browse related errors
07Reset network settings

Damaged network settings can break name resolution for the whole PC.

  1. In Command Prompt (Admin), run netsh winsock reset and netsh int ip reset, then restart.
  2. If that does not help, use Settings > Network & internet > Advanced network settings > Network reset.

Network reset removes saved Wi-Fi networks and passwords.

What to expect

Websites load normally.

If it does not help

After a network reset, reconnect to Wi-Fi and reinstall VPN software if you use it.

Browse related errors

Possible causes

  • A mistyped address, or a website that no longer exists
  • A DNS server that is down or filtering the domain
  • Stale entries in the Windows or browser DNS cache
  • Hosts file entries, a VPN or a proxy redirecting lookups
  • Antivirus or parental control software blocking the site

Sources & further reading