Understanding DNS Record Types: A Complete Guide to DNS Records

Reveal Domains•November 10, 2025•10 min read

Understanding DNS Record Types: A Complete Guide to DNS Records

When managing a domain name, understanding DNS (Domain Name System) records is essential. These records tell the internet where to find your website, how to deliver your email, and much more. Whether you're a web developer, business owner, or just getting started with your first domain, this guide will explain each DNS record type in simple terms.

What Are DNS Records?

DNS records are instructions stored in DNS servers that provide information about a domain. Think of them as a phonebook for the internet - when someone types your domain name into their browser, DNS records tell their computer where to find your website's server.

Each DNS record typically includes:

Type: The kind of record (A, CNAME, MX, etc.)
Name/Host: The domain or subdomain the record applies to
Value/Data: Where the record points to
TTL (Time to Live): How long the record should be cached

Essential DNS Record Types Explained

A Record (Address Record)

The A record is the most fundamental DNS record type. It maps a domain name to an IPv4 address.

Purpose: Points your domain to the specific IP address where your website is hosted.

Example:

Type: A
Name: @
Value: 192.168.1.1
TTL: 3600

This tells browsers that when someone visits your domain, they should connect to the server at IP address 192.168.1.1.

When to Use:

Connecting your root domain (example.com) to your hosting server
Setting up subdomains (blog.example.com)
Creating multiple A records for load balancing

Common Mistakes:

Using multiple A records without proper load balancing configuration
Forgetting to update A records when changing hosting providers

AAAA Record (IPv6 Address Record)

The AAAA record is the IPv6 version of an A record. It maps a domain name to an IPv6 address.

Purpose: Points your domain to an IPv6 address, supporting the newer internet protocol.

Example:

Type: AAAA
Name: @
Value: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
TTL: 3600

When to Use:

Supporting IPv6 connections alongside IPv4
Future-proofing your domain configuration
Optimizing performance for IPv6 networks

Why It Matters: As the internet transitions from IPv4 to IPv6, having AAAA records ensures your site remains accessible to all users.

CNAME Record (Canonical Name Record)

A CNAME record creates an alias from one domain name to another. Instead of pointing to an IP address, it points to another domain.

Purpose: Redirect one domain or subdomain to another domain name.

Example:

Type: CNAME
Name: blog
Value: yourdomain.com
TTL: 3600

This makes blog.yourdomain.com point to wherever yourdomain.com points.

When to Use:

Setting up subdomains that should follow your main domain
Connecting to third-party services (CDNs, email marketing platforms)
Creating aliases for easier domain management

Important Rules:

Cannot be used for root domains (use A records instead)
Cannot coexist with other record types for the same name
Should point to a domain name, not an IP address

Common Use Cases:

www.yourdomain.com → yourdomain.com
shop.yourdomain.com → yourstore.shopify.com
mail.yourdomain.com → ghs.google.com

MX Record (Mail Exchange Record)

MX records specify which mail servers handle email for your domain.

Purpose: Direct email sent to your domain to the correct mail servers.

Example:

Type: MX
Name: @
Value: mail.example.com
Priority: 10
TTL: 3600

When to Use:

Setting up email hosting for your domain
Configuring email services like Google Workspace or Microsoft 365
Establishing backup mail servers

Understanding Priority: The priority number determines which server receives email first. Lower numbers have higher priority. If the primary server is unavailable, email is routed to the next priority level.

Typical Configuration:

Priority 10: mail1.provider.com
Priority 20: mail2.provider.com
Priority 30: backup-mail.provider.com

TXT Record (Text Record)

TXT records store text information that can be used for various verification and security purposes.

Purpose: Provide text-based data for domain verification, email authentication, and other services.

Example:

Type: TXT
Name: @
Value: "v=spf1 include:_spf.google.com ~all"
TTL: 3600

Common Uses:

1. SPF (Sender Policy Framework) Prevents email spoofing by specifying which servers can send email from your domain.

v=spf1 include:_spf.google.com ~all

2. DKIM (DomainKeys Identified Mail) Adds a digital signature to your emails to verify authenticity.

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3...

3. DMARC (Domain-based Message Authentication) Tells receiving servers what to do with emails that fail SPF or DKIM checks.

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

4. Domain Verification Proves ownership of your domain to services like Google, Microsoft, or Facebook.

google-site-verification=abc123def456

5. Site Information Store any text-based information about your domain.

NS Record (Name Server Record)

NS records identify which DNS servers are authoritative for your domain.

Purpose: Delegate your domain to specific DNS servers that contain your DNS records.

Example:

Type: NS
Name: @
Value: ns1.hosting-provider.com
TTL: 86400

When to Use:

Setting up your domain with a hosting provider
Delegating subdomains to different DNS servers
Changing DNS management between providers

Important Notes:

Usually configured at your domain registrar, not within the DNS zone itself
Typically requires at least two NS records for redundancy
Changes can take 24-48 hours to propagate globally

SOA Record (Start of Authority Record)

