CNAME Record — What It Is, Simple Explanation [2026]

Enterno.io Editorial Team

CNAME record: Definition, Syntax, and Examples

By Anatoly Oshmanovsky · Updated Apr 17, 2026

TL;DR:

CNAME (Canonical Name) is a DNS record type that turns one domain into an alias of another. For example, www.example.com (CNAME) → example.com (actual address). The browser follows the chain and retrieves the final A/AAAA records. CNAME cannot be used on the apex (root) domain — only on subdomains.

Try it now — free →

What is a CNAME record

Check CNAME record online

Use the Enterno.io tool — enter a domain, get results in 1-2 seconds. Free, no signup.

Check →

A / AAAAIPv4 and IPv6 host addresses

MX RecordsDomain mail servers

TXT / SPFVerification & anti-spoofing

NS / SOAName servers & zone authority

Why teams trust us

DNS record types

SPF+DKIM

email protection

<1s

DNS response

check regions

How it works

Enter domain

Select record type

Get DNS response

What are DNS Records?

DNS (Domain Name System) translates domain names into IP addresses. DNS records are instructions that define where to route traffic, email, and how to verify domainownership.

Complete Lookup

Query all record types — A, AAAA, MX, NS, TXT, CNAME, SOA — in a single request.

Instant Results

Direct queries to authoritative servers. Results in milliseconds, no caching.

Security Checks

SPF, DKIM, and DMARC analysis to evaluate email protection against spoofing and phishing.

Export & History

Save check results. Compare DNS records before and after registrar changes.

Who uses this

DevOps

DNS check after deploy

Email marketers

SPF/DKIM/DMARC audit

SEO

DNS config audit

Sysadmins

DNS zone control

Common Mistakes

❌

Missing SPF recordWithout SPF, emails may land in spam. Add a v=spf1 TXT record.

❌

Single NS serverIf the only NS fails, the domain becomes unreachable. Use at least 2 NS servers.

❌

CNAME conflicting with other recordsCNAME cannot coexist with MX or TXT on the same name — this violates RFC.

❌

TTL set too highWith 86400s TTL, DNS changes take a full day. Lower TTL to 300 before migrations.

❌

Missing PTR recordMail servers check PTR. Without it, emails may be rejected.

Best Practices

✓

Set up SPF + DKIM + DMARCThe trio of records that protects your email from spoofing and improves deliverability.

✓

Use 2+ NS serversDistribute NS servers across different networks for redundancy.

✓

Lower TTL before migrationSet TTL to 300 at least 24-48 hours before an IP change for fast propagation.

✓

Verify DNS after changesAfter updating records, confirm changes propagated correctly and no errors remain.

✓

Add a CAA recordCAA restricts which Certificate Authorities can issue SSL certificates for your domain.

Get more with a free account

DNS check history, API keys and DNS change monitoring.

Learn more

How-to

Glossary

Research

Alternatives

Frequently Asked Questions

How does CNAME record differ from similar concepts?

See the full breakdown in the article above. For a quick check, use our online tool.

Does this need manual updates?

Usually no — most modern services configure it automatically. Manual setup is only needed for migrations or exotic configurations.