DNS Troubleshooting Guide: Find and Fix Common Website Resolution Errors
DNSnameserversDNS propagationsubdomainswebsite troubleshooting

DNS Troubleshooting Guide: Find and Fix Common Website Resolution Errors

vvarious.cloud Editorial Team
2026-11-16
8 min read

Use this DNS troubleshooting checklist to diagnose domain resolution, nameserver, propagation, subdomain, email, and hosting errors.

When a domain stops loading after a DNS change, the cause may be an incorrect record, outdated delegation, resolver caching, or a separate hosting problem. This reusable DNS troubleshooting checklist shows how to isolate each possibility, verify results from more than one network, and fix common errors such as NXDOMAIN, SERVFAIL, redirect loops, and intermittent resolution.

Overview

DNS management connects a human-readable domain name with services such as a website, email platform, or application. A typical website setup may involve an A record pointing a name to an IPv4 address, an AAAA record for IPv6, a CNAME record pointing a subdomain to another hostname, and NS records identifying the authoritative nameservers for the domain.

DNS troubleshooting is easiest when you separate the process into three questions:

  1. Delegation: Which nameservers are authoritative for the domain?
  2. Configuration: Do those nameservers publish the records you intended?
  3. Service: Does the destination hosting server respond correctly once the name resolves?

A browser error does not identify which layer failed. Start with DNS queries, then test the hosting destination, HTTPS configuration, and application behavior. Avoid making several changes at once; changing multiple records makes it harder to identify the original cause.

For a new website, record the intended DNS setup before editing it. Include the registrar, DNS provider, nameservers, website address, email provider, record types, values, and TTL settings. This small inventory is particularly useful during a hosting migration or domain transfer. For related launch steps, see the cloud hosting website launch workflow.

Checklist by scenario

Scenario 1: The domain does not resolve at all

  1. Confirm the domain is spelled correctly, including the top-level domain.
  2. Check the domain's nameservers at the registrar. They should match the nameservers supplied by the DNS provider you intend to use.
  3. Check the DNS provider's zone for the exact hostname. The root domain is usually written as @ or left blank, while www is a separate name.
  4. Confirm that an appropriate A, AAAA, or CNAME record exists for the name visitors are using.
  5. Query the domain through more than one public resolver and, if possible, from a different network.

An NXDOMAIN response means the queried name does not exist from the perspective of the responding DNS system. Check for a misspelled hostname, a missing record, incorrect delegation, or a zone that has not been created at the active DNS provider. If the root domain works but www returns NXDOMAIN, troubleshoot the www record specifically rather than changing the root record.

Scenario 2: The domain sometimes works and sometimes fails

Intermittent results often indicate different resolvers have cached different answers, or that more than one authoritative nameserver is returning inconsistent data. Query the domain repeatedly using different resolvers and compare the returned address and authoritative nameserver. If the answers differ unexpectedly, review recent record edits and nameserver configuration.

Also check for old and new hosting addresses being published at the same time. Multiple A records can be intentional, but they can also send visitors to a retired server. An old AAAA record is another common cause: some networks may prefer IPv6 and reach a server that is not configured for the website.

Scenario 3: The domain returns SERVFAIL

SERVFAIL indicates that a resolver could not obtain or validate a usable answer. Check the authoritative nameservers, their availability, and whether the DNS zone contains a configuration error. If DNSSEC is enabled, verify that the DS information at the registrar matches the DNSSEC signing configuration at the DNS provider. A mismatch can make a domain fail validation even when ordinary records appear correct.

Do not remove DNSSEC automatically. Treat that as a deliberate security decision and first compare the registrar's DS record with the DNS provider's current settings or contact the responsible provider for a controlled correction.

Scenario 4: The domain resolves, but the website does not load

Once a DNS query returns the expected address, DNS may be working correctly. Confirm that the address belongs to the intended hosting service, that the server accepts the domain in its hosting configuration, and that ports for HTTP and HTTPS are reachable. A default hosting page, connection timeout, or application error usually requires investigation in the hosting panel or server logs rather than another DNS edit.

If HTTP redirects to HTTPS and the browser reports a redirect loop, review both the hosting platform and any proxy or CDN settings. Check whether the origin expects HTTP while the proxy repeatedly redirects the request to HTTPS, or whether the application has conflicting URL settings. DNS records alone do not create an HTTP redirect.

