DNS Records Explained: A Complete Guide to A, AAAA, CNAME, MX, TXT, and More

The Domain Name System (DNS) is the invisible backbone of the internet. Every time you type a URL into your browser, send an email, or connect to an API, DNS translates human-readable names into machine-readable IP addresses. Understanding DNS records is fundamental for anyone who manages websites, servers, or online services.

Think of DNS as the internet's phone book. When you call someone, you do not dial a random sequence of numbers — you look up their name and get the number. DNS does exactly this: you ask for example.com, and DNS returns 203.0.113.50.

This guide explains every common DNS record type with practical examples, real dig output, and guidance on when to use each one.

The DNS Resolution Process

Before diving into record types, let us understand how a DNS query travels from your browser to the answer:

This entire process typically completes in under 50 milliseconds, and the result is cached at multiple levels to speed up subsequent queries.

A Record — The Foundation

The A record (Address record) is the most fundamental DNS record. It maps a domain name to an IPv4 address. When someone visits your website, the A record tells their browser which server to connect to.

Key facts about A records:

• You can have multiple A records for the same domain (round-robin DNS)
• The @ symbol represents the root domain (e.g., example.com)
• Subdomains need their own A records (e.g., blog.example.com)
• TTL (Time to Live) determines how long the record is cached

AAAA Record — IPv6 Address

The AAAA record (pronounced "quad-A") is the IPv6 equivalent of the A record. As IPv4 addresses become scarce, IPv6 adoption continues to grow — Google reports over 45% of traffic now uses IPv6.

CNAME Record — The Alias

A CNAME record (Canonical Name) creates an alias from one domain name to another. Instead of pointing to an IP address, it points to another domain name. The DNS resolver follows the chain until it reaches an A record.

Common CNAME use cases:

MX Record — Email Routing

The MX record (Mail Exchanger) tells the world which server handles email for your domain. When someone sends an email to [email protected], their mail server looks up the MX record for example.com to find where to deliver it.

The number before each server is the priority (lower = higher priority). In the example above, mail servers try mail.example.com first (priority 10). If it is unavailable, they fall back to mail2.example.com (priority 20).

TXT Record — The Swiss Army Knife

The TXT record stores arbitrary text data associated with a domain. It has become the most versatile record type, used for email authentication, domain verification, and security policies.

SPF (Sender Policy Framework)

SPF tells receiving mail servers which IP addresses are authorized to send email on behalf of your domain. This prevents spammers from spoofing your domain:

DKIM (DomainKeys Identified Mail)

DKIM adds a digital signature to outgoing emails, allowing receiving servers to verify the email was not tampered with in transit:

DMARC (Domain-based Message Authentication)

DMARC builds on SPF and DKIM to tell receiving servers what to do when authentication fails:

Domain Verification TXT Records

Many services use TXT records to verify domain ownership:

NS Record — Nameserver Delegation

The NS record (Nameserver) specifies which DNS servers are authoritative for a domain. When you register a domain and set nameservers at your registrar, you are defining NS records:

SRV Record — Service Discovery

The SRV record (Service) specifies the host and port for specific services. It is commonly used for VoIP, XMPP (chat), LDAP, and Microsoft Active Directory:

CAA Record — Certificate Authority Authorization

The CAA record specifies which Certificate Authorities (CAs) are allowed to issue SSL certificates for your domain. This prevents unauthorized CAs from issuing certificates, adding an extra layer of security:

PTR Record — Reverse DNS

The PTR record (Pointer) is the reverse of an A record — it maps an IP address back to a domain name. PTR records are primarily used for email deliverability and security verification:

TTL — Time to Live

Every DNS record has a TTL value measured in seconds. This tells DNS resolvers how long to cache the record before checking for updates:

Complete DNS Record Reference

Checking DNS Propagation

After changing DNS records, propagation can take anywhere from a few minutes to 48 hours depending on TTL values and resolver caching. Here is how to check propagation status:

DNS Management with Panelica

Panelica includes a built-in BIND DNS server that manages all record types directly from the web panel. Combined with Cloudflare integration, you get a comprehensive DNS management solution:

• Full record management — Create, edit, and delete A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, and PTR records
• Automatic zone generation — When you add a domain, Panelica creates the DNS zone with sensible defaults
• Cloudflare integration — Manage Cloudflare DNS from Panelica with drift detection (detects when records change outside the panel)
• Email DNS automation — SPF, DKIM, and DMARC records are generated automatically when you enable email for a domain
• Subdomain management — Create subdomains with their own DNS records and web server configurations
• Zone import/export — Import existing BIND zone files or export for backup