A CNAME is not allowed at the apex, yet hosted services often want you to point the bare domain at them. DNS hosts solve it themselves: they look up the target and serve the result as ordinary A and AAAA records — called ALIAS, ANAME or CNAME flattening depending on the host.
| A standard record type? | No — a feature of your DNS host |
| What resolvers see | Ordinary A and AAAA records |
| Standard alternative | An HTTPS record in alias mode (RFC 9460) |
| Defined in | RFC 1034 §3.6.2 |
Look up the A records of any name
One question to DNS, answered as it is. You can change the record type too.
What it does
The apex always has NS and SOA records, and a CNAME may not share its name with anything, so example.com cannot be a CNAME. Flattening happens inside your DNS host: it resolves the target (say, the load balancer’s name) and answers with that name’s addresses, refreshing them as they change. Cloudflare calls it CNAME flattening, Route 53 alias records, others ALIAS or ANAME.
An effort to standardise ANAME never finished. The HTTPS record’s alias mode is the standard way to alias an apex for browsers, though clients that do not read HTTPS records still need A and AAAA.
How it is written
| Field | Meaning |
|---|---|
| Name | @ (the apex) |
| Value | A host name — the host turns it into addresses |
Examples
example.com. ALIAS myapp.herokudns.com.
In the DNS host’s panel. Resolvers see A records with myapp’s current addresses.
Common mistakes
- Moving to a DNS host without ALIAS support and replacing the alias with fixed A records that go stale.
- Expecting a lookup to show the ALIAS itself — only the addresses are visible from outside.
What we recommend
Use your DNS host’s ALIAS or flattening for the apex, and CNAMEs for subdomains.
Sources
Checked on 25 September 2026 against these official sources:
- RFC 1034: Domain names — rfc-editor.org