DNS_PROBE_FINISHED_NXDOMAIN: What It Is and How to Fix It (2026 Guide)

Key Takeaways

• DNS_PROBE_FINISHED_NXDOMAIN error happens when the browser fails to translate a web address into an IP address.
• Regular Visitors can resolve this error by flushing their device’s DNS cache or switching to a public DNS.
• Website owners should check for an expired domain or misconfigured DNS records to get their site back online.
• Cloudways helps prevent this error from happening in the first place by using built-in premium DNS and edge routing to keep website traffic stable.

Few things are more annoying than expecting a site to load, and instead seeing a “This site can’t be reached” message. The most common version of this error is DNS_PROBE_FINISHED_NXDOMAIN.

Depending on which browser or device you’re using, the error may look a bit different. You might see err_name_not_resolved or server ip address could not be found.

Whatever variation you’re seeing, they all mean the same thing. Your browser is unable to locate the website you want to visit. This can be due to a temporary glitch in how your device talks to Domain Name System (DNS) servers.

Fixing this issue is not too difficult. And in this guide, I’m going to show you how. I’ll cover the most common reasons which triggers this error along with a list of tested solutions to resolve it.

What Is the DNS_PROBE_FINISHED_NXDOMAIN Error?

This error shows up when your browser can’t figure out where a website is located on the internet. It can’t find the server associated with the domain name you’re typing in the browser.

Before we get to the fixes for this error, let me first explain how your computer finds a website in the first place.

Understanding the DNS Lookup Process

Every time you load a webpage, your device performs a series of steps known as a DNS lookup. Since computers communicate using IP addresses and humans use domain names, DNS works as a translator.

When you type a web address into your browser and hit Enter, your device performs a series of steps to locate the website:

• Your browser first checks its DNS cache for a saved IP address from a previous visit.
• If no record is found, your device sends a DNS lookup request.
• The DNS resolver searches for the domain’s IP address.
• Once the correct IP is found, it is returned to your browser.
• Your browser connects to the web server and loads the site.

This entire process completes in seconds. But if any step in the chain fails, or if the server returns outdated information, the connection breaks and triggers the error.

Get Your Website Live Faster with Cloudways DNS Made Easy.

Manage domains with DNS made easy and gain complete control over your website’s online presence.

TRY NOW

What Does “NXDOMAIN” Actually Mean?

Sounds gibberish, but dns_probe_finished_nxdomain actually means something. Only the last two letters matter N and X. It stands for Non-Existent Domain.

When your browser runs the lookup steps I mentioned earlier, the DNS server sends back a specific message, telling your browser that it can’t find any matching IP address records for that specific domain name.

The domain actually exists and is probably working fine for others. But because the error is triggered due to a setting on your computer, your browser, or your network is misconfigured, the DNS request fails before it reaches the right server.

How This Error Appears in Different Browsers

Like I mentioned earlier, there are variations of the error you’d see depending on your browser or device. The error is the same, but different browsers use their own phrasing to display it.

Google Chrome

Chrome shows a very direct message. You’ll usually see a message stating this site can’t be reached, sometimes with a note that says the server ip address could not be found.

And at the bottom, it gives you the exact DNS_PROBE_FINISHED_NXDOMAIN code so you know what went wrong.

Microsoft Edge

Since Edge also runs on the same engine as Chrome, it shows a very similar looking error message. You’ll typically see “Hmm… can’t reach this page” followed by the same DNS error code.

Mozilla Firefox

Firefox shows a Server Not Found error along with a message saying it can’t connect to the website. It also shows troubleshooting tips, like checking your modem or reconnecting to your Wi-Fi.

Apple Safari

Safari just shows you a generic alert stating that it cannot find the server for the website.

What Causes the DNS_PROBE_FINISHED_NXDOMAIN Error?

The cause of the error can be anything from a simple typo to something deeper like a network configuration issue. Here are some of the most common reasons why this issue happens.

1. You Misspelled the Domain

One wrong letter can stop DNS from finding the site you’re requesting. The same issue can also happen if the domain doesn’t exist or hasn’t been registered yet, since there’s nothing for DNS to resolve to.

2. The DNS Records Are Broken or Outdated

If the domain is valid, but the DNS records are misconfigured, this can also trigger the error. This can happen if someone forgot to renew the domain, or the records were set up incorrectly.

When the DNS can’t figure out where to send your request, the browser can’t do anything aside from throwing the error.

3. Your Computer Is Holding Onto Bad Info

