DNS_PROBE_FINISHED_NXDOMAIN: 8 Fixes That Work

DNS_PROBE_FINISHED_NXDOMAIN means Chrome’s DNS lookup returned “non-existent domain”. If you keep getting DNS_PROBE_FINISHED_NXDOMAIN for a site that should exist, your DNS settings are the likely culprit.

Quick answer: DNS_PROBE_FINISHED_NXDOMAIN means DNS says the domain does not exist. Check the spelling, flush DNS, renew your IP, change DNS servers, and clear the hosts file entry if one exists.

DNS_PROBE_FINISHED_NXDOMAIN error message shown in Chrome browser

What Causes DNS_PROBE_FINISHED_NXDOMAIN?

NXDOMAIN literally means no such domain was found. This can happen when:

The domain is expired or not yet pointed at a server.
The DNS cache holds an old failed result.
Your DNS server is unreliable.
A hosts file or security tool is blocking the domain.

How to Fix DNS_PROBE_FINISHED_NXDOMAIN: Step-by-Step

Step 1: Check the spelling and the domain

Confirm the exact address. For your own new site, check that the domain’s nameservers are set at your registrar.

Step 2: Flush DNS

Run ipconfig /flushdns in an administrator Command Prompt. This is the quickest fix.

Also Read: https://axeetech.com/how-to-fix-err-name-not-resolved-complete-guide/

Step 3: Renew your IP

Run ipconfig /release then ipconfig /renew.

Step 4: Change DNS servers

Use 8.8.8.8 and 8.8.4.4 or 1.1.1.1. The full steps are in the ERR_NAME_NOT_RESOLVED guide.

Step 5: Check the hosts file

Open C:\Windows\System32\drivers\etc\hosts and delete lines that map the domain.

Step 6: Restart the DNS Client service

Use services.msc, then restart DNS Client.

Step 7: Disable VPN and security software

Test with them off, then add exceptions if it works.

Step 8: Wait for DNS propagation

If you just changed nameservers, propagation can take up to 48 hours. Check status with a DNS propagation checker.

DNS_PROBE_FINISHED_NXDOMAIN on Mac, Android and iPhone

On a Mac, flush DNS with sudo dscacheutil -flushcache and sudo killall -HUP mDNSResponder, and set 8.8.8.8 and 1.1.1.1 under Network, Details, DNS. The Apple Support site covers network settings.

On Android and iPhone, change the Wi-Fi DNS to 1.1.1.1 or enable Private DNS (Android). Restarting airplane mode also refreshes the DNS state.

Advanced Troubleshooting for DNS_PROBE_FINISHED_NXDOMAIN

If you own the domain, check nameservers at your registrar and look for a typo in A or CNAME records. A newly registered domain can show NXDOMAIN until records propagate.

Use nslookup example.com to see exactly what DNS returns. A non-existent domain response confirms the problem is DNS and not Chrome. Microsoft documents DNS tools in its Windows support center.

Related fixes: ERR_NAME_NOT_RESOLVED and ERR_CONNECTION_TIMED_OUT.

DNS_PROBE_FINISHED_NXDOMAIN fix checklist with steps in order

How to Stop DNS_PROBE_FINISHED_NXDOMAIN Coming Back

Keep your domain auto-renew on.
Use reliable DNS.
Avoid third-party tools that edit the hosts file.

Visitor or Domain Owner: Who Needs to Fix DNS_PROBE_FINISHED_NXDOMAIN?

If you are only visiting a site, your fixes are local: clear the DNS cache, change your DNS servers, and check the hosts file. If the same DNS_PROBE_FINISHED_NXDOMAIN message appears for every visitor, the problem sits with the domain owner. Owners should confirm the domain has not expired, that the nameservers at the registrar match the DNS provider, and that the A record for the root domain and the www record both exist and point to the correct server.

After any DNS change, wait for propagation before testing again, and test from a different network so your own cached result does not mislead you. The related guide on ERR_NAME_NOT_RESOLVED explains the cache steps in more detail.

Common Mistakes When Fixing DNS_PROBE_FINISHED_NXDOMAIN

Most repeat cases of DNS_PROBE_FINISHED_NXDOMAIN come from a handful of avoidable slips. Before you spend an hour on advanced troubleshooting, check that you have not made one of these:

Retyping the same misspelled domain several times instead of checking it character by character.
Editing the hosts file and forgetting about the entry months later.
Expecting new DNS records to work instantly, when propagation can take hours.

Testing one change at a time also helps. If you change DNS, proxy and firewall settings together, you will not know which change actually fixed DNS_PROBE_FINISHED_NXDOMAIN, and you may leave a harmful setting in place.

Quick Recap: Fixing DNS_PROBE_FINISHED_NXDOMAIN

Work through the fixes in order, because most cases of DNS_PROBE_FINISHED_NXDOMAIN clear up within the first three or four steps. If you still see DNS_PROBE_FINISHED_NXDOMAIN after every step, note the time it happens, which network you are on, and which sites are affected, then contact your internet provider, your hosting company or the site owner with those details.

How to fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome step-by-step guide

DNS_PROBE_FINISHED_NXDOMAIN FAQ

What is NXDOMAIN?

It stands for non-existent domain, meaning DNS has no record for that name.

Is it fixed on the router?

Sometimes. Restart the router and set DNS there if needed.

How long do DNS changes take?

Usually minutes to a few hours, up to 48 hours in rare cases.

What does NXDOMAIN stand for?

Non-Existent Domain: the DNS server reports it has no record for that name.

Can antivirus cause NXDOMAIN?

Yes. DNS filtering or web protection features can block lookups and return this result.

Axee Davies

Axee Davies is the founder of AxeeTech, publishing gaming guides, codes, and Windows how-tos since March 2013. A tech enthusiast for 13+ years — starting with smartphones and Android rooting — he now runs a site that puts out a new guide every day for Roblox players, traders, and Windows users. More about AxeeTech

axeetech.com