DNS Troubleshooting for Developers: A Record, CNAME, TXT, MX, and TLS Verification Checklist
DNSdomain managementhostingTLSCDNemail authentication

DNS Troubleshooting for Developers: A Record, CNAME, TXT, MX, and TLS Verification Checklist

NNetworked DevOps Editorial Team
2026-11-13
8 min read

A practical DNS troubleshooting checklist for A, CNAME, TXT, MX, NS, CAA, CDN routing, email verification, propagation, and TLS problems.

When a domain, subdomain, email service, or TLS certificate stops working after a DNS change, the fastest path to an answer is a structured comparison of what you intended, what the authoritative nameservers publish, and what recursive resolvers return. This DNS troubleshooting checklist gives developers and IT teams a reusable workflow for checking records, identifying stale or conflicting data, validating CDN and hosting routes, and separating DNS problems from application and certificate problems.

Overview

DNS translates names such as app.example.com into information that clients use to connect to a service. A DNS failure can therefore appear as a website outage, a failed domain-verification message, missing email, an unexpected CDN response, or a TLS certificate warning. These symptoms often have different causes.

Start by documenting the intended configuration before changing anything:

  • The hostname affected, including whether it is the root domain or a subdomain.
  • The expected record type and value.
  • The DNS provider or authoritative nameservers responsible for the zone.
  • The hosting, CDN, email, or certificate platform that should receive the request.
  • The time of the change and the previous value, if available.

DNS troubleshooting works best in layers. First confirm delegation through the NS records. Then query the authoritative nameserver directly. Finally compare that answer with results from one or more recursive resolvers. This distinguishes a bad record from a cached answer, a local resolver issue, or a service configured incorrectly behind DNS.

Record reference

RecordPurposeChecks to perform
AMaps a hostname to an IPv4 address.Confirm the address belongs to the intended host, load balancer, or edge service.
AAAAMaps a hostname to an IPv6 address.Check it separately; a broken IPv6 route can affect clients even when IPv4 works.
CNAMEAliases a name to another hostname.Verify the target, trailing dot handling in provider interfaces, and whether the target resolves.
TXTStores text used for verification, SPF, DKIM-related data, and other policies.Check exact spelling, quotation handling, and whether long values were split correctly.
MXSpecifies mail servers and their priorities.Confirm hostnames, priority order, and that each mail host has address records.
NSIdentifies authoritative nameservers for a zone.Compare registrar delegation with the nameservers configured at the DNS provider.
CAAControls which certificate authorities may issue certificates for a domain.Check that the requested certificate authority is permitted, including relevant wildcard or validation behavior.

Checklist by scenario

1. Establish the authoritative answer

Use dig where available:

dig NS example.com
dig A app.example.com
dig AAAA app.example.com
dig CNAME app.example.com
dig TXT example.com
dig MX example.com
dig CAA example.com

For a more complete response, add +noall +answer. To query a specific authoritative server, first obtain the zone's nameserver, then run:

dig @ns1.example-dns.com app.example.com A

Compare this result with a recursive lookup:

dig @1.1.1.1 app.example.com A
dig @8.8.8.8 app.example.com A

The resolver addresses above are examples of public resolvers; use an approved resolver for your environment when testing sensitive infrastructure. On systems without dig, use nslookup or host:

nslookup -type=TXT example.com
host -t MX example.com

2. A domain or subdomain does not open

  1. Check both A and AAAA records. An incorrect AAAA record can send some clients to an unreachable endpoint.
  2. Check whether the hostname is supposed to use a CNAME instead of a direct address.
  3. Confirm that the destination service recognizes the hostname. Many hosting and edge platforms require the domain to be added to a project before they serve the expected content.
  4. Test the response separately from DNS with curl -I https://app.example.com. A correct DNS answer does not guarantee that the web server, CDN route, origin, or application is healthy.
  5. Review the HTTP status, response headers, and edge-provider diagnostic information to determine whether traffic reached the intended service.

3. A CNAME is not working

Query the CNAME directly and then query its target. A CNAME target must ultimately resolve, and the alias cannot normally coexist with other data at the same hostname. Remove conflicting address, MX, or TXT records where the provider's model requires a pure CNAME. Also check whether you are configuring the root domain: traditional DNS does not allow a standard CNAME at the zone apex, although some providers offer an apex-alias feature under names such as ALIAS or flattening.

Confirm that the provider's record-name field expects only app or the full hostname. Interfaces differ, and entering the full name into a field that automatically appends the zone can create an unintended name.

4. Domain verification fails

Copy the verification hostname and value exactly from the platform. For TXT verification, inspect the authoritative answer and look for duplicate or malformed values:

dig @ns1.example-dns.com _verify.example.com TXT

Some tools display a long TXT value as multiple quoted strings; that does not necessarily mean the record is wrong. Focus on the reconstructed value and exact characters. Check for Unicode punctuation, accidental spaces, missing underscores, or a record added to the wrong zone. If verification uses a CNAME, query the alias and follow its target. Do not delete existing TXT records without understanding their purpose; SPF and other service verifications may share the same name.

