Have you opened a website in Google Chrome only to see the message DNS_PROBE_FINISHED_NXDOMAIN? This error can be frustrating, especially when you need to access an important website or manage your own domain.

The good news is that you can often resolve the problem by correcting a DNS setting, clearing a cached lookup, or checking your internet connection. However, if the problem affects a website you own, the cause may be an incorrect DNS record, an expired domain, or a nameserver configuration issue.

In this guide, you will learn what the error means, how to fix it on Windows, and what to check if your own website is unavailable.

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

DNS stands for Domain Name System. It translates human-readable domain names, such as example.com, into the IP addresses computers use to connect to websites.

The error DNS_PROBE_FINISHED_NXDOMAIN means that the DNS resolver returned a response indicating that the requested domain name does not exist. In some cases, the cause is local to your computer or network. In others, the domain’s DNS configuration needs attention.

Common causes include:

• A temporary DNS cache problem on your computer.
• A mistyped website address.
• Incorrect DNS server settings.
• Missing or incorrect DNS records.
• Incorrect nameservers at the domain registrar.
• An expired domain or registration issue.
• DNSSEC configuration problems.
• A recent DNS change that has not reached all resolvers.

Important: If only one website is affected, investigate that domain first. If many websites fail to load, start with your computer, router, or DNS resolver.

Quick Fixes to Try First

Before changing advanced settings, try these simple checks:

1. Check the website address for spelling mistakes.
2. Open another website to see whether your internet connection works.
3. Try the affected website in another browser.
4. Connect through another network, such as a mobile hotspot.
5. Restart your browser and, if necessary, your router.
6. Check whether the domain has expired or its DNS settings have changed.

If the error persists, follow the solutions below in order.

1. Clear the DNS Cache in Windows

Windows stores recently resolved domain names in a local DNS cache. If an incorrect or outdated result has been cached, clearing the cache can help Windows request fresh DNS information.

Steps to clear the cache

1. Open the Start menu.
2. Search for Command Prompt.
3. Open Command Prompt.
4. Enter the following command:

ipconfig /flushdns

5. Press Enter and wait for the confirmation message.
6. Close the window and reload the website.

This command clears the local Windows DNS resolver cache. It does not repair incorrect DNS records on a website’s server.

If the error remains, continue to the next solution.

2. Clear Chrome’s DNS Cache

Google Chrome maintains its own network-related caches. Clearing Chrome’s host cache can help when the browser continues using an outdated DNS result.

Steps

1. Open Google Chrome.
2. Enter the following address in the address bar:

chrome://net-internals/#dns

3. Press Enter.
4. If the page provides a Clear host cache button, select it.
5. Close and reopen Chrome.
6. Try loading the website again.

The exact diagnostic interface can vary by Chrome version. If the address or control is unavailable, skip this step and continue with the operating system and network checks.

3. Change Your DNS Server

Your internet service provider normally supplies the DNS servers your device uses. If the configured resolver is experiencing problems, switching to a reputable public DNS service may help.

Two widely used options are:

Choose one provider rather than mixing the two unnecessarily.

How to change DNS in Windows 11

1. Open Settings.
2. Select Network & internet.
3. Open your active Wi-Fi or Ethernet connection.
4. Find the DNS server assignment setting.
5. Select Edit and choose Manual.
6. Enable IPv4.
7. Enter the preferred and alternate DNS addresses for your chosen provider.
8. Save the settings and test the website again.

Menu names can vary slightly between Windows versions.

If you are using a managed workplace or school network, check with the network administrator before changing DNS settings.

Remember: Changing DNS providers will not fix a domain that has missing records, incorrect nameservers, or an expired registration.

4. Restart Your Computer and Router

A temporary network problem may affect DNS resolution. Restarting your computer and router can help establish a fresh network connection.

Follow these steps:

1. Save your work and close open applications.
2. Restart your computer.
3. Restart your router or modem using its normal power procedure.
4. Wait for the connection to return.
5. Open the affected website.

If possible, test the website using a mobile hotspot. If it works on the hotspot but not on your normal connection, investigate your router, ISP, or configured DNS resolver.

If it fails on multiple unrelated networks, the domain itself may need attention.

5. Renew Your IP Configuration

If the problem is related to your computer’s network configuration, renewing its DHCP-assigned IP configuration may help.

Open Command Prompt and run the following commands one at a time:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

The first command releases the current DHCP-assigned address, and the second requests a new configuration. Your connection may temporarily disconnect while these commands run.

Do not run these commands through a remote connection that depends on the same network unless you have another way to reconnect.

Afterward, reopen your browser and test the website.

6. Check Your VPN, Proxy, and Security Software

A VPN, proxy server, firewall, or security application may affect how your device resolves domain names.

To investigate:

1. Check whether a VPN is connected.
2. If appropriate, disconnect the VPN temporarily.
3. Review your proxy settings.
4. Check whether a security application provides DNS filtering or parental controls.
5. Retry the website.

Do not permanently disable your firewall or antivirus software to fix a DNS error. If a security product is responsible, adjust the relevant setting safely or consult its support documentation.

If the website works only when a VPN is enabled, the issue could involve your normal network, DNS resolver, or network-level filtering.

7. Check Whether the Domain Name Is Correct and Active

If you are trying to visit a specific website, make sure the domain is spelled correctly and remains registered.

For example, these are separate hostnames:

• example.com
• www.example.com
• blog.example.com

A domain may resolve correctly while one of its subdomains does not.

If you own the domain, check the following:

• The domain registration has not expired.
• The domain is not subject to a registration hold.
• The registrar lists the intended nameservers.
• The authoritative DNS zone contains the required records.
• Both the root domain and www hostname are configured if you use both.

You can start by looking up the domain using Google Public DNS. For more detailed diagnostics, use Google’s domain troubleshooting guide.

