Quick Answer: A Record vs CNAME
An A record maps a name to an IPv4 address — 'webji.in lives at 203.0.113.10'. A CNAME maps a name to another name — 'cdn.webji.in is whatever cdn-provider.net resolves to' — and inherits that target's addresses.
| Dimension | A record | CNAME |
|---|---|---|
| Points to | IPv4 address | Another hostname |
| At zone apex (root)? | Yes | No — protocol forbids it |
| Follows target IP changes | No — manual updates | Yes, automatically |
| Other records at same name | Allowed | Forbidden |
| IPv6 sibling | AAAA record | Works the same |
Rule of thumb: your own stable servers get A records; anything whose IPs you do not control gets a CNAME. The full record set lives in DNS records explained.
What an A Record Does (IP Mapping)
An A record answers "where does this name live?" with an IPv4 address, in a single lookup — the fastest path DNS offers. One name can carry several A records, one per IP, which resolvers use for round-robin load balancing; and unlike a CNAME it can share its name with MX and TXT records. The trade-off is control: when the server's IP changes, you update the record yourself.
What a CNAME Does (Name Aliasing)
A CNAME answers "where does this name live?" with "wherever that name lives": the resolver follows the alias to the canonical hostname and resolves that instead — at least one extra lookup on every first visit. It must be the only record at its name, but it automatically follows the target's IP changes, which is exactly why CDNs and cloud platforms hand you a hostname to CNAME instead of an IP. Keep chains short: a CNAME pointing at a CNAME adds another lookup per hop.
The Root-Domain CNAME Restriction
The rule behind every confused forum thread, in plain terms:
- The zone apex must hold SOA and NS records — they identify the zone's authority.
- A CNAME must be the only record at a name, by definition.
- Both cannot coexist, so a CNAME at the root is a protocol violation; most panels simply reject it.
Practical mapping: apex gets an A record (or provider-side flattening); www gets a CNAME to the apex or your host's hostname; subdomains (shop, blog, staging) freely CNAME to platform hostnames. A verification TXT record at a name you also want as CNAME is a conflict — resolve with A records or nested names.
When to Use Each: Hosting, CDN, www
Concrete setups:
- Pointing at shared hosting — your host gives an IP: A record at the apex, optionally www CNAME'd to it. If the host gives a hostname instead, CNAME the subdomains; the apex still needs an A record.
- Attaching a CDN — edge hostnames change constantly, so subdomains CNAME to the CDN target. Full-site CDN at the apex needs flattening.
- www setups — apex A record plus www CNAME to apex, with redirects choosing one canonical.
- Email — unaffected: MX records live at whichever name receives mail.
Setting these lives in the DNS zone of your domain registration — the zone editor handles all four cases.
ALIAS, ANAME and CNAME Flattening
These are the DNS industry's answers to the apex restriction: the DNS host resolves the CNAME target on its own authoritative servers and returns plain A/AAAA answers, so the record behaves like a CNAME while remaining legal at the root. Two caveats worth knowing. Resolution happens from the provider's servers, so any geo-routing configured on the target sees the provider's location, not your visitor's. And support varies by host — look for an ALIAS or ANAME record type, or a "flatten CNAME at apex" toggle, in the zone editor before you plan a full-site CDN on the naked domain.
Setting Both in Your DNS Panel
Set the nameservers at the registrar, then edit records only in the DNS host those nameservers point at. Editing the other panel does nothing. A website and its mail can use different hosts: the A record sends the site, MX sends the mail.
Frequently Asked Questions
What is the difference between an A record and a CNAME?
An A record maps a name to an IPv4 address — 'webji.in lives at 203.0.113.10'. A CNAME maps a name to another name — 'cdn.webji.in is whatever cdn-provider.net resolves to' — and inherits that target's addresses.
Can I put a CNAME on the root domain?
No — the DNS protocol forbids it. The root must hold SOA and NS records (usually MX too), and a CNAME must be the only record at its name. Point the apex at an A record, or use ALIAS/ANAME/flattening if your DNS host supports it.
Should I point to hosting with an A record or CNAME?
Match what your host hands you. If it gives an IP: A record at the apex, optionally with www CNAME'd to it. If it gives a hostname instead, CNAME the subdomains — the apex still needs an A record.
Can a CNAME point to an IP address?
No. A CNAME's target must be a hostname — that is its whole job. To point a name at an IP address, use an A record (IPv4) or an AAAA record (IPv6).
What is CNAME flattening?
Flattening is a DNS-host feature that resolves a CNAME-like target on the provider's authoritative servers and returns plain A/AAAA answers — so you get CNAME behaviour at the zone apex, where a real CNAME is not allowed.
How many A records can one domain have?
As many as you need: one name can carry multiple A records, one per IP, and resolvers rotate between them (round-robin). What a name cannot do is carry a CNAME alongside anything else — a CNAME must be alone at its name.
Is WebJi® an Indian company?
Yes. WebJi® is headquartered in Jaipur, Rajasthan and has operated since 2005. Billing, support and governance all run from India.
Do you provide GST invoices?
Every purchase and renewal gets a GST invoice with our GSTIN, and hosting prices are quoted exclusive of 18% GST. Claim input credit as applicable.