Every device stores its own DNS cache to help sites load faster the next time you visit them. But sometimes, cache can hold onto old or incorrect data, like a website’s previous IP address. When that happens, your browser gets confused and throws the error.

The same goes for the local hosts file on your computer. If you ever tweaked it in the past to test a website and forgot to revert it back, that old entry will block the connection.

4. Network Settings or ISP DNS Problems

Another common cause for the error is bad DNS settings on your machine or router. If the DNS server you’re using goes down or stops responding properly, which is normal with internet service providers, your browser will not be able to resolve the domain even though the site itself is completely fine.

5. VPNs, Antivirus, or Firewalls Getting in the Way

A strict firewall or antivirus program might block a request it flags as suspicious. A VPN might try to route your traffic through a DNS server that is currently having issues. These tools are super useful, but occasionally they block access to perfectly safe websites.

6. Problems With CDN or DNS Propagation

If a website was recently moved or its DNS settings were changed, it takes a while for those updates to spread across the internet. During this waiting period, also known as DNS propagation, your browser might show you the error because it’s looking at outdated records. You see this happen a lot right after website owners make changes in services like Cloudflare.

How to Fix DNS_PROBE_FINISHED_NXDOMAIN (For Everyday Users)

If you’re just trying to browse the internet and see the error page, go through the tested solutions covered below. I’ve arranged the solutions from simple fixes to more advanced network troubleshooting.

1. Check for Domain Typos

Before you start changing any system settings, start with the simplest fix. A common cause of this error is a basic typo in the website address.

Carefully check the entire URL in your browser’s address bar. Even one misplaced letter, a hyphen instead of an underscore, or an extra dot is enough to trigger the non-existent domain error.

If you are 100% sure the spelling is correct and the site is still not loading, move to the next solution.

2. Clear Chrome’s Internal DNS Cache

Chrome keeps its own hidden DNS cache completely separate from your computer’s operating system. But when this internal cache gets corrupted, it’ll block you from accessing sites.

Running a quick chrome net internals dns clear host cache is one of the most effective ways to get things working again.

Here is how to do it:

• Open a new tab in Chrome, type the following address in the search bar and hit Enter:

chrome://net-internals/#dns

• You’ll see a screen with a few options. Click the option that says Clear host cache.

There is no confirmation popup, but the cache should clear up as soon as you click the button. Once done, go ahead and reload your website to see if it works now.

3. Flush Your System’s DNS Cache (Windows & macOS)

And just like Chrome, your operating system keeps its own local cache of IP addresses. If the Chrome fix didn’t work, you’ll need to flush your system’s DNS cache. You can do this by running a simple flush dns command. It’ll force your computer to delete all saved IP addresses and fetch fresh ones.

Here is how to do it depending on your operating system:

For Windows:

• Open up command prompt, paste the following command and hit Enter:

ipconfig /flushdns

• You should see a message saying “Successfully flushed the DNS Resolver Cache.“

For macOS:

• Open the Terminal app, paste the following command and hit Enter.

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

• It’ll ask for your Mac admin password. Type it in and hit Enter. Once you do, you won’t see a success message, but the cache will be cleared. Now go ahead and reload the site to see if it’s working now.

4. Clear DNS Cache on Mobile (Android & iPhone)

If you’re on home Wi-Fi and seeing this error on your phone or tablet, the problem could be due outdated network data stored on the device.

Like computers, mobile devices also cache network information to speed things up. But these records can become outdated and cause connection issues.

Here is how you can clear cache without resetting your entire phone:

For Android

The fastest way to clear your network data on Android is to turn your network connection off and then back on again, or reset your browser cache.

• Swipe down on your screen to open the Quick Settings panel and turn on the Airplane Mode.
• Wait a few seconds, then turn it off. This forces your phone or tablet to request a fresh network connection. Test now and the site should load without the error.
• If you’re using Chrome on Android, you can also go to Settings > Privacy and security > Clear browsing data. Then check Cached images and files, and tap Clear data.

For iPhone (iOS)

• Swipe down on your screen to access the Control Center.
• Turn on Airplane Mode.
• Wait a few seconds, and then turn it off again.
• Alternatively, you can clear Safari’s system cache by going to your phone’s Settings > Apps > Safari and tapping Clear History and Website Data.

5. Change Your DNS Servers (Switch to Public DNS)

By default, your computer uses any DNS servers your Internet Service Provider (ISP) assigned to it. But, DNS servers assigned by ISPs are known for going down, being slow, or taking a long time to update their DNS records.

If this is the case for you, switching to a better free public alternative like Google Public DNS or Cloudflare is a permanent fix for this issue.