8. Fix DNS Records for Your Own Website

If visitors receive DNS_PROBE_FINISHED_NXDOMAIN when accessing your website, inspect the DNS zone at the provider responsible for hosting your DNS records.

Common records include:

Example DNS configuration

A typical website might use records conceptually similar to these:

Type    Name    Value
A       @       YOUR_SERVER_IPV4
CNAME   www     example.com

These are illustrative values, not records you should copy blindly. Replace the example domain and server address with the correct values for your own hosting setup. Your hosting provider may require a different configuration.

What to verify

Check the root domain. Confirm that the apex domain has the record required by your hosting provider.

Check the www hostname. Make sure www has a valid A or CNAME configuration.

Check nameservers. The nameservers at the registrar should match the provider where you manage the DNS zone. If you recently changed DNS providers, confirm that the required records exist at the new provider.

Check for conflicting records. Remove incorrect or obsolete records only after confirming that they are not needed for your website, email, verification, or other services.

Allow for DNS caching. DNS changes can take time to become visible across resolvers. The delay depends on record TTLs, caching, and the type of change. Repeatedly changing records can make troubleshooting more difficult.

For Cloudflare users, see its official guide to DNS_PROBE_FINISHED_NXDOMAIN.

9. Check DNSSEC Configuration

DNSSEC adds a layer of authenticity to DNS responses. Incorrect DNSSEC configuration can prevent validating resolvers from resolving a domain successfully.

This can happen after a domain moves between DNS providers if the parent-zone DS record no longer matches the DNSSEC configuration at the new provider.

If your domain has recently changed registrars, nameservers, or DNS providers:

1. Check the domain’s DNSSEC status with your registrar.
2. Review the DNSSEC configuration at your DNS provider.
3. Use a DNSSEC diagnostic tool to identify validation errors.
4. Contact your registrar or DNS provider before removing or changing DS records.

Do not disable DNSSEC as a guess. First confirm that a DNSSEC validation problem is actually present.

For more information, consult Google’s domain troubleshooting documentation.

10. Use Command-Line Tools to Find the Cause

If the previous solutions do not work, compare DNS responses from different resolvers.

Open Command Prompt on Windows and run:

nslookup example.com
nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1

Replace example.com with the affected domain.

How to interpret the results

• All lookups fail: The domain, its authoritative nameservers, or a broader DNS issue may be responsible. Confirm that the domain exists and check its DNS configuration.
• Only your default resolver fails: Your ISP’s DNS resolver or local network configuration may be involved.
• The root domain works but www fails: Check the DNS record for www.
• The domain resolves to an unexpected IP address: Review the A or AAAA records and any DNS proxy configuration.
• The domain resolves but the website still does not open: Investigate the web server, hosting configuration, TLS certificate, firewall, and HTTP response. The issue may no longer be DNS-related.

A successful lookup does not guarantee that a website is healthy. It only confirms that the hostname resolved to a DNS answer.

What If the Error Affects Only Your Website?

Website owners should avoid assuming that the error is caused by the visitor’s computer. If several visitors report the same issue, investigate the domain and its DNS provider.

Use this diagnostic sequence:

1. Confirm the domain’s registration status.
2. Check the nameservers configured at the registrar.
3. Check the A, AAAA, and CNAME records for the root domain and relevant subdomains.
4. Verify that the records point to the correct hosting destination.
5. Check DNSSEC if the domain recently changed providers or resolvers report validation errors.
6. Compare lookup results from multiple public resolvers.
7. Contact the registrar, DNS provider, or hosting company if the authoritative configuration is incorrect.

For more advanced investigation, Google’s DNS troubleshooting guide explains how to compare resolver responses and investigate authoritative nameserver problems.

Frequently Asked Questions

1. Is DNS_PROBE_FINISHED_NXDOMAIN a problem with Chrome?

Not necessarily. Chrome displays the error, but the underlying cause may be the computer’s DNS cache, the configured resolver, the network, or the domain’s DNS configuration.

2. Will flushing DNS fix the error?

It can help when an incorrect or outdated DNS response is cached locally. It will not repair missing DNS records, incorrect nameservers, an expired domain, or a DNSSEC configuration error.

3. Why does a website work on mobile data but not on Wi-Fi?

Different networks may use different DNS resolvers. If the website works on mobile data, investigate the Wi-Fi router, ISP, or DNS resolver before changing the website’s records.

4. Why does my website work without www but not with www?

The root domain and the www hostname are separate DNS names. The www hostname may be missing a record or may point to the wrong destination. Check both hostnames in your DNS provider’s dashboard.

5. How long does it take for DNS changes to work?

There is no universal propagation time. Some changes become visible within minutes, while cached responses may remain available until their TTL expires. Resolver behavior and DNS configuration also affect the result.

6. Can an expired domain cause this error?

Yes. If a domain expires or its registration is placed on hold, it may stop resolving normally. Check its registration status and resolve any registrar-related issues.

7. What should I do if none of these fixes works?

Run the nslookup tests, compare results from multiple networks, and check the domain’s registration, nameservers, DNS records, and DNSSEC status if you manage the domain. Share the diagnostic results with your ISP, registrar, DNS provider, or hosting company as appropriate.

Final Thoughts

The DNS_PROBE_FINISHED_NXDOMAIN error means that a DNS lookup returned a result indicating that the requested domain does not exist. The best fix depends on where the failure occurs.

Start with the simple steps: verify the address, clear the local DNS cache, restart the network connection, and test another resolver. If the problem affects a website you own, focus on domain registration, nameservers, DNS records, and DNSSEC configuration.

By identifying whether the issue is local or domain-wide, you can avoid unnecessary changes and get back to browsing or managing your website more efficiently.