What is the main difference between A records and CNAME records?

An A record maps a domain name directly to an IPv4 address (e.g., example.com → 93.184.216.34). A CNAME record maps a domain name to another domain name (e.g., blog.example.com → example.wordpress.com). The key difference: A records are direct pointers to servers, while CNAMEs are aliases that eventually resolve to an A record. CNAMEs follow changes automatically, A records need manual updates when IPs change.

Can I use a CNAME record on my root domain?

No. The DNS specification (RFC 1034) prohibits CNAME records at the zone apex (root domain like example.com). This is because CNAME cannot coexist with other record types, and root domains require SOA and NS records. Some DNS providers offer workarounds: Cloudflare has 'CNAME flattening', Route53 has 'ALIAS', and DNSimple has 'ALIAS records.' These resolve the CNAME internally and return A records to clients.

Which is faster, A record or CNAME?

A records are slightly faster because they resolve in one DNS query. CNAME records require at least two queries: first to resolve the CNAME to another domain name, then to resolve that domain to an IP. In practice, DNS caching makes this difference negligible — both are resolved in milliseconds. The management benefits of CNAME (automatic IP following) usually outweigh the tiny speed difference.

Why can't I have a CNAME and other records on the same subdomain?

The DNS specification states that if a CNAME exists for a name, it must be the only record for that name. This means you can't have a CNAME alongside MX records (for email), TXT records (for SPF/DMARC), or any other type. This is the main technical reason CNAME can't be used on root domains — root domains need MX records for email and NS records for DNS delegation.

When should I use A records for subdomains?

Use A records when: (1) you control the server and its IP is stable, (2) you need other record types on the same subdomain (like MX or TXT), (3) you want the fastest possible DNS resolution, or (4) you're pointing to a server with a dedicated/static IP. If none of these apply, CNAME is usually the better choice for subdomains.

What is an ALIAS or ANAME record?

ALIAS (or ANAME) is a non-standard record type offered by some DNS providers (Cloudflare, Route53, DNSimple) that behaves like a CNAME at the root domain level. The DNS provider resolves the CNAME chain internally and returns A records to clients, so it looks like a regular A record but follows a CNAME target. This solves the 'no CNAME at root domain' problem but isn't universally supported across all DNS providers.

Do A records or CNAMEs affect email deliverability?

Indirectly, yes. Email authentication records (SPF, DKIM, DMARC) use TXT and CNAME record types. DKIM is typically set up via CNAME records pointing to your email provider's key servers. SPF and DMARC use TXT records. If these are misconfigured, your emails may fail authentication checks and land in spam. The A record itself doesn't affect email, but the overall DNS configuration matters greatly for deliverability.

How do I check what type of record my domain uses?

Use our CNAME lookup tool to check if a domain has a CNAME record and see the resolution chain. For MX records (email), use our MX lookup tool. For SPF, use our SPF checker. You can also use command-line tools like 'dig example.com A' or 'nslookup -type=CNAME blog.example.com' to query specific record types directly from your terminal.

Back to Tools

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.

Start Free Trial

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 tools

Free CNAME Record Lookup

Look up CNAME records for any domain. Follows the full resolution chain, detects the hosting service (AWS, Cloudflare, Vercel, Shopify, etc.), and shows associated A/AAAA records.

Shopify Profit Margin Calculator

Calculate real Shopify profit per order after COGS, shipping, fulfillment, payment fees, returns, apps, and ad cost.

Product Pricing Calculator

Find the selling price needed to hit a target net margin after ecommerce costs, returns, fees, and ad spend.

Discount Impact Calculator

See whether a sale or discount still leaves enough profit after fees, returns, shipping, fulfillment, and ad cost.

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