Menu
How to fix DNS_PROBE_FINISHED_NXDOMAIN error on Windows 10 and Windows 11 in Chrome, Edge and Firefox

How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Windows

0

Table of content

If you’ve ever tried to visit a website on your Windows PC and seen a message like “This site can’t be reached – Server IP address could not be found” or simply “Hmm… can’t reach this page”, then you’ve likely encountered the DNS_PROBE_FINISHED_NXDOMAIN error in your browser (Chrome, Edge or Firefox).
In simple terms: your browser tried to translate the website’s name into an IP address (via the DNS – the internet’s “phone book”), and it failed. This guide walks you through what the error means, why it happens on Windows, and how to fix it with 11 proven steps. Whether you’re a power-user or a Windows admin, you’ll find actionable fixes here.

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

Let’s break it down:

  • DNS = Domain Name System: converts website names (like example.com) into IP addresses.

  • PROBE = a test/lookup your system sends out to a DNS server.

  • FINISHED = the lookup process completed.

  • NXDOMAIN = “Non-Existent Domain” – the server returned that the domain does not exist.

So, when you see DNS_PROBE_FINISHED_NXDOMAIN, it means your system asked the DNS server “what’s the IP for this domain?” — the request completed, but the answer was “there is no such domain.” The cause could be on your Windows PC or network, or it might be a problem with the domain’s DNS configuration or registration.

Common Causes

Here are the most common root causes of this error on Windows:

  • Typo in the URL you entered.

  • Local DNS cache corruption or stale entries.

  • Misconfigured DNS servers on your Windows device or router.

  • A VPN/antivirus/firewall interfering with DNS resolution.

  • Browser-specific issues (cache, corrupted data, extensions).

  • Domain-side issues: expired domain, incorrect DNS records, propagation delay.

  • ISP or DNS-provider problems.

Quick Fix Summary

Here’s a quick bullet list of the fixes (full steps follow below):

  1. Confirm URL & try another browser

  2. Restart your PC & router

  3. Flush DNS cache

  4. Release & renew IP address

  5. Change DNS servers (Google DNS / Cloudflare)

  6. Restart DNS Client service (Windows)

  7. Clear browser cache & disable extensions

  8. Temporarily disable VPN/antivirus/firewall

  9. Check the local hosts file

  10. Check the domain’s DNS records & propagation

  11. Contact ISP or hosting provider

Step-by-Step Fixes on Windows

