Complete Guide to DNS Records: A, AAAA, MX, TXT, CNAME & NS Diagnostics

The Domain Name System (DNS) is often called the phonebook of the internet. It translates human-readable domain names like n4r.org into machine-readable IP addresses like 104.21.48.1.

When migrating domain names, setting up corporate email hosting, or resolving website downtime, proper DNS record configuration and diagnostics are critical skills for web engineers and sysadmins.

This guide provides a comprehensive breakdown of essential DNS record types, propagation mechanics, and diagnostic workflows using the N4R Online DNS Lookup Tool.

Core DNS Record Types Explained

1. A & AAAA Records (Address Records)

• A Record: Maps a domain name to an IPv4 address (e.g., n4r.org -> 104.21.48.1).
• AAAA Record: Maps a domain name to an IPv6 address (e.g., 2606:4700:3031::6815:3001).

2. CNAME Records (Canonical Name)

• Aliases one domain name to another canonical domain (e.g., www.n4r.org -> n4r.org). CNAME records require a secondary DNS query to resolve the target domain's final IP address.

3. MX Records (Mail Exchange)

• Directs incoming email for a domain to specified mail servers with priority weights:

  Priority 10: mail.example.com
  Priority 20: fallbackmail.example.com
  

4. TXT Records (Text & Email Security)

• Stores text-based data frequently used for email security protocols:
  • SPF (Sender Policy Framework): Authorizes specific IP ranges to send emails on behalf of your domain.
  • DKIM (DomainKeys Identified Mail): Holds cryptographic public keys to verify email authenticity.
  • DMARC (Domain-based Message Authentication): Specifies policies for handling emails that fail SPF/DKIM checks.

5. NS Records (Name Server Delegation)

• Identifies the authoritative DNS servers responsible for answering queries for a specific domain zone.

Troubleshooting DNS Propagation Delays

When you update DNS records at your registrar or cloud provider, changes do not occur globally instantaneous due to Time-To-Live (TTL) caching:

1. TTL Expiration: Local ISP resolvers cache DNS answers for the duration specified in the record's TTL field (e.g., 3600 seconds = 1 hour).
2. Flush Local Cache: Flush operating system DNS cache using CLI commands:
   • Windows: ipconfig /flushdns
   • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
3. Use Online Verification Tools: Verify global authoritative records instantly using the N4R DNS Diagnostic Checker.

By regularly auditing your domain DNS records, you prevent email delivery failures, minimize migration downtime, and maintain high availability across your web infrastructure.