Hosting & Deployment

Troubleshoot DNS Records for Website Deployments

Diagnose A, AAAA, CNAME, MX, TXT and propagation issues without confusing DNS caching with server availability.

DNS connects human-readable hostnames to network services. A website migration can fail even when the new server is healthy if records are inconsistent, cached or incomplete. Troubleshooting begins by identifying which hostname and record type the client is resolving.

Understand common record types

A and AAAA records map a hostname to IPv4 and IPv6 addresses. CNAME records alias one hostname to another, subject to DNS rules for the zone apex. MX records identify mail exchangers, while TXT records are commonly used for domain verification and email authentication.

Check authoritative answers

Query the authoritative nameservers to confirm the published zone data, then compare answers from multiple recursive resolvers. A cached old answer may remain available until its TTL expires. Lowering TTL shortly before a migration helps only if the lower TTL was published and cached in advance.

Check IPv6 separately

A stale AAAA record can send some visitors to an old or misconfigured server even when the A record is correct. Test both address families and verify that the web server is listening and firewalls permit the expected traffic.

Change records with a rollback plan

Record the previous values and intended TTLs before editing DNS. Avoid changing nameservers, web records and mail records simultaneously unless the migration plan requires it. Verify MX and TXT records after a web hosting move so email delivery is not accidentally interrupted.

Checklist

  • Confirm authoritative A and AAAA answers.
  • Check CNAME and zone-apex constraints.
  • Verify MX and TXT records after changes.
  • Account for TTL and resolver caching.
  • Test IPv4 and IPv6 connectivity independently.
Share this page Help other developers discover this resource.