5. Email is failing after a DNS change

  1. Check MX records and their priorities.
  2. Resolve every hostname listed by the MX records to an A or AAAA address.
  3. Inspect the domain's SPF TXT record for syntax, duplicate policies, and unintended removal of an authorized sender.
  4. Check DKIM records at the selector hostname supplied by the email platform.
  5. Check the DMARC record at _dmarc.example.com if the domain uses DMARC.

DNS can publish the correct email records while delivery still fails because of mail-server configuration, authentication alignment, reputation, or recipient-side policy. Treat DNS as one layer of the diagnosis.

6. TLS certificate or CDN routing is wrong

First verify that DNS points to the intended edge or hosting service. Then confirm that the hostname has been added to that service and that a certificate covers the exact name. A certificate for example.com does not automatically cover every subdomain, and wildcard coverage has defined limits.

Use SNI-aware testing when comparing certificates:

openssl s_client -connect app.example.com:443 -servername app.example.com

Review the certificate subject, subject alternative names, issuer, validity period, and presented chain. If certificate issuance is blocked, inspect CAA records and confirm that the permitted certificate authority and any required issuance rules match the platform's instructions. A successful DNS lookup cannot resolve an incorrect certificate, an origin certificate problem, or a CDN configuration mismatch.

What to double-check

Propagation, TTL, and cache behavior

“DNS propagation” is a convenient phrase for the time it takes different caches to expire and obtain a newer answer. It is not a single global switch. A resolver may retain an old response until its cached TTL expires, while another resolver already returns the new value. Negative answers can also be cached, so a hostname that previously did not exist may continue to appear absent for a period.

Check the TTL returned by the authoritative server and avoid repeatedly changing records during an incident. Lowering a TTL affects future caching; it does not immediately remove answers already cached elsewhere. Test from the affected network, a known recursive resolver, and the authoritative server.

Delegation and split-horizon DNS

Use dig +trace example.com to inspect the delegation path from the root through the top-level domain to the authoritative nameservers. If the registrar delegates to different nameservers than the provider you edited, your change may be published in the wrong place.

Organizations using split-horizon DNS may intentionally return different answers inside and outside the corporate network. Compare queries from both contexts and check VPN, resolver, search-domain, and local hosts-file settings before concluding that public DNS is incorrect.

DNSSEC

If DNSSEC is enabled, a stale or incorrect delegation-signing record can cause validating resolvers to return a security failure rather than an ordinary answer. Check the DNS provider's DNSSEC status, the registrar's delegation data, and whether a recent migration left old signing information behind. Make DNSSEC changes carefully and follow the provider's current procedure; do not disable it as a first response without understanding the failure.

Common mistakes

  • Checking only one resolver: A single result cannot distinguish cache behavior from authoritative configuration.
  • Editing the wrong DNS provider: Registrar records, hosting records, and authoritative zone records may be managed in separate systems.
  • Forgetting IPv6: An obsolete AAAA record can create intermittent or location-dependent failures.
  • Replacing shared TXT data: Adding a new verification value should not remove SPF, DKIM, or other required TXT values.
  • Expecting DNS to fix an application issue: Once the correct endpoint answers, investigate routing, origin health, firewall rules, and application configuration.
  • Using a CNAME at the apex without checking provider behavior: Root-domain aliasing is provider-specific and should be documented.
  • Changing records without a rollback note: Record the old value, new value, timestamp, TTL, and reason so the change can be reversed safely.

For infrastructure teams, keep DNS changes in the same review and change-management process used for deployment configuration. Documentation should identify ownership, expected destinations, verification commands, and expiration or renewal steps. Related operational practices are covered in the DNS and Hosting for Developers guide and the CI/CD pipeline troubleshooting checklist.

When to revisit

Return to this checklist before a domain migration, subdomain launch, CDN or hosting cutover, email-provider change, certificate renewal, or DNS provider consolidation. Revisit it after an incident whenever a record was changed under pressure, and before seasonal planning cycles if your team reviews domains, certificates, or edge routing on a schedule.

When workflows or tools change, update the commands and ownership details in your runbook. Record the authoritative nameservers, approved DNS providers, certificate authorities, expected records, and escalation contacts. During the next issue, follow this short sequence:

  1. Write down the intended hostname, record, value, and service.
  2. Confirm delegation with NS lookups.
  3. Query the authoritative server directly.
  4. Compare at least two recursive results and the affected network's result.
  5. Check A, AAAA, CNAME, TXT, MX, and CAA records as relevant.
  6. Test the service with HTTP, mail, or TLS-specific tools rather than stopping at DNS.
  7. Document the change, evidence, rollback, and final verification.

This process turns “the DNS change has not propagated” into a testable diagnosis and gives the next engineer a clear record of what was checked.

Related Topics

#DNS#domain management#hosting#TLS#CDN#email authentication
N

Networked DevOps Editorial Team

Senior SEO Editor

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.