CNAME Record Verification: How to Check and Fix DNS Aliases
Verify a CNAME points where you expect, avoid apex CNAME mistakes, and unblock domain verification flows that depend on correct alias records.
Verification says “DNS found” but TLS fails. The CNAME target is off by one label — shops.example.net instead of shops.example.com. Browsers and SaaS checks disagree in maddening ways until the alias matches vendor docs exactly.
A CNAME means “this hostname is an alias of that hostname.” Wrong, missing, or conflicting records break CDNs, certs, and ownership flows.
What a CNAME is
app.example.com. CNAME shops.example.net.
Lookups for app.example.com continue at the target. Common uses: CDN frontends, DKIM CNAME delegation, SaaS custom domains, some vendor verification patterns.
How to check a CNAME
- Open the CNAME checker.
- Enter the full hostname you configured (
www,verify,app) — not the apex unless the apex is truly the alias. - Match the target to provider docs (trailing dots and subdomain depth count).
- Follow nested CNAMEs until A/AAAA appear.
- Still Unverified in product? Read why your domain may show unverified — wrong host labels top the list.
Use DNS lookup when you need MX/TXT/NS on the same zone.
Rules that bite teams
| Rule | Why it matters |
|---|---|
| No other data at the same owner name | CNAME owners generally cannot also hold A, MX, or TXT on that label |
| Apex constraints | True apex CNAME is often forbidden — ALIAS/ANAME instead |
| Chains | Each hop adds latency and failure surface |
| TTL | High TTL slows rollback after a bad target |
Apex must serve TXT verification and alias to a CDN? Classic apex CNAME will not work. Use apex alias from your DNS host or verify on a supported subdomain.
Verification workflows (PandaONE and others)
Patterns:
- TXT on
_vendor-verifyor apex - HTTP file under
/.well-known/ - CNAME to a vendor-controlled target
When status stays pending:
- Confirm NS still point at the zone you edited.
- Confirm the host field in the UI (
www, FQDN,_prefix). - Wait for TTL — do not rewrite records every two minutes.
- Confirm HTTPS redirects are not blocking HTTP file checks.
- Re-query with the CNAME checker.
PandaONE TXT/HTTP detail: Why is my domain unverified?.
CNAME vs A vs ALIAS
- A / AAAA — direct IP
- CNAME — name → name
- ALIAS / ANAME — apex-friendly synthesized alias
Follow provider docs for apex. Guessing yields “SSL broken” when DNS never hit the load balancer.
Provider UI gotchas
- Some want only the left label (
www,_acme-challenge) - Others want FQDN and duplicate the zone if you paste twice
- Auto-append can produce
app.example.com.example.com
Re-query after save. One wrong label fails TLS and verification while the panel looks green.
DKIM selector CNAMEs must match the ESP hostname exactly. A working site CNAME does not fix mail signing.
Propagation and debugging order
- Registrar NS → the DNS host you edited
- CNAME from more than one resolver if possible
- Target resolves to healthy A/AAAA
- Certificate SANs include your alias hostname
- Then application 404s
“Clear CDN cache” rarely helps when the alias never pointed at the CDN. Start with authoritative answers.
FAQ
Why does dig show CNAME but the site fails?
Wrong target, SAN mismatch, or dead origin behind the CDN. DNS first, then certs.
Can I CNAME and TXT the same name?
No on the same owner under normal rules. Use a subdomain for verification TXT.
How long until updates work?
Often minutes; bounded by prior TTL. Corporate resolvers cache longer.
Does a CNAME hide my server?
Follow the chain to A/AAAA. Not an access-control mechanism.
Keep verification CNAMEs forever?
While the vendor requires them. Remove abandoned SaaS CNAMEs so old vendor hostnames cannot become takeover routes.
Summary
Query the exact hostname, match the target string to vendor docs, and walk the chain to A/AAAA. Apex + TXT + alias conflicts need ALIAS/ANAME, not a classic apex CNAME. Confirm NS, SANs, then the app. Use the CNAME checker after every save.