What each record does
An A record points a name at an IPv4 address: yourdomain.com goes to 203.0.113.10. An AAAA record does the same job for an IPv6 address. It is a direct answer.
A CNAME points a name at another name: www.yourdomain.com goes to shops.myshopify.com, and the resolver then looks up that second name to find the address. Platforms like CNAMEs because they can change the addresses behind their hostname without asking every customer to edit DNS.
Both are on the record types page with examples. The catch is where each one is allowed to live.
Why the root can't have a CNAME
The DNS rules say that a name with a CNAME may not hold any other record. A CNAME means "this name is only an alias, look over there for everything", so nothing else can sit beside it.
Your root domain (also called the apex or bare domain: the name with nothing in front of it) always holds other records. The NS and SOA records that make the zone work live there. So do your MX records for email and TXT records such as SPF. A CNAME at the root would collide with all of them.
Panels handle this in different ways. Many simply reject a root CNAME. Where one is accepted as a plain CNAME, the usual casualty is email, because a lookup for your MX records gets sent to the alias target instead. The same rule applies to subdomains: if www is a CNAME, you cannot also put a TXT record on www.
Three ways to point the bare domain
1. Use A records
Many platforms publish fixed addresses for exactly this purpose. Shopify gives one A record for the root, GitHub Pages gives four, and a server or VPS has its own IP. This works at every DNS provider. The trade-off is that if the platform ever changes its addresses, you have to update the record yourself. The Route Planner holds the values for each destination it covers.
2. Use ALIAS, ANAME or CNAME flattening
Some DNS providers offer a record that behaves like a CNAME but is legal at the root. You enter a hostname, the provider looks up its address and answers with ordinary A records, so the rule is never broken. The name varies. Porkbun calls it ALIAS. Cloudflare lets you add a CNAME at the root and flattens it for you. Amazon Route 53 and Azure DNS have alias records for pointing at their own cloud resources. It is not a standard record type, so it only exists where your DNS provider has built it. If yours has not, use option 1 or 3.
3. Redirect the root to www
Make www the real address of the site with a normal CNAME, then send the bare domain to it with your registrar's domain forwarding (choose the permanent, 301 kind). Check first that the forwarding service answers https:// requests as well as http://. Make a note that it is switched on, too: as our GoDaddy and 123 Reg guides point out, forwarding can override an A record you add to the root later.
Typing it in: @, blank or the full name
Once you know which record you need, the last hurdle is the Name field, because panels disagree on how to write "the root". GoDaddy, Namecheap and Cloudflare want @. Porkbun and Route 53 want the field left blank. cPanel wants the full domain with a trailing dot: yourdomain.com. Each of our provider guides has an "at a glance" box that says which applies.
Before you add the new record, clear the road:
- Delete the parking A record that most registrars add to a new domain. Two A records on the root means visitors are sent to either one at random.
- Delete any existing
wwwrecord before adding awwwCNAME. A CNAME cannot share its name. - On Cloudflare, check whether the record should be proxied (orange cloud) or DNS only. The Route Planner flags the records that must not be proxied.
So which should you use?
- Root domain: A records, or ALIAS or flattening if your DNS provider has it and the platform gives you a hostname instead of an IP.
- www and other subdomains: a CNAME if the platform gives you a hostname, an A record if it gives you an IP.
- Email (MX) targets: always a hostname with its own A record. Never a CNAME, never a bare IP address.
Whichever you choose, pick either yourdomain.com or www.yourdomain.com as the main address and make sure the other one redirects to it, so visitors and search engines see a single site. Then give the change time to reach caches. How long that takes depends on the TTL of the record you replaced.



