You type a web address, press Enter, and instead of the page you get a grey screen that says “This site can’t be reached” with the code DNS_PROBE_FINISHED_NXDOMAIN. It looks technical, but in most cases it takes less than five minutes to fix. This guide explains what the error means, walks through real-world scenarios we see at Venus Systems, and gives you the fixes in the order that solves the problem fastest.
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
Every website has a name (like venussystems.ca) and a numeric IP address (like 203.0.113.10). The Domain Name System (DNS) is the internet’s phone book that translates names into addresses. When your browser asks DNS for a website’s address and gets back the answer “this name does not exist”, Chrome shows DNS_PROBE_FINISHED_NXDOMAIN. NXDOMAIN literally means non-existent domain.
The important point: the website is not always the problem. Very often the domain is perfectly fine, and something between your device and the internet (your router, your computer’s DNS cache, a VPN or a security tool) is giving the wrong answer.
You may see the same problem in other browsers with different wording:
- Chrome / Edge: “This site can’t be reached … DNS_PROBE_FINISHED_NXDOMAIN”
- Firefox: “Hmm. We’re having trouble finding that site.”
- Safari: “Safari can’t find the server.”
First, a 30-second check: is it you or the website?
- Check the spelling of the address. A missing letter or a wrong ending (.com instead of .ca) is the most common cause of all.
- Try the site on another network. Turn off Wi-Fi on your phone and open the site using mobile data. If it loads there, the website is fine and the problem is on your network or device.
- Try another website. If no websites load at all, your internet connection itself is down, which is a different problem.
Real-world scenarios
Scenario 1: “It works on my phone’s data, but not on the office Wi-Fi”
This happened to us. Our own website suddenly showed DNS_PROBE_FINISHED_NXDOMAIN on our network, while it loaded normally on mobile data and on other networks. Public DNS servers were answering correctly. The culprit was the router’s DNS cache, which was holding on to a bad answer. A simple router restart fixed it instantly. If the site works on another network, start with Fix 1 below.
Scenario 2: “Only one computer in the office gets the error”
Other devices on the same Wi-Fi open the site without trouble. The problem is local to that computer: its DNS cache, its DNS settings, a VPN, or its hosts file. Go to Fixes 2 to 6.
Scenario 3: “Nobody can reach our website, from anywhere”
If the error appears on every network and every device, the issue is likely with the domain itself: an expired domain registration, a recent change of name servers, or missing DNS records. Jump to “If you own the website” below.
Scenario 4: “It started after installing a VPN, antivirus or browser extension”
Security and privacy tools often route DNS requests through their own servers. If those servers are slow or blocking a domain, you will see NXDOMAIN. See Fix 7.
The fixes, in the order we recommend
Fix 1: Restart your router and modem
Your router keeps its own copy of recent DNS answers. If that copy is stale or corrupted, every device on your network gets the wrong answer. Restarting clears it.
- Unplug the power from your router (and modem, if it is a separate box).
- Wait 30 seconds.
- Plug the modem in first, wait until its lights are steady, then plug in the router.
- Wait two to three minutes, then try the website again.
This single step resolves a large share of the NXDOMAIN cases we handle for small offices.
Fix 2: Change your DNS server to Google (8.8.8.8) or Cloudflare (1.1.1.1)
By default your computer uses your internet provider’s DNS servers, which are sometimes slow or out of date. Switching to a reliable public DNS service is quick and safe.
- Google Public DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare: 1.1.1.1 and 1.0.0.1
On Windows 10 / 11
- Press Windows + R, type
ncpa.cpland press Enter. - Right-click your active connection (Wi-Fi or Ethernet) and choose Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Choose Use the following DNS server addresses and enter 8.8.8.8 as preferred and 8.8.4.4 as alternate.
- Click OK, close the windows, and try the site again.
On a Mac
- Open System Settings → Network, select your connection and click Details.
- Go to the DNS tab, click + and add 8.8.8.8 and 8.8.4.4.
- Click OK and try again.
For the whole office: you can set the same DNS servers in your router’s settings so every device benefits. If you manage a business network with its own domain controller or firewall, talk to your IT provider first so you don’t break internal name resolution.
Fix 3: Flush your computer’s DNS cache
Your computer also remembers DNS answers. Clearing them forces a fresh lookup.
Windows (open Command Prompt as administrator):
ipconfig /flushdnsmacOS (open Terminal):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFix 4: Clear Chrome’s own DNS cache
Chrome keeps a separate cache. In the address bar, open chrome://net-internals/#dns and click Clear host cache. Then go to chrome://net-internals/#sockets and click Flush socket pools. Restart Chrome and try again.
Fix 5: Release and renew your IP address and reset the network stack (Windows)
If the problem persists, reset the network configuration. In Command Prompt as administrator, run these one at a time:
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock resetRestart your computer afterwards.
Fix 6: Check the hosts file
The hosts file can override DNS for specific websites, and old entries or malware sometimes point a domain to the wrong place. On Windows it is located at C:\Windows\System32\drivers\etc\hosts; on a Mac it is /etc/hosts. Open it as an administrator and look for a line containing the website’s name. If you find one you don’t recognise, remove it (or ask your IT team), save the file, and flush DNS again.
Fix 7: Temporarily disable VPN, proxy, antivirus web filtering and extensions
- Disconnect your VPN and try again.
- In Chrome, open Settings → Privacy and security → Security and check Use secure DNS. Try switching the provider or turning it off temporarily.
- Pause your antivirus or firewall’s web protection for a minute to test.
- Open the site in an Incognito window to rule out extensions.
If the site loads after one of these changes, you have found the cause. Re-enable your protection and adjust that tool’s settings rather than leaving it off.
Fix 8: Restart the DNS Client service and update network drivers
On Windows, a stuck DNS Client service or an outdated network adapter driver can cause intermittent NXDOMAIN errors. Restarting the computer usually resets the service; updating the network driver from the manufacturer’s website helps when the problem keeps coming back.
Fix 9: Contact your internet provider
If nothing above works and the error happens on every device on your network, your provider’s DNS or network may be having an outage. Changing to 8.8.8.8 (Fix 2) usually bypasses it while they fix the problem.
If you own the website
When customers report DNS_PROBE_FINISHED_NXDOMAIN from many locations, check the domain itself:
- Is the domain registration active? An expired domain stops resolving. Check the renewal date with your registrar.
- Are the name servers correct? If you recently moved hosting or DNS providers, confirm the name servers at your registrar match your DNS host.
- Do the DNS records exist? Make sure there is an A record for the main domain and a record for www (A or CNAME).
- Test from outside your network. Run
nslookup yourdomain.ca 8.8.8.8in Command Prompt or Terminal. If Google’s DNS returns an address, the domain is fine and the problem is local to the affected users. - Allow time for changes. After changing DNS records or name servers, updates can take from a few minutes up to 48 hours to reach every network.
Quick checklist
- Check the spelling of the address.
- Test the site on mobile data or another network.
- Restart the router and modem.
- Change DNS to 8.8.8.8 / 8.8.4.4 (or 1.1.1.1).
- Flush the computer’s DNS cache.
- Clear Chrome’s host cache.
- Release/renew IP and reset Winsock.
- Check the hosts file.
- Disable VPN, proxy, secure DNS or web filtering to test.
- Contact your internet provider, or check the domain if you own it.
Frequently asked questions
Is DNS_PROBE_FINISHED_NXDOMAIN a virus?
No. It is a name-lookup error. In rare cases malware changes your DNS settings or hosts file, which is why Fix 6 and a security scan are worth doing if the error keeps returning.
Is it safe to use 8.8.8.8?
Yes. Google Public DNS and Cloudflare (1.1.1.1) are widely used, free and reliable. Businesses with internal servers should set DNS centrally on their firewall or domain controller instead of on each computer.
Why does the website work on my phone but not on my computer?
Your phone on mobile data uses your carrier’s DNS, while your computer uses your router’s. A stale router or computer cache is the usual reason. Restart the router and flush DNS.
How long does the error last?
If it is caused by a cache, it clears as soon as you restart or flush. If it is caused by a recent DNS change on the website, it can take up to 48 hours to disappear everywhere.
Need help?
DNS errors that keep coming back are often a sign of a deeper network issue, such as an ageing router, a misconfigured firewall or DNS settings that were never documented. At Venus Systems we monitor and manage business networks across Toronto and the GTA so problems like this are caught before your team notices. Call us at 647-336-6908 or book a free IT assessment.
Ready to Modernize Your IT Environment?
Secure, scalable, and business-focused technology solutions built for growth.