Scenario 5: A subdomain or business email stopped working

For a subdomain such as app.example.com, verify that the record is created under the correct parent zone and that its target is valid. A CNAME target should be a hostname, not an IP address. Check for a conflicting record at the same name; a hostname should not have both a CNAME and other data records at that exact label.

Email uses different records from website hosting. Confirm the intended MX records and their priorities, then review SPF, DKIM, and DMARC records with the email provider. Do not replace working email records while fixing a website record. The business email DNS guide provides a separate checklist for those records.

What to double-check

Nameserver delegation

The registrar's nameserver setting determines where the public DNS zone is managed. Editing records at a different provider has no effect if the domain is delegated elsewhere. After a nameserver migration, compare the delegation shown by the registrar with the nameservers returned by an authoritative query. Keep the old DNS zone available until the new zone contains every required website, verification, and email record.

Record names and values

DNS control panels vary in how they display the root domain. A field labeled “Name” may expect @, a blank value, or the full domain. Read the provider's field guidance before entering a record. Check for accidental trailing punctuation, copied quotation marks, an incomplete hostname, or an IP address with a typo. For a CNAME, confirm whether the provider automatically appends the domain name; entering a full name where a relative name is expected can produce an unintended target.

TTL and propagation

TTL, or time to live, tells caching resolvers how long they may retain an answer. A lower TTL can help during planned changes, but it does not force every resolver to refresh immediately. Cached data may remain until the previous TTL expires, and some browser, operating-system, router, or corporate-network caches may behave differently.

Propagation is therefore not a substitute for configuration testing. First verify the authoritative answer; then compare recursive resolvers. If the authoritative server still returns the old value, the change was made in the wrong zone or has not been published. If the authoritative answer is correct but a recursive resolver is old, waiting for its cache to expire may be appropriate. Do not repeatedly edit the record simply because one network has not updated.

Command-line checks

From a terminal, use tools available on your system to inspect specific record types:

  • dig example.com A checks the IPv4 address.
  • dig www.example.com CNAME checks the subdomain alias.
  • dig example.com NS checks the nameserver records returned for the domain.
  • dig example.com MX checks mail routing.
  • dig @1.1.1.1 example.com A queries a particular recursive resolver, if that resolver is available on your network.
  • nslookup example.com provides a simpler cross-platform check.

Compare the answer section, status code, TTL, and responding server. These commands show DNS results; they do not prove that the web server, certificate, or application is healthy.

Common mistakes

  • Editing the wrong DNS provider: The registrar, hosting provider, and DNS provider may be separate companies. Confirm which nameservers are active before making changes.
  • Creating duplicate or conflicting records: Review existing A, AAAA, and CNAME records before adding new ones. Remove obsolete entries only after confirming they are no longer needed.
  • Forgetting the subdomain: A working root domain does not automatically make www, mail, api, or another subdomain work.
  • Changing DNS to fix an HTTPS problem: If the name resolves to the right server, investigate the SSL certificate, virtual host, proxy, or application settings. See the SSL certificate troubleshooting checklist.
  • Testing only in one browser: Use a private window, a second browser, a different network, and command-line queries to separate local cache from public DNS behavior.
  • Changing several records at once: Make one controlled change, note the time and intended result, then test before continuing.
  • Ignoring email during a hosting move: Website migration does not necessarily require changing mail records. Preserve working MX, SPF, DKIM, and DMARC configuration unless the email service is also changing.

When to revisit

Return to this checklist whenever you change nameservers, move hosting, launch a subdomain, alter email providers, renew or modify DNSSEC, or update a website's canonical domain. Use it before planned seasonal campaigns or other high-traffic periods, when a small configuration error has a larger operational cost.

Review your DNS inventory at least when your infrastructure or provider workflow changes. Provider dashboards, command-line examples, browser behavior, and hosting-panel labels can change over time, so refresh internal documentation when those tools change. Keep a dated record of the previous and new values, TTL settings, test results, and the person responsible for the change.

For the next incident, follow this order: check delegation, query the authoritative nameserver, compare recursive resolvers, verify the exact record, test the hosting destination, and then inspect HTTPS or application behavior. This sequence prevents a propagation problem from being confused with a hosting outage and gives you evidence before you make another edit.

Related Topics

#DNS#nameservers#DNS propagation#subdomains#website troubleshooting
v

various.cloud Editorial Team

Technology Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.