The SOA record contains administrative information about your DNS zone, including the primary name server and zone settings.

Purpose: Store essential zone information like refresh rates and version numbers.

When to Use: SOA records are automatically created when you set up DNS hosting. Most users never need to manually edit these records - your DNS provider manages them.

PTR Record (Pointer Record)

PTR records provide reverse DNS lookup, mapping an IP address back to a domain name (the reverse of an A record).

Purpose: Primarily used for email server verification to improve deliverability and reduce spam scores.

When to Use: Mainly for email servers. PTR records are typically managed by your hosting provider or ISP, not in your regular DNS control panel.

SRV Record (Service Record)

SRV records specify the location (hostname and port) of servers for specific services like VoIP, instant messaging, or LDAP.

Purpose: Define where specialized services are hosted and which port they use.

When to Use: VoIP services (SIP), instant messaging servers, Microsoft Active Directory, or other specialized applications. Most standard websites don't need SRV records.

CAA Record (Certification Authority Authorization)

CAA records specify which certificate authorities (CAs) are allowed to issue SSL certificates for your domain.

Purpose: Enhance security by preventing unauthorized SSL certificate issuance.

When to Use: Add CAA records to control which certificate authorities can issue SSL certificates for your domain (e.g., Let's Encrypt, DigiCert). This is optional but improves security.

ALIAS/ANAME Record (Proprietary)

Some DNS providers offer ALIAS or ANAME records as a workaround to point root domains to hostnames (like CNAME, but for root domains).

Purpose: Allow your root domain to point to another hostname instead of an IP address.

When to Use: When pointing your root domain to cloud services (AWS, Cloudflare) or CDNs that provide hostnames instead of IP addresses. Not all DNS providers support this - it's a proprietary feature.

Common DNS Configuration Examples

Basic Website Setup

Most websites need just these essential records:

Type: A, Name: @, Value: [Your server IP]
Type: A, Name: www, Value: [Your server IP]

Email Configuration

For email to work with your domain:

Type: MX, Priority: 10, Value: mail.yourdomain.com
Type: TXT, Value: v=spf1 include:_spf.google.com ~all

Subdomain Setup

To create a blog subdomain:

Type: A, Name: blog, Value: [Blog server IP]

Or using CNAME:

Type: CNAME, Name: blog, Value: hosting-platform.com

How to Check Your DNS Records

Want to see your domain's DNS records? Use these methods:

Reveal Domains DNS Checker - Check all DNS records for any domain
Command Line: nslookup yourdomain.com or dig yourdomain.com
Your DNS Control Panel - Direct access through your registrar or hosting provider

Where to Manage DNS Records

DNS records are typically configured through:

Domain Registrar - Where you purchased your domain
Hosting Provider - If using their DNS servers
DNS Service - Services like Cloudflare or AWS Route 53

DNS Propagation Time

When you update DNS records, changes aren't instant. DNS propagation typically takes:

Most cases: 1-4 hours
Maximum: Up to 48 hours
Speed tip: Lower your TTL value before making changes

Conclusion

Understanding DNS record types doesn't have to be complicated. Here's what you need to remember:

A records connect your domain to an IP address
CNAME records create domain aliases
MX records handle email routing
TXT records verify ownership and secure email
NS records control which DNS servers manage your domain

Most websites use just a handful of these record types. Start with the basics (A, MX, TXT) and add others as you need specific functionality.

Ready to manage your domain's DNS?

Use our DNS Record Checker to view any domain's records
Check domain availability with Reveal Domains search
Look up domain details with WHOIS lookup

Frequently Asked Questions

What's the difference between A record and CNAME record?

An A record points directly to an IP address (like 192.168.1.1), while a CNAME record points to another domain name. Use A records for your root domain and when you know the specific IP address. Use CNAME records for subdomains or when connecting to third-party services that might change their IP addresses.

How long do DNS changes take to go live?

DNS changes typically take 1-4 hours to propagate globally, though it can take up to 48 hours in some cases. The speed depends on your TTL (Time to Live) setting. You can speed this up by lowering your TTL to 300 seconds before making changes.

Can I have multiple MX records for email?

Yes! It's actually recommended to have multiple MX records for redundancy. Each has a priority number - email goes to the lowest priority first (10 before 20). If that server is down, the next priority server receives the email instead.

Do I need all these DNS record types?

No. Most websites only need a few basic types: A records for your website, MX records for email, and TXT records for email security (SPF/DKIM). Other record types like SRV, PTR, or CAA are only needed for specific services or advanced security requirements.

Why can't I use CNAME for my root domain?

DNS protocol rules prohibit CNAME records at the root domain level because they would conflict with required records like NS and SOA. Use A records for root domains instead, or check if your DNS provider offers ALIAS/ANAME records (a proprietary workaround).

How do I check if my DNS records are correct?

Use our DNS Checker to view all records for your domain, or use command-line tools like nslookup or dig. The easiest way to verify is to test functionality - if your website loads and email works, your critical DNS records are configured correctly.