How to Read DNS Records
DNS (Domain Name System) is the phonebook of the internet. It translates human-readable domain names like example.com into IP addresses that computers use to communicate. Understanding DNS records is crucial for managing websites, troubleshooting email delivery, and securing your domain.
The Six Essential DNS Record Types
A Record (Address)
The A record is the most fundamental DNS record. It maps a domain name to an IPv4 address (like 93.184.216.34). When someone types your domain into a browser, the A record tells their computer which server to connect to.
example.com. 300 IN A 93.184.216.34
Most domains have at least one A record. Larger sites may have multiple A records for load balancing — the DNS resolver will rotate between them.
AAAA Record (IPv6 Address)
The AAAA record (pronounced "quad-A") is the IPv6 equivalent of an A record. As the internet transitions to IPv6, these records are becoming increasingly important.
example.com. 300 IN AAAA 2606:2800:220:1:248:1893:25c8:1946
If a domain has both A and AAAA records, modern browsers and operating systems will typically prefer IPv6 when available. Having AAAA records shows your infrastructure supports the newer protocol.
MX Record (Mail Exchange)
MX records specify which mail servers are responsible for receiving email for a domain. Each MX record has a priority value — lower numbers mean higher priority.
example.com. 300 IN MX 10 mail1.example.com. example.com. 300 IN MX 20 mail2.example.com.
In this example, mail is first delivered to mail1.example.com (priority 10). If that server is unavailable, the sending server tries mail2.example.com (priority 20). Common MX setups point to services like Google Workspace (aspmx.l.google.com) or Microsoft 365 (*.mail.protection.outlook.com).
CNAME Record (Canonical Name)
A CNAME record creates an alias from one domain name to another. Instead of pointing to an IP address, it points to another domain name, which then resolves to an IP.
www.example.com. 300 IN CNAME example.com.
CNAMEs are commonly used for www subdomains, CDN setups (pointing to cdn.cloudflare.net), and SaaS platforms. Important: You cannot place a CNAME on the root domain (apex) alongside other records — it's technically only valid for subdomains.
TXT Record (Text)
TXT records store arbitrary text data associated with a domain. While originally intended for human-readable notes, they're now primarily used for verification and security purposes:
- SPF records — specify which servers can send email for your domain (learn more)
- Domain verification — prove ownership to services like Google, Microsoft, and others
- DKIM keys — cryptographic keys for email authentication
- DMARC policies — email authentication and reporting policies
example.com. 300 IN TXT "v=spf1 include:_spf.google.com ~all"
NS Record (Name Server)
NS records specify which DNS servers are authoritative for a domain. These are the servers that hold the "truth" about all other DNS records for that domain.
example.com. 86400 IN NS ns1.example.com. example.com. 86400 IN NS ns2.example.com.
Every domain must have at least two NS records for redundancy. When you change your DNS provider (e.g., moving to Cloudflare), you update your NS records at your registrar. NS changes can take up to 48 hours to propagate globally.
Reading DNS Records: TTL and Classes
Each DNS record includes a TTL (Time to Live) value measured in seconds. This tells DNS resolvers how long to cache the record before checking for updates. A TTL of 300 means the record is cached for 5 minutes; 86400 means 24 hours.
Lower TTLs mean faster propagation of changes but more DNS queries. Higher TTLs reduce DNS traffic but make changes slower to take effect. Before making DNS changes, it's common practice to lower the TTL first, make the change, then raise it again.
Checking DNS Records
You can check any domain's DNS records instantly with our free lookup tool. Just enter a domain and we'll show you all configured records, along with WHOIS data, SSL certificate details, and email security status.
You can also use command-line tools like dig or nslookup, or check your own IP address to understand how DNS resolution works from your location.