Engineering Glossary · DNS Records
Cname record — Every CNAME Hop Is Another Lookup Your Visitor Waits For
A vendor has given you a hostname to alias, and you want to know what that indirection costs before you put it in front of users.
The short answer
A CNAME makes one hostname an alias of another, so the name resolves to wherever its target currently points. That indirection is genuinely useful — the provider can move addresses beneath you forever without touching your zone — and it is not free, because a resolver has to follow the chain to its end before it has an address.
The cost is one extra lookup per hop that is not already cached. One hop is usually invisible. A chain that runs through a vendor hostname, into a platform hostname, into a CDN hostname is three resolutions standing between a cold visitor and a connection, and that is worth measuring before it ships.
By the HostingFast team · Reviewed 24 August 2026
100+
Terms defined properly
2 min
Read time, end to end
Plain
English, no hand-waving
24/7
Engineers on shift
Indirection by design: www aliases the apex, or a shop subdomain aliases a commerce platform's hostname. When the target's addresses change, every alias follows automatically, which is exactly why SaaS providers hand you a hostname to point at rather than a number.
There are rules. A CNAME cannot coexist with any other record on the same name, which is why the bare domain traditionally cannot carry one — it already holds SOA and NS records. Some providers work around this with flattening, marketed as ALIAS or ANAME, which resolves the target and publishes the resulting addresses for you.
Counting the hops in your chain
Ask for the name and read the full answer rather than just the final address: each intermediate CNAME appears in the reply. Count them. One is normal, two is common with a platform in front of a CDN, and three should prompt a question about whether every layer is still needed.
Then time it. Request the hostname on a cold cache and record the lookup segment, and compare against a name that resolves directly to an address. The difference is the price of the flexibility, and it is usually a price worth paying — but it should be a decision rather than an accident.
The apex problem, and the flattening workaround
You cannot put a CNAME on the bare domain, because the apex already carries records a CNAME is not allowed to share a name with. Providers that offer flattening resolve the target on your behalf and publish A records with the result, giving you the behaviour without breaking the standard.
The trade-off is that the flattening provider is now resolving on a schedule you do not control. If the target's addresses change quickly, the flattened answer can lag. For most vendors this is irrelevant; for anything doing rapid failover, it is worth checking.
Why a valid CNAME still gets rejected
Vendor validation failures nearly always come down to four things: a typo in the target, a trailing dot missing or added where the panel did not expect it, the record attached to the wrong label, or a panel that silently appended your domain to a value that was already fully qualified.
Query the name directly and you see exactly what every other resolver on the planet sees. That single check settles the argument with a vendor's support desk faster than any screenshot of a control panel.
Aliases on this platform
Subdomains, addon domains and their records are managed from the panel, and free SSL is issued for each hostname you attach — including aliased ones — and renewed automatically before expiry.
The renewal price matches the price you signed up at, so the plan that carries all these hostnames costs the same in year two as it did in year one. There is no introductory rate quietly expiring in the background.
Written to be checked, not admired
The point of a reference is to shorten an argument. Each entry names the query that produces the evidence, so a disagreement with a vendor lasts one command rather than one week.
Free SSL is included on every plan and renews itself ahead of expiry, for aliased hostnames as well as for the main one.
- 100+ entries with the evidence step included
- Chain counting and hop cost explained
- Wired into A Record, DNS and Subdomain
- Written by the engineers on the platform
Why HostingFast
Standard on every plan
Indirection, priced
The flexibility a CNAME buys, stated alongside the lookup it costs a cold visitor.
CNAME, as a chain
How to read every hop in an answer and decide whether the layers still earn their place.
The apex rule explained
Why the bare domain cannot hold one, and what flattening does about it.
Rejection causes listed
Four specific reasons a valid-looking record gets refused by a vendor, in order of likelihood.
Vendor arguments shortened
One query shows what every resolver sees, which usually ends the discussion.
Continues into its neighbours
A Record, Subdomain and TXT Record carry on from here.
Quick Start
From order to online
- 1
Read the whole answer, not the last line
Query the hostname and look at every record in the reply. The intermediate aliases are the hops you are paying for.
- 2
Compare a cold lookup against a direct one
Time a resolve of the aliased name and of a name that points straight at an address. The gap is the cost of the chain.
- 3
Check the target exactly as published
Confirm the trailing dot, the label and the fully qualified value. Panels differ in what they append, and that is where most rejections come from.
- 4
Prune layers that no longer do anything
If a hop exists because of a vendor you stopped using two years ago, remove it and re-time the lookup.
Built In
Loaded onto every plan
- Subdomain and alias records managed from the panel
- Free SSL for every hostname, aliased ones included
- Renewal billed at the price you originally signed up at
- Daily backups with self-service restores
- LiteSpeed caching at server level on every plan
- Per-site PHP version switching from the panel
- NVMe SSD storage across every tier
- Human support available at any hour
Frequently Asked
What people ask us most often
How many CNAME hops is too many?
One is normal and effectively free once anything in the chain is cached. Two is common when a platform sits in front of a CDN. Three or more deserves a review: on a cold cache each unresolved hop is another round trip before a connection can even be attempted, and it is usually a layer nobody has questioned since it was added.
Why can the bare domain not have a CNAME?
Because the apex already holds SOA and NS records, and the standard forbids a CNAME from sharing a name with any other record. The workarounds are provider-side flattening, published as ALIAS or ANAME, or an A record at the apex with CNAMEs on the subdomains beneath it.
The CNAME looks right but the vendor still rejects it. Why?
Query the name directly and compare the answer, character for character, with what the vendor asked for. Nine times in ten it is a trailing dot, a panel that appended your domain to an already-qualified value, or the record sitting on the wrong label. The query settles it immediately.
How does payment and auto-renewal work?
By credit or debit card through a secure checkout, with renewals billed at the same rate as the original order. Every invoice is in your client area and auto-renewal is a toggle in your account — no phone call, no retention conversation.
Keep reading
TXT Record
Arbitrary text in a zone, and the lookup limits that come with it.
Subdomain
Named branches of your domain, each with its own root and certificate.
How to Create an SPF Record
Publishing a sender policy properly, with the lookup limit explained.
VPS Hosting
KVM virtual servers with root access, DDoS filtering and a flat monthly price.
Dedicated Servers
Bare metal with a panel included and the specification stated up front.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Fewer hops, fewer handshakes.
Scaling from one site to a rack of servers is an account change here, not a migration you have to survive.
View VPS Hosting plans