DNS Troubleshooting Guide: How to Fix Common Website and Email Record Errors
dnsdns-troubleshootingemail-dnsdomain-managementwebsite-errors

DNS Troubleshooting Guide: How to Fix Common Website and Email Record Errors

WWebArchive Editorial Team
2026-11-15
6 min read

Diagnose website and email DNS errors with a record reference, propagation checklist, verification workflow, and recurring audit plan.

DNS changes can affect a website, email delivery, domain verification, and security controls at the same time. This guide explains how to identify the failing record, distinguish a configuration error from normal propagation, verify results from multiple locations, and maintain a repeatable DNS troubleshooting process after migrations or service changes.

Overview

The Domain Name System translates human-readable names such as example.com into the addresses and service destinations that browsers, mail servers, and other applications use. When a record is missing, duplicated, pointed at the wrong destination, or published at the wrong DNS provider, the visible symptom may be “the website is down” or “email is not working,” even though the underlying problem is more specific.

Start by defining the exact failure. Is the root domain unavailable, is only www failing, are some users seeing an old site, or are outgoing messages being rejected? A precise symptom narrows the search. Also record the time of the change, the DNS provider currently authoritative for the domain, the intended value, and the value that public resolvers are returning.

Do not change several records at once unless an outage requires immediate containment. One controlled change followed by verification gives you a clear cause-and-effect trail. If you are connecting a domain to a new host, compare this process with the broader guide to connecting a domain to web hosting.

What to track

Maintain a simple DNS inventory for every active domain. The inventory should identify the record name, type, intended value, purpose, owner, and date last reviewed. The following records account for many website and email problems:

RecordWhat it controlsCommon failure
AMaps a hostname to an IPv4 address.The address points to an old server, a parking page, or the wrong environment.
AAAAMaps a hostname to an IPv6 address.IPv6 users reach an unavailable or incorrectly configured server even though IPv4 works.
CNAMEAliases one hostname to another hostname.The alias targets the wrong service, conflicts with another record, or is added at the wrong name.
MXSpecifies where mail for a domain should be delivered.Mail is routed to an old provider, or the target hostname cannot be resolved.
TXTStores verification and email-policy text.A token is incomplete, an SPF policy is duplicated, or a required value is published on the wrong host.
NSIdentifies the authoritative nameservers for a domain or delegated subdomain.Changes are made in a dashboard that is not authoritative for the domain.

For email, track MX records separately from SPF, DKIM, and DMARC records. MX determines delivery routing; SPF, DKIM, and DMARC influence authentication and policy. A domain can have correct MX records and still experience authentication failures. Use the SPF, DKIM, and DMARC setup guide when auditing those records.

Also record the TTL, or time to live, for important records. TTL tells recursive resolvers how long they may retain an answer in cache. It does not force every resolver to refresh at the same moment, and changing a TTL does not erase answers that were already cached under the previous value.

Cadence and checkpoints

Use a three-stage verification workflow after any DNS change.

  1. Check the authoritative source. Confirm the record in the DNS provider or nameserver that is authoritative for the domain. First verify the active NS records, then inspect the record at the provider those nameservers identify.
  2. Query public resolvers. Check the record using more than one recursive resolver or a DNS propagation checker. Compare the returned value, status, and TTL. Differences shortly after a change may reflect caching; persistent differences may indicate delegation or configuration problems.
  3. Test the service itself. Load the website over both the root hostname and any intended subdomain. For email, send and receive controlled test messages and inspect bounce messages or authentication results. A DNS answer alone does not prove that the web server, TLS configuration, or mail service is healthy.

For routine maintenance, review the DNS inventory monthly or quarterly according to the importance and change rate of the domain. A quarterly review is often sufficient for a stable brochure site; domains supporting frequent deployments, customer accounts, or multiple email services deserve a more regular operational check.

Create extra checkpoints after a hosting migration, registrar transfer, nameserver change, email-provider change, or addition of a third-party verification service. Keep the old hosting account available until the new records and services have been tested. The website migration checklist can help coordinate DNS with backups, redirects, and application testing.

How to interpret changes

Use the symptom to choose a path rather than editing records at random:

  • The website fails everywhere: Check NS delegation first, then the A and AAAA records. Confirm that the destination server is running, accepts the hostname, and has a valid TLS configuration. If only one hostname fails, inspect its specific record rather than the entire zone.
  • The website works for some people but not others: Compare answers from multiple recursive resolvers and networks. This can be normal during cache transition, but it can also indicate inconsistent authoritative nameservers or both old and new records being published.
  • The root domain works but www does not: Check the www A or CNAME record, the web server’s configured hostnames, and any redirect rule. A working root record does not automatically configure its subdomain.
  • Email stopped after a DNS change: Check MX priority and target names, then verify that each MX target resolves. Confirm that the domain’s mail provider still expects the published records. Do not remove authentication records simply because the immediate symptom is a bounce.
  • A verification service cannot find a TXT record: Confirm the exact record name, including whether the provider expects the root domain or a subdomain. Check for split or incorrectly quoted values and verify the record publicly rather than relying only on the provider dashboard.
  • IPv4 works but some connections fail: Inspect the AAAA record. An obsolete IPv6 address can direct compatible clients to a server that is offline, blocked, or not configured for the domain.

Common DNS errors have straightforward causes. “NXDOMAIN” generally means the queried name does not exist according to the responding authority, while “SERVFAIL” can indicate delegation, DNSSEC, nameserver, or server-side problems. A timeout may be caused by network conditions or an unreachable nameserver, not necessarily by a missing record. Treat these results as clues and compare them with authoritative answers and service tests.

Be careful with record conflicts. A hostname generally should not have a CNAME alongside other data at the same name, and multiple SPF TXT records can produce an invalid or unpredictable policy. Follow the requirements of the relevant service and preserve a change log before consolidating or deleting records.

When to revisit

Revisit this troubleshooting process whenever a site changes hosts, a domain changes registrars, nameservers are updated, a new email provider is introduced, or a service requests a verification record. Repeat the review after a security incident, unexpected email rejection, unexplained regional outage, or change to IPv6 support.

At each monthly or quarterly checkpoint, confirm that the authoritative nameservers are still expected, remove records for retired services, review unusual subdomains, and compare public answers with your inventory. Check that SSL certificates, website redirects, backups, and mail authentication are still aligned with the current infrastructure. Domain renewal and expiration are also operational risks; use the domain expiration and renewal guide to prevent an avoidable loss of DNS control.

When an incident occurs, save the evidence before making further changes: timestamped DNS answers, authoritative nameservers, provider screenshots or exports, bounce messages, and the exact commands or tools used. Then make one correction, wait long enough to observe resolver changes, and repeat the three-stage verification workflow. This turns DNS troubleshooting from guesswork into a maintainable reliability practice.

Related Topics

#dns#dns-troubleshooting#email-dns#domain-management#website-errors
W

WebArchive 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.