On Windows

• Open up the Control Panel, click Network and Internet, then Network and Sharing Center.
• Click Change adapter settings.
• Right-click your active connection and select Properties.

• Click on Internet Protocol Version 4 (TCP/IPv4) option, then Properties.
• Check the option that says Use the following DNS server addresses and type in these addresses:

• Preferred DNS server: 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google)
• Alternate DNS server: 1.0.0.1 (Cloudflare) or 8.8.4.4 (Google)

• Click OK to save and close out the windows.

On macOS

• Click the Apple logo and choose System Settings.
• Click on Network in the left sidebar, then choose your active connection.
• Then click the Details… button next to your active connection.
• In the popup window, select DNS.
• Click the small + (plus) icon and add these addresses:

• 1.1.1.1
• 1.0.0.1

• Click OK to apply the changes.

6. Release and Renew Your IP Address

If clearing cache and changing DNS servers didn’t work, you’ll need to renew your IP address. Doing this will force your computer to drop its current connection and ask your router for a new IP address and DNS settings.

On Windows

Open the Command Prompt just like I showed you earlier. Type ipconfig /release and hit Enter.

Your internet will disconnect temporarily now. Next, type ipconfig /renew and hit Enter. This will reconnect you to the network with a fresh IP address.

On macOS

• Go back to the System Settings on your Mac and click Network. Select your active connection and click Details.
• Choose TCP/IP from the sidebar, then click the Renew DHCP Lease button.

7. Restart the DNS Client Service (Windows Only)

Windows runs its own background service to handle DNS requests and cache. If this service gets stuck, it can throw the NXDOMAIN error. If you simply restart the service, you can get rid of the error pretty quickly.

To do this, hit the Windows key + R to open the Run dialog box. Type services.msc and hit Enter to open the Services window.

Now look for the DNS Client option. Right-click on it and select Restart.

If the Restart option is greyed out, which is common in Windows 10 and 11, just restart your computer to achieve the same result.

8. Check Your Local Hosts File

Your computer has a hidden text file called the “hosts” file which lets you manually map a domain name to a specific IP address. Developers use this file to test websites before they go live.

But if you, or a program you installed, added the website you’re trying to visit to this file with an outdated IP address, it will block you from accessing the site.

On Windows

• Open Notepad, click File > Open. Then paste the following address in the File name field: C:\Windows\System32\drivers\etc\
• Change the file type dropdown from “Text Documents” to “All Files“.

• Open the file named hosts.

• If you see any suspicious lines at the bottom of this file that mention website URLs, delete them. Then save the file, and restart your browser. This should fix the error.

On macOS

• Open the Terminal app and type sudo nano /private/etc/hosts and hit Enter.
• Enter your Mac’s admin password.
• In the file, if you see the website you want to visit listed, delete that line.

• To save the changes you make to the file in the nano editor, hit Control + O, then Return, and finally Control + X to close the file.

Finally, go ahead and check if the site loads now without showing you the dns_probe_finished_nxdomain error.

9. Temporarily Disable Your VPN or Antivirus

Virtual Private Networks (VPNs) and antivirus programs can sometimes get a little too aggressive. And when they do, they accidentally block completely safe websites or interfere with your network’s DNS settings.

To see if this is what’s causing the error, temporarily turn off your VPN connection and pause your antivirus software.

Once they are completely disabled, try reloading the website. If the site loads perfectly, you know what’s causing the issue.

To fix this, check to see if there’s an update available for your VPN or antivirus program. Also check their whitelist settings and whitelist the site you want to visit.

10. Reset Chrome Flags

If you use Google Chrome, there’s a chance you or your browser extension might have tweaked “Chrome Flags” at some point to try out experimental features.

While these features are nice to have, they’re experimental for a reason. And when they glitch or break, it can interfere with DNS resolution and prevent websites from loading.

To fix this:

• Open a new tab in Chrome and type chrome://flags in the address bar.

• Click the Reset all button.

• Lastly, click the Relaunch button to restart your browser.

Once Chrome launches back, try visiting the website one last time to see if the error is gone.

How to Fix DNS_PROBE_FINISHED_NXDOMAIN (For Website Owners)

If you are seeing this error on your own website, the problem is likely on the backend rather than your device. What I mean is that the domain may no longer be active, or its DNS settings may be pointing visitors to the wrong server.

Here is how to troubleshoot the error as a website owner.

1. Check If Your Domain Has Expired

If your credit card expired or auto-renew failed, your domain registrar will either suspend your domain name or temporarily park it. When that happens, DNS records may stop resolving properly, causing visitors to see an NXDOMAIN error.