1. Basic checks

  • Make sure you typed the website address correctly (check for typos).

  • Try another site (e.g., https://www.google.com) to see if only one site fails.

  • Try a different browser (if you use Chrome try Edge) to isolate whether it’s browser-specific or system-wide.

  • Try connecting another device to the same network – if it works, the issue is likely on your Windows PC.

2. Restart the PC + Router/Modem

Sometimes a simple restart solves the problem:

  1. Shut down your Windows PC and unplug your router/modem.

  2. Wait ~30 seconds, plug the modem back in, wait ~1 minute, then plug the router back in.

  3. Boot your PC and open the browser.
    Why it works: this resets the network stack, clears transient DNS/connection issues.

3. Flush DNS cache

On Windows:

  1. Press Win + R, type cmd  and press Ctrl+Shift+Enter to run Command Prompt as Administrator.

  2. Enter: ipconfig /flushdns

  3. You should see: “Successfully flushed the DNS Resolver Cache.”

  4. Close the window, open your browser and test the site.
    This clears stored domain-to-IP mappings that might be outdated or corrupted.

4. Release & renew IP address

Still in Command Prompt as Administrator:

ipconfig /release
ipconfig /renew

Then restart your PC. This forces your Windows system to re-negotiate network settings and can fix hidden DHCP or IP issues.

5. Change DNS servers (Google DNS / Cloudflare)

On Windows 10/11:

  1. Open Control Panel → Network and Internet → Network and Sharing Center.

  2. Click Change adapter settings. 

  3. Right-click your active Wi-Fi or Ethernet adapter → Properties. 

  4. Select Internet Protocol Version 4 (TCP/IPv4) → click Properties. 

  5. Choose Use the following DNS server addresses, and enter for example: 

    • Preferred: (Google)8.8.8.8

    • Alternate: 8.8.4.4

  6. Click OK → close everything → restart your browser (or PC).
    Switching to a known-good public DNS often resolves DNS resolution failures.

  7. The other option is also we can do it from Chrome browser, Enter chrome://settings/security on the address bar to access the Chrome DNS settings.
  8. Scroll down to the Advanced section and select With Custom. Users can change it to one of the built-in DNS server addresses from Cloudflare, OpenDNS, CleanBrowsing, or Google.
    Modifying DNS settings on Google Chrome.

6. Restart the DNS Client service

If none of the above worked:

  1. Press Win + R, type , press Enter.services.msc

  2. Scroll to DNS Client, right-click → Restart. 

    • If the option is greyed out, use Command Prompt (Admin):

      net start dnscache
      net stop dnscache  

fter restarting the service, restart your browser and check again.
The DNS Client service is responsible for resolving and caching DNS names locally on Windows. A hang or fault here can lead to NXDOMAIN errors.

7. Clear browser cache & disable extensions

Browsers can interfere with DNS resolution especially if an extension redirects or blocks DNS queries. In Chrome/Edge/Firefox:

  • Go to browser settings → Clear Browsing Data → choose Cached images and files and Cookies and other site data → Clear.

  • Disable all extensions temporarily (especially ad-blockers or DNS-related extensions).

  • In Chrome you can also enter chrome://net-internals/#dns → click Clear host cache. 
    Then retry accessing the site.

8. Temporarily disable VPN / antivirus / firewall

VPNs, security software or firewalls can block or reroute DNS lookups, causing failures.

  • Temporarily disable your VPN or turn it off.

  • Temporarily disable your antivirus / firewall (or set it to a test/allow mode).

  • Then test if the website loads.
    Important: After testing, re-enable your security software.

9. Check the local hosts file

The local hosts file matches a domain name to its IP address. Computers refer to it every time you open a website so that they can fetch the correct page to display on the browser. Sometimes, the hosts file can unknowingly mark a specific domain name or IP address as inaccessible. Checking and editing the file can potentially fix the DNS_PROBE_FINISHED_NXDOMAIN error. The Windows hosts file can override DNS resolution:

  1. In the search box, type Notepad and select Run as administrator.
Running Notepad as the administrator.
  1. Navigate to File -> Open. Change the file filter from Text Documents (*.txt) to All Files.
  2. Enter the path below in the File name bar:
C:\Windows\System32\drivers\etc\
This PC File name Windows System 32 drivers etc
  1. Select the hosts file and open it
system32 hosts drivers etc
  1. The file will show a list of blacklisted websites below the last line using the # symbol. If you see the target website’s domain name and IP address under ::1 localhost line, remove them and save changes.
Visit the previously blocked websites to check if the DNS_PROBE_FINISHED_NXDOMAIN notification is still there.
 

10. For Webmasters: Check the domain’s DNS records & propagation

If the above is still not working, it might not be your Windows PC at all but the domain’s DNS:

  • Check the domain hasn’t expired or been suspended.

  • Verify the domain’s A/AAAA/CNAME records point correctly to the hosting server.

  • If you recently changed DNS, allow time for propagation (could take up to 48 hours).

  • If using a CDN or DNS proxy (e.g., Cloudflare), check their configuration.
    If you’re the website owner, you may also contact your DNS/hosting provider.

11. When to contact your ISP or hosting provider

If you’ve tried all the above on your Windows PC, and still get the error:

  • Contact your ISP: ask if there are DNS issues or filtering on their network.

  • If you’re a website owner and the error happens only for your domain: contact your hosting/DNS provider with the domain name, screenshots, any nslookup or ping results.Providing clear info helps reduce the troubleshooting time.

FAQs

Q1. What does DNS_PROBE_FINISHED_NXDOMAIN mean in Chrome?
A1. It means Chrome sent a DNS lookup for the website, the lookup completed, but returned “NXDOMAIN” (non-existent domain). Essentially, the browser couldn’t find the IP for the domain.

Q2. Is DNS_PROBE_FINISHED_NXDOMAIN a virus or malware?
A2. No — it’s not a virus. It’s a DNS resolution error. However, malware or malicious software can cause DNS issues by hijacking DNS settings or hosts file, so it’s worth checking if you’ve recently installed odd software.

Q3. Why does DNS_PROBE_FINISHED_NXDOMAIN happen only on one device?
A3. Because that device may have a local issue (DNS cache stale, misconfigured DNS server, hosts file entry, browser extension) while other devices on the network work fine.

Q4. How do I fix DNS_PROBE_FINISHED_NXDOMAIN on mobile?
A4. On Android or iOS you would restart the device, clear Wi-Fi settings or switch to a different DNS server, flush the DNS/app cache, disable VPNs/antivirus apps. But since this blog is Windows-specific, I recommend checking a mobile-focused guide or [How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Windows – Tech EUC our general DNS guide].

Q5. How do I know if the problem is my PC, my router/ISP or my domain?
A5. Try these steps:

  • Use another device on same network. If it works, your PC is the problem.

  • Use your Windows PC on another network (e.g., mobile hotspot). If it works, your router/ISP was the problem.

  • If the issue is only one domain (others work fine), then likely the domain’s DNS/hosting is at fault.

Signup to our weekly newsletter

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *