A Record vs CNAME: Interactive Comparison
Understand the difference between A records and CNAME records with an interactive guide. Includes scenario-based recommendations, DNS resolution visualization, common mistakes, and a quick reference for all DNS record types.
Side-by-Side Comparison
| Feature | A Record | CNAME |
|---|---|---|
| Points to | IP address (e.g., 93.184.216.34) | Another domain name (e.g., example.cdn.net) |
| Root domain (example.com) | Yes — the only option | No — prohibited by RFC 1034 |
| Subdomains | Yes | Yes — most common use |
| When target IP changes | Must manually update the record | Automatically follows the target |
| DNS lookup speed | Direct — one query to resolve | Extra hop — queries the alias, then resolves that |
| Can coexist with other records | Yes — can have A + MX + TXT on same name | No — CNAME must be the only record for that name |
| IPv6 equivalent | AAAA record (for IPv6 addresses) | Same CNAME record (works for any IP version) |
| External services (CDN, SaaS) | Poor choice — IPs change, you lose routing optimization | Best choice — follows the service's dynamic routing |
| Email authentication | Not used for email auth | Common for DKIM records |
| TTL (caching) | Controlled by your DNS settings | May inherit TTL from target domain |
Which Should I Use? (Interactive Guide)
Select your scenario to get a specific recommendation.
How DNS Resolution Works: A Record vs CNAME
A Record Resolution
Step 1
Browser asks: "What IP is example.com?"
Step 2
DNS returns: A record → 93.184.216.34
Step 3
Browser connects to 93.184.216.34
Total: 1 DNS query — direct and fast.
CNAME Resolution
Step 1
Browser asks: "What IP is blog.example.com?"
Step 2
DNS returns: CNAME → example.wordpress.com
Step 3
Browser asks: "What IP is example.wordpress.com?"
Step 4
DNS returns: A record → 192.0.78.25
Step 5
Browser connects to 192.0.78.25
Total: 2 DNS queries — slightly slower, but the target IP is managed by the service.
All DNS Record Types (Quick Reference)
DNS has 7+ common record types beyond just A and CNAME. Click "Show All" to see a reference of each type and when to use it.
Common Mistakes
Using CNAME on the root domain
CNAME on example.com violates DNS standards and breaks email. Use an A record, or an ALIAS/ANAME record if your DNS provider supports it.
Using A record for a cloud load balancer
Cloud load balancers (AWS ELB, Azure LB) don't have static IPs. Their IP can change at any time. Use CNAME to point to the load balancer's DNS name.
Adding other records alongside a CNAME
CNAME must be the only record for that hostname. If you need MX + CNAME on the same subdomain, you can't — use A records instead.
Using A record for a CDN subdomain
CDNs route users to the nearest edge server via DNS. An A record bypasses this, sending everyone to one IP. Use CNAME so the CDN's DNS can optimize routing.
Forgetting to update A records when server IP changes
This is the main advantage of CNAME — it follows changes automatically. If you use A records, create calendar reminders to check them when migrating servers.
Creating CNAME chains longer than 2-3 hops
Each hop adds latency and a chance for failure. Keep CNAME chains short. If you see 4+ hops, simplify your DNS architecture.
For Email Marketers: DNS Records That Matter
If you're setting up email marketing, here are the DNS records you'll typically need:
MX Records (A-record-like)
Tell other mail servers where to deliver email for your domain. Points to your email provider (Gmail, Outlook, etc.).
SPF Record (TXT)
Lists which servers are authorized to send email from your domain. Prevents spoofing.
DKIM Records (CNAME)
CNAME records pointing to your email service's DKIM key servers. Proves emails are actually from you and haven't been tampered with.
DMARC Record (TXT)
Tells receiving servers what to do with emails that fail SPF/DKIM checks. Essential for email deliverability.
Return-Path CNAME
Some email services ask for a CNAME on a subdomain like bounce.example.com to handle bounces and maintain sender reputation.
Like this tool? Try Sequenzy for free
AI-powered email marketing with Stripe integration, automations, and built-in analytics.
About this tool
A records and CNAME records are the two most common DNS record types, and choosing the wrong one can break your website, slow down your loading time, or cause email delivery failures. The short version: A records point directly to IP addresses, CNAMEs point to other domain names. But the decision of which to use depends on your specific situation.
This interactive guide helps you pick the right record type for your scenario — whether you're setting up a root domain, connecting a subdomain to an external service, configuring a CDN, or setting up email authentication. Select your use case and get a specific recommendation with example DNS records you can copy.
For email-specific DNS setup, check our SPF checker, DKIM checker, and DMARC checker to verify your email authentication records. Use our CNAME lookup tool to check existing CNAME records, and our MX lookup to verify mail server configuration.
Understanding DNS is especially important for email marketing. When you set up a platform like Sequenzy, you'll add CNAME records for DKIM authentication and TXT records for SPF. Getting these wrong means your emails land in spam. Our deliverability score tool checks all of this for you in one scan.
Frequently Asked Questions
More Free Tools
View all toolsEmail Signature Generator
Create professional HTML email signatures for Gmail, Outlook, and Apple Mail. Choose from multiple styles and customize with your contact info and social links.
Free Attrition Rate Calculator
Calculate attrition rates for employees, customers, email subscribers, or students. Includes retention analysis, half-life projections, replacement cost estimates, and industry benchmarks.
Email Text-to-Image Ratio Checker
Analyze your email HTML to check the text-to-image ratio. Spam filters flag image-heavy emails with too little text content. Optimize your ratio for better deliverability.
DKIM Record Checker
Verify your domain's DKIM configuration for email authentication. Check the public key, selector, and key strength to ensure your emails are properly signed.