DNS & Domain Errors

About this error category

# DNS & Domain Errors

DNS errors occur when a hostname cannot be translated into the IP address or service endpoint needed to reach a website. The browser message may mention DNS, but the underlying problem can be limited to one device, affect a local network, or involve the domain's records, nameservers, or registration status.

Common symptoms

DNS and domain problems can appear as:

• DNS_PROBE_FINISHED_NXDOMAIN in a browser.
• DNS_PROBE_FINISHED_BAD_CONFIG or another resolver-related message.
• A hostname that works for some people but not others.
• A newly registered domain or recently changed record that does not resolve.
• A bare domain that works while www or another subdomain fails.
• A hostname that fails on one network while other websites continue to load.
• A domain that resolves to the wrong address after a DNS change.

The exact result matters. NXDOMAIN means the DNS lookup received an answer stating that the name does not exist. That differs from a timeout, a refused query, or an HTTP or TLS error returned after DNS resolution has succeeded.

First determine the scope of the failure

Before editing DNS records, establish whether the problem affects one device, one network, or the domain from multiple locations:

1. Test the hostname from another connection, such as mobile data instead of the affected Wi-Fi network.
2. Test another device if one is available.
3. Check the bare domain, www, and any relevant subdomain separately.
4. If only one device or network fails, inspect its DNS settings, VPN, security software, router, and cached results.
5. If the hostname fails consistently across different networks, inspect the domain's authoritative DNS records and delegation.

If the hostname works elsewhere, changing authoritative records is unlikely to fix the affected device. A failure across several independent networks is stronger evidence of a domain, zone, nameserver, or registration problem.

Check authoritative DNS configuration

For a domain-wide failure, verify the configuration at the DNS provider that is authoritative for the domain. Check that:

• The domain uses the intended authoritative nameservers.
• Those nameservers are correctly delegated at the registrar or parent zone.
• The required A or AAAA record exists for the exact hostname being tested.
• A CNAME points to the intended target and is not combined with conflicting records where the DNS provider disallows that arrangement.
• www has its own correct record or alias if visitors use it.
• The record is in the correct DNS zone and the hostname has not been duplicated or entered incorrectly.
• The destination belongs to the intended hosting or service provider.

A record can be validly formatted and still point to the wrong service. If DNS returns the expected destination but the browser shows an HTTP status, redirect failure, connection error, or certificate warning, investigate hosting, the web server, TLS, firewall rules, or the application rather than repeatedly changing DNS.

Understand DNS caching and propagation

Recursive DNS resolvers cache answers according to each record's TTL. After a legitimate change, different networks can temporarily return different answers because they received the old and new responses at different times.

Waiting does not repair a missing record, incorrect nameserver delegation, a misspelled hostname, or a change made at the wrong DNS provider. Confirm the exact hostname, the authoritative provider, and the current delegation before treating the issue as propagation. Repeatedly changing a record can make the results harder to interpret and may extend inconsistent caching.

Use the specific error as a clue

DNS_PROBE_FINISHED_NXDOMAIN

This response generally means the resolver was told that the queried name does not exist. Check the hostname for spelling errors, confirm that the domain is registered and active, and verify nameserver delegation and the required records. If the name works from another network, compare local DNS settings and cached answers before changing authoritative records.

See the guide for [DNS_PROBE_FINISHED_NXDOMAIN](dns-probe-finished-nxdomain) for focused checks.

DNS_PROBE_FINISHED_BAD_CONFIG

This usually indicates that the device or local network cannot use its configured DNS service correctly. Compare the result on another network, inspect the configured DNS servers, and check the router, VPN, or security software. If only one domain fails across multiple networks, investigate that domain's delegation and records instead of assuming the device is misconfigured.

See the guide for [DNS_PROBE_FINISHED_BAD_CONFIG](dns-probe-finished-bad-config) for step-by-step diagnosis.

When to contact another provider

Contact the registrar or DNS provider when nameservers are incorrect, the zone is missing, the domain has a registration or account issue, or records cannot be changed as expected. Contact the hosting provider or web administrator when DNS resolves to the intended destination but the site returns an HTTP, redirect, connection, TLS, or application error.

When escalating, record the exact hostname, when the problem began, which networks were tested, and the DNS result observed. This helps distinguish a local cache or resolver issue from a delegation, zone, or hosting failure.