Fix DNS_PROBE_FINISHED_NXDOMAIN in Windows 10/11

Quick answer for advanced users: Open Command Prompt as admin and run ipconfig /flushdns, then ipconfig /registerdns, then ipconfig /release and ipconfig /renew. If that doesn't work, change your DNS to Google's (8.8.8.8 and 8.8.4.4).

This error happens when your computer asks a DNS server for the IP address of a website, and the server replies 'that domain doesn't exist.' But the website does exist—it's you, not them. Usually, it's a corrupt DNS cache, a misconfigured DNS server, or a temporary network glitch. I've seen it after switching Wi-Fi networks, after VPN disconnects, or just randomly on Windows machines. It's infuriating because one site works, the next doesn't. Let's fix it.

Step-by-Step Fix for DNS_PROBE_FINISHED_NXDOMAIN

Flush the DNS cache
This clears out corrupted DNS entries your PC has stored.
```
ipconfig /flushdns
```
Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Windows Terminal (Admin)). Paste that and hit Enter. You should see 'Successfully flushed the DNS Resolver Cache.'
Register DNS again
This tells your PC to re-register with the network.
```
ipconfig /registerdns
```
Wait a few seconds—it might take a moment.
Release and renew your IP
This forces your network adapter to get a fresh IP address from the router.
```
ipconfig /release
ipconfig /renew
```
The /release command will drop your internet—don't panic. The /renew brings it back. If you get an error like 'No operation can be performed on Local Area Connection,' just move on.
Reset Winsock and reset the catalog
Winsock is the Windows socket API—when it's corrupted, network calls go nowhere.
```
netsh winsock reset
netsh int ip reset
```
Both commands will ask you to restart your computer. Do that after running them.
Change your DNS servers
If the above didn't work, your ISP's DNS might be the problem. Switch to a public DNS provider. Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active connection (Wi-Fi or Ethernet) > Properties. Select 'Internet Protocol Version 4 (TCP/IPv4)' > Properties. Choose 'Use the following DNS server addresses' and set:
```
Preferred DNS: 8.8.8.8
Alternate DNS: 8.8.4.4
```
Then click OK and close everything. Test the website.
Clear Chrome's internal DNS cache
Chrome has its own DNS cache that sometimes goes stale. Type chrome://net-internals/#dns in the address bar and hit Enter. Click the 'Clear host cache' button. Then go to chrome://net-internals/#sockets and click 'Flush socket pools.' Close and reopen Chrome.

If the Error Still Appears

Sometimes the problem isn't your PC—it's your router or your VPN. Try these:

Restart your router by unplugging it for 30 seconds. This clears its DNS cache too. I've fixed this error more times than I can count with a simple power cycle.
Disable your VPN temporarily. Some VPNs mess with DNS routing. If the site loads after disconnecting, reconfigure your VPN's DNS settings or switch servers.
Check the hosts file for stale entries. Open Notepad as admin, go to C:\Windows\System32\drivers\etc\hosts, and look for any line pointing the domain to an old IP. Delete it and save.
Run the Windows Network Troubleshooter. I know, it's the 'turn it off and on again' of software, but it can detect and fix simple misconfigurations in seconds.

Preventing This Error in the Future

Set your DNS manually to a reliable provider like Google (8.8.8.8/8.8.4.4) or Cloudflare (1.1.1.1). That avoids ISP DNS outages. Also, keep Windows and Chrome updated—both have fixed DNS bugs in recent patches. If you use a VPN, choose one that supports DNS leak protection and custom DNS. And every few months, run ipconfig /flushdns just to keep things clean. You're welcome.