Networking • Beginner • 6 min read

How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Windows 11, 10, & Chrome

Summary

Step-by-step technical guide to resolving the DNS_PROBE_FINISHED_NXDOMAIN error. Clear DNS cache, reset Winsock, configure reliable DNS servers, and fix network adapters.

Companion Tool
Common Network Ports & Services Reference Guide

Search and inspect TCP and UDP network ports, protocols, and standard services. Quick reference lookup for firewalls, networking, and system security.

Open tool

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

When you encounter the DNS_PROBE_FINISHED_NXDOMAIN error in Google Chrome, Microsoft Edge, or Mozilla Firefox, your browser is communicating that the Domain Name System (DNS) probe concluded that the requested domain name does not exist (NXDOMAIN stands for Non-Existent Domain).

In simple terms: the browser failed to translate the human-readable website URL (such as example.com) into its corresponding 32-bit numerical IP address.

While this error occasionally occurs when a website domain has genuinely expired, in over 85% of cases, the issue resides entirely within your local Windows DNS cache, router DNS forwarder, or corrupted network stack settings.

Method 1: Flush the Local DNS Resolver Cache

Corrupted or stale DNS records stored in your computer’s local resolver cache can cause domain lookups to fail even when the destination server is online.

  1. Press Win + S to open Windows Search, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Execute the following command to flush the resolver cache: 
    ipconfig /flushdns
  3. You should see the confirmation:
    Successfully flushed the DNS Resolver Cache.
  4. Next, release and renew your local DHCP lease: 
    ipconfig /release
ipconfig /renew
  5. Reload the website in your browser.

Method 2: Reset Winsock Catalog & TCP/IP Stack

Windows manages network sockets via the Windows Sockets API (Winsock). If third-party VPNs, anti-malware suites, or network drivers corrupt this catalog, network routing fails.

In the elevated Administrator Command Prompt, run:

netsh winsock reset
netsh int ip reset

Important: Windows requires a full system restart after resetting the TCP/IP stack. Reboot your PC and test your connection.

Method 3: Change to High-Reliability Public DNS Servers

By default, your operating system obtains DNS servers automatically from your local ISP router via DHCP. ISP DNS servers frequently suffer from caching outages, slow TTL propagation, or geographic misconfigurations.

Switching to verified, global Anycast DNS providers (such as Cloudflare or Google) permanently eliminates ISP lookup failures:

DNS ProviderPrimary IPv4Secondary IPv4Primary IPv6
Cloudflare (Fastest & Privacy)1.1.1.11.0.0.12606:4700:4700::1111
Google Public DNS8.8.8.88.8.4.42001:4860:4860::8888
Quad9 (Malware Blocking)9.9.9.9149.112.112.1122620:fe::fe

How to Change DNS in Windows 11 / 10:

  1. Press Win + R, type ncpa.cpl, and hit Enter to open Network Connections.
  2. Right-click your active connection adapter (Ethernet or Wi-Fi) and select Properties.
  3. Double-click Internet Protocol Version 4 (TCP/IPv4).
  4. Select the radio button: Use the following DNS server addresses:
    • Preferred DNS server: 1.1.1.1
    • Alternate DNS server: 8.8.8.8
  5. Check Validate settings upon exit and click OK.

Method 4: Restart the Windows DNS Client Service

The Dnscache service caches DNS names and registers the computer’s name for network discovery.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll down to locate DNS Client.
  3. If the options are not grayed out, right-click and click Restart.
  4. (Note: On modern Windows 11 builds, the service status is protected by Windows Defender. If grayed out, flushing via ipconfig /flushdns in Method 1 is the official alternative).

Method 5: Clear Google Chrome’s Internal Host Cache

Google Chrome maintains its own independent internal DNS socket pool separate from the operating system:

  1. Open a new tab in Google Chrome.
  2. In the URL address bar, navigate to: 
    chrome://net-internals/#dns
  3. Click the Clear host cache button.
  4. Next, navigate to: 
    chrome://net-internals/#sockets
  5. Click Close idle sockets followed by Flush socket pools.
  6. Close and restart your browser.

Summary Verification Checklist

If the website still fails to load after completing all five methods:

  • Test loading the URL on your mobile phone connected to cellular data. If it fails on mobile data as well, the website’s authoritative nameservers or domain registration have experienced an outage at the registrar level.
  • Disable any active third-party VPN tunnel or proxy server temporarily to rule out corrupted route tables.

Related reference

← Back to all guides