To check if this is the case, go to a free WHOIS lookup tool like lookup.icann.org. Type in your domain name and look for the Registry Expiry Date.

If the date has already passed, log into your domain registrar like Namecheap, and pay the renewal fee to reactivate the domain.

2. Verify Your DNS Records and Nameservers

If your domain is active, then the problem could be due to a misconfigured DNS record. If you recently migrated your site to a new host, you might have entered the wrong IP address or forgotten to update your nameservers.

• A Record: This record tells DNS which server hosts your website. Make sure the IP address in your DNS settings matches the one provided by your hosting provider. A small mismatch can prevent visitors from reaching your site.

• Nameservers: Nameservers tell the internet where your DNS records are managed. If you’re using a DNS provider such as Cloudflare, make sure your nameservers are pointing there and not to your registrar’s default DNS service.

Log in to your domain registrar or hosting control panel. Open the DNS management section, and verify that your records are configured correctly. Pay attention to these records to make sure they’re pointing exactly where they should.

3. Give It Time for DNS Propagation

If you recently updated your nameservers, changed hosting providers, or renewed an expired domain, the changes may still be taking effect.

Usually, this process takes just a few hours, but it can sometimes take up to 48 hours to complete fully. During this waiting period, some visitors might see your site fine, while others get the NXDOMAIN error.

To check if the DNS propagation process is still in progress, you can use a free DNS checker like whatsmydns.net.

Enter your domain, select the ‘A‘ record, and hit search. If you see red crosses and green checkmarks, your site is still propagating, so give it some time.

4. Check Your CDN Configuration

If you use a CDN such as Cloudflare, it works as an intermediary between visitors and your website’s server. If its DNS settings are misconfigured, your visitors will encounter NXDOMAIN errors even though the origin server itself is online and functioning normally.

This can happen if you added your site to Cloudflare but didn’t update your domain’s nameservers yet. Or if the DNS records inside your Cloudflare dashboard are pointing to an old server IP address.

To check if this is causing the issue, log into your CDN dashboard. Make sure the A Record in there points to your current web host’s IP address.

If it does, temporarily pause or disable the CDN. In Cloudflare, you can use the “Pause Cloudflare” option to do this.

Wait a few minutes, clear your browser cache, and test your site. If it loads, you’ll know the issue is with your CDN settings.

Stop DNS Errors Before They Happen with Cloudflare Enterprise.

Prevent “site not found” errors and ensure your website stays reachable for every visitor with our built-in Cloudflare integration.

TRY NOW

How Cloudways Prevents the NXDOMAIN Error

As we saw in this guide, resolving DNS errors is easy but takes time to pinpoint the root cause. And every second your site is down, you’re losing traffic.

That’s why Cloudways offers built-in features to stop the NXDOMAIN error from happening in the first place, rather than just leaving you to troubleshoot a broken site.

Here are the two Cloudways add-ons you can use to keep your DNS routing completely stable.

1. DNS Made Easy Add-on

A major cause of NXDOMAIN errors is either your DNS provider experiencing an outage or the DNS propagation period taking too long to complete.

Like I mentioned earlier, when you update a DNS record, it can take up to 48 hours to complete. During which, visitors might see the NXDOMAIN error.

Cloudways integrates directly with DNS Made Easy, which is a premium DNS service with a 100% uptime history. When you use this add-on, your IP updates take effect instantly, minimizing the likelihood of visitors encountering DNS-related connectivity issues.

2. Cloudflare Enterprise Integration

DNS misconfigurations and incorrect record settings are also common causes of NXDOMAIN errors. Cloudways offers a built-in Cloudflare Enterprise integration to solve this.

Because Cloudflare operates one of the fastest, and most reliable DNS networks, it automatically handles your traffic routing and syncs your records at the edge.

This reduces DNS resolution issues, propagation delays, and routing inconsistencies that can otherwise make a website temporarily unreachable.

Final Thoughts

The DNS_PROBE_FINISHED_NXDOMAIN error is frustrating to see, but rarely a permanent error that can’t be fixed.

For everyday users, simple fixes like clearing cache or restarting the router are enough to resolve the error. For website owners, double-checking domain status and DNS records is usually all it takes to get the site back online.

If you’re a website owner and don’t want to worry about manual DNS configurations or propagation delays, consider migrating to Cloudways. We offer built-in tools like Cloudflare Enterprise, DNS Made Easy add-on and a lot more to keep your routing stable, preventing these errors from affecting your traffic in the first place.