You've got a CDN, a landing-page builder, or a SaaS product that gives you a hostname to point your domain at — something like abc123.cdn-provider.net — instead of an IP address. That's easy for a subdomain: add a CNAME for app or www and you're done. But when you try to do the same thing for the bare root domain, yourdomain.com with nothing in front of it, the zone editor throws an error or the change just silently fails to resolve. This trips up more customers than you'd expect, and it's not a SkyServer limitation — it's a DNS rule that's older than most of the tools people are trying to use around it.
Symptom
Typical signs you've hit this:
- cPanel's Zone Editor rejects a CNAME record on the root/apex entry (the row with no subdomain, just
yourdomain.com.) yourdomain.comdoesn't resolve at all, or resolves to the wrong place, whilewww.yourdomain.comworks fine- Your CDN or app provider's setup docs say "just CNAME your domain to us" and don't mention that this doesn't work for apex domains
- You added the CNAME anyway (some panels let you), and now MX or other records on the same domain have stopped working
Cause: the apex CNAME restriction
This isn't a bug — it's RFC 1912 and the core DNS spec doing what they were designed to do. A CNAME record means "this name is an alias — go look up whatever records exist for the target name instead." The rule is that if a name has a CNAME, it can have no other records of any type at that same name.
The problem is the root of your zone almost always needs other records too — at minimum an SOA and NS record, which every zone has automatically, and usually MX records for email and maybe TXT records for SPF or domain verification. A CNAME at the apex would conflict with all of those, so resolvers and DNS servers (including cPanel's BIND-based zone editor) simply won't allow it.
Subdomains don't have this problem because they don't need SOA/NS records of their own — that's exactly why www or app can be a CNAME with no issue, but the bare domain can't.
Fix: three real options
Which one you use depends on what your DNS is actually capable of and what the target service needs.
Option 1 — ALIAS / ANAME record (best, if your DNS supports it)
An ALIAS (also called ANAME, or "CNAME flattening" depending on the provider) looks like a CNAME to you when you set it up, but the DNS provider resolves the target hostname on its own servers and hands out the resulting A/AAAA records to the world — so from the outside it looks like a normal A record, not a CNAME. That satisfies the RFC and lets your app's IP change without you touching anything.
Standard cPanel zone editors backed by plain BIND generally don't offer this natively. If you need it, options are:
- Move DNS hosting for that domain to a provider that supports ALIAS/ANAME (Cloudflare calls it CNAME flattening and applies it automatically at the apex, no separate record type needed)
- Ask your SkyServer support team whether ALIAS is available for your specific hosting package's DNS — some newer cPanel/DNSSEC-enabled zones support it via a plugin
If you're already using Cloudflare in front of a SkyServer-hosted site (see our Cloudflare + cPanel setup guide), this is usually the path of least resistance: point nameservers to Cloudflare, add a CNAME at the apex there, and Cloudflare flattens it for you.
Option 2 — plain A/AAAA record with the target's published IPs
Most CDNs and SaaS platforms that hand you a CNAME target also publish a static IP (or small IP range) specifically for customers who can't use ALIAS. Check their docs for a phrase like "apex domain setup" or "root domain / naked domain" — it's usually right below the CNAME instructions. Add that as a plain A record (and AAAA if they publish an IPv6 address) at the root.
The catch: if the provider ever rotates those IPs without warning, your apex domain breaks until you notice and update the record. This is fine for stable, well-documented services; it's riskier for smaller providers that don't guarantee IP stability.
Option 3 — redirect the apex to www instead
If you don't strictly need the app/CDN to answer at the bare domain, the simplest fix is to sidestep the whole problem: keep www.yourdomain.com as your real CNAME target, and make yourdomain.com just 301-redirect to www.yourdomain.com. In cPanel this is usually an A record on the apex pointing at your SkyServer hosting IP, with a redirect rule (via .htaccess or the Redirects tool) sending apex traffic to www. Search engines treat a properly configured 301 the same as a direct visit for ranking purposes, so this costs you nothing on SEO.
Quick comparison
| Approach | Handles IP changes automatically | Needs a specific DNS provider | Best for |
|---|---|---|---|
| ALIAS/ANAME (e.g. Cloudflare flattening) | Yes | Yes | CDNs, platforms with rotating IPs |
| Static A/AAAA record | No | No | Providers with a documented, stable apex IP |
| 301 redirect apex → www | N/A | No | When www is fine as the "real" address |
Prevention
A few habits save you this scramble next time:
- Before committing to a CDN or SaaS product, search their docs for "apex," "root," or "naked domain" setup instructions — reputable providers document this because it comes up constantly
- If you expect to need ALIAS/ANAME support down the line, put that domain's DNS on a provider that offers it (Cloudflare's free tier covers this) rather than discovering the limitation mid-migration
- Keep a note of which records exist at your apex (MX, TXT/SPF, DMARC, verification records) before making DNS changes — these are exactly the records that silently break if something ever does slip a CNAME onto the root
- Whichever option you pick, verify with
dig yourdomain.com(ordig yourdomain.com ANYif your resolver allows it) after the change, and give it time to propagate before assuming it's broken — see our DNS propagation guide if resolution looks inconsistent across locations
Frequently Asked Questions
Can I just force a CNAME onto my root domain anyway?
Some zone editors will let you save it, but it violates the DNS spec and will conflict with your SOA, NS, and any MX/TXT records at that name. Expect email delivery, domain verification, or the domain itself to break unpredictably. Don't do it even if the interface allows it.
What's the difference between ALIAS and ANAME?
They're marketing names for the same underlying idea from different DNS providers — a record that behaves like a CNAME for setup purposes but gets resolved server-side into A/AAAA records so it's valid at the zone apex. Cloudflare calls its version "CNAME flattening" and applies it automatically; you don't pick a separate record type there.
Does cPanel's Zone Editor support ALIAS/ANAME?
Standard BIND-based cPanel zones generally don't expose this as a record type. If you need it for a domain hosted with SkyServer, the practical route is running that domain's DNS through a provider like Cloudflare (with SkyServer still hosting the site) rather than the cPanel zone editor.
Will redirecting my apex to www hurt my SEO?
No. A proper 301 redirect passes ranking signals to the destination URL, and search engines have handled the apex-to-www pattern for decades. Just make sure it's a real 301, not a 302 or a JavaScript redirect, and that you're consistent about which version (with or without www) you use in links and marketing.
My provider only gave me a CNAME target, no IP — what now?
Email their support and ask specifically for "apex/root domain" or "naked domain" setup instructions — most CDNs and app platforms have a documented IP or ALIAS path for exactly this case, it's just often buried below the main CNAME instructions aimed at subdomains.
