DNS_PROBE_FINISHED_NXDOMAIN

What this error means & how to recognize it

• Chrome or Edge shows “This site can’t be reached — DNS_PROBE_FINISHED_NXDOMAIN.”
• Another browser reports that the server cannot be found or the domain cannot be resolved.
• The error affects one hostname, such as www.example.com, or every hostname under the domain.
• A newly registered, transferred, or recently reconfigured domain fails to resolve.
• The failure repeats across networks, suggesting a DNS or domain configuration issue rather than an isolated browser problem.
• If DNS resolves successfully but the site still fails, the issue is likely elsewhere, such as the web server, TLS configuration, or application.

Root causes, ordered by likelihood

1. The exact hostname has no DNS record. A record for example.com does not automatically create one for www.example.com or another subdomain.
2. The domain uses the wrong nameservers, or the authoritative zone lacks the required records. This often follows a hosting move, registrar change, or nameserver update.
3. A DNS change is still propagating, or a resolver has cached an earlier NXDOMAIN response. This is particularly likely after creating a record or changing delegation.
4. The hostname was entered incorrectly. A missing character, incorrect domain extension, or unintended subdomain can produce NXDOMAIN.
5. The domain has expired or been suspended. A registrar or registry hold can prevent the domain’s delegation from resolving.
6. The authoritative DNS configuration is incomplete or invalid. The intended provider may not have the zone or required record configured for the domain.

How to fix it

1. Verify the exact hostname

Read the browser address carefully and compare it with the name you intended to publish. Check:

• example.com versus www.example.com
• Spelling and domain extension
• Subdomains such as shop.example.com or mail.example.com

Do not assume that a working apex domain means every subdomain is configured.

2. Check the hostname from another network or resolver

Use an independent DNS lookup service or a DNS query from a different network. Query the exact failing hostname and inspect its A, AAAA, or CNAME result as applicable.

If independent resolvers also return NXDOMAIN, the problem is probably authoritative DNS, nameserver delegation, the domain itself, or a genuinely missing record. If only one device or network fails, investigate its local resolver or cache.

3. Confirm the authoritative nameservers

At the registrar or a domain lookup service, check which nameservers the domain uses. They should match the DNS provider you intend to manage.

Then sign in to that provider and confirm that the domain’s DNS zone exists. If delegation points to a new provider, editing records at the old provider will not fix the domain.

4. Add or correct the record for the failing name

At the authoritative DNS provider, create or update the record for the exact hostname:

• Use an A record for an IPv4 address.
• Use an AAAA record for an IPv6 address when applicable.
• Use a CNAME record when the hostname should resolve to another hostname.

Check the record name, target, and provider-specific formatting. Avoid conflicting records that the provider does not allow. Save the change, then query the hostname again from an independent resolver.

5. Check domain registration status

If the apex domain and all subdomains fail, inspect the registrar account for expiration, suspension, or a hold. Confirm that renewal succeeded and that the domain remains delegated to the intended nameservers.

A registrar or registry problem must be corrected there; changing an individual A record will not resolve it.

6. Allow for propagation and negative caching

After a record or nameserver fix, recursive resolvers may continue returning a cached NXDOMAIN response. Flush the DNS cache on the affected computer and restart the browser if necessary, but use independent lookups to determine whether the change is visible beyond that device.

Resolution may return within minutes, but the timing depends on previous TTL values, the type of change, and cached responses. Nameserver changes can sometimes take up to 48 hours to appear consistently.

7. Separate DNS resolution from website availability

Once the hostname returns an address or CNAME, try loading it again. If DNS resolves but the browser shows a timeout, certificate warning, server error, or application error, continue with web-server, hosting, TLS, or application diagnostics rather than treating it as NXDOMAIN.

Prevention & how to verify the fix

• Keep an external record of the intended nameservers and important DNS records for comparison after hosting or registrar changes.
• Before changing nameservers, recreate and verify the required DNS zone at the new provider where appropriate.
• Use TTL values that fit the expected change frequency; very long TTLs can delay later corrections.
• Test both the apex domain and important hostnames such as www after publishing DNS changes.
• Set renewal reminders and keep registrar contact and account details current.
• Verify DNS changes from an independent resolver or external network instead of relying only on the local browser.

Frequently asked questions