DNS4 min
ALIAS Records vs. CNAME Records: Which Do You Need?
NS
NameSilo Staff8/12/2026
Share
A CNAME record points a subdomain to another hostname, but core DNS rules forbid using a CNAME on a root domain because it conflicts with MX (email) and NS records. An ALIAS record (also called ANAME, or CNAME flattening) solves this by acting like a CNAME while dynamically resolving to an IP address behind the scenes, letting you route your root domain without breaking email.
The Rule: RFC 1035 and RFC 1912
The restriction traces back to RFC 1035 §3.6.2: if a CNAME record exists at a name, no other record type may exist at that same name. Your root domain (the "zone apex") must hold SOA and NS records at minimum, and typically MX records too, so a CNAME there is structurally forbidden.
RFC 1912 §2.4, a widely cited operational guidance document, spells out the consequence: placing a CNAME at the apex breaks delegation and mail routing. Resolvers handle the violation inconsistently; some ignore it, some return SERVFAIL.
Subdomains are exempt. A name like www.yourdomain.com typically holds nothing else, so a CNAME there is perfectly valid.
Why It Matters: Deploying Without Breaking Email
Modern platforms like Heroku, Vercel, and Netlify hand you a hostname to point your domain at, expecting a CNAME. That works cleanly for www.yourdomain.com. It fails the moment you try the bare root domain, because your MX records live there too.
Get this wrong, and every @yourdomain.com email account stops receiving mail the instant the record saves, with no warning from most DNS panels.
Deep Dive: The CNAME
A CNAME is a strict alias: "this name is nothing but a pointer, go resolve the target instead." It's fast, simple, and exactly what subdomains like www or blog are built for.
What it cannot do: coexist with any other record type at the same name. This single restriction is why the root domain problem exists in the first place.
Deep Dive: The ALIAS (or ANAME)
Different vendors use different names for the same workaround: ALIAS, ANAME, or CNAME flattening (Cloudflare's term). All describe a proprietary, non-standard record that behaves like a CNAME in the DNS panel, but the provider's servers resolve it to an A/AAAA record before answering queries. Because the final answer is an IP address, it can legally coexist with MX and NS records.
Important nuance: ALIAS/ANAME was never formally standardized. An IETF draft for a true ANAME record was proposed and later abandoned. What exists today are vendor-specific implementations, not a universal DNS record type. A newer standard, RFC 9460 (SVCB/HTTPS records), offers a standards-compliant path to apex aliasing, but client and browser support remains incomplete as of 2026, so vendor-specific flattening remains the practical solution.
Common Mistakes
Forcing a CNAME onto the root domain anyway: Some DNS panels technically allow saving it. The moment you do, MX and NS records at that name become invalid, and inbound email to @yourdomain.com starts hard-bouncing immediately.
Assuming every registrar supports ALIAS/ANAME: It's a proprietary feature, not a DNS standard, so support varies by provider. Confirm before architecting a deployment around it.
Mixing root and www configuration inconsistently: Point www via CNAME but leave the root unconfigured, and visitors typing the bare domain land somewhere broken.
What This Means for You
NameSilo's DNS Manager does not currently offer ALIAS/ANAME flattening. The reliable workaround is a CNAME on www combined with root domain forwarding, supported natively. If your deployment specifically requires true ALIAS-style flattening at the root, keep your domain registered at NameSilo while delegating DNS management to a provider like Cloudflare that offers it, a common and fully supported pairing. Need a domain to start with? Search available names.
Frequently Asked Questions
What is an ALIAS record in DNS?
A vendor-specific record resolving like a CNAME but usable at the root.
Can I put a CNAME on a root domain?
No. It conflicts with required NS and MX records per RFC 1035.
Why does a CNAME break email MX records?
A CNAME cannot coexist with any other record type at the same name.
What is the difference between an A record and an ALIAS record?
A records point to a static IP; ALIAS dynamically resolves to one.
Does NameSilo support ALIAS records?
Not currently. Use CNAME on www plus root forwarding, or delegate DNS elsewhere.
How do I point my root domain to Heroku?
Use root forwarding, or delegate DNS to a provider supporting ALIAS/ANAME.
What is CNAME flattening?
Cloudflare's term for resolving a CNAME-style record into an IP at the edge.
Are ANAME and ALIAS records the same?
Functionally yes; providers simply use different names for it.
.png&w=2048&q=75)
NameSilo StaffThe NameSilo staff of writers worked together on this post. It was a combination of efforts from our passionate writers that produce content to educate and provide insights for all our readers.
More articleswritten by NameSilo
.png&w=3840&q=75)