0 of 8 reviewed

Client apex domains: stay on Cloudflare, or move hosting?

Cangelosi forced this question. Here is what I verified, what it would actually cost to leave, and the one change I think we should make.

Your premise is half right. Cloudflare genuinely cannot serve a client apex when the client keeps their own DNS. That is a hard wall at our price point, not a misconfiguration, and no amount of fiddling fixes it.

But moving hosting is aimed at the wrong target. Only the apex redirect is broken. Every www site works on Cloudflare with one CNAME from the client. And of all our live client domains, Cangelosi is the only one where the client keeps their DNS. The rest of our apexes already work because those zones sit in our account.

Why the apex fails and www does not

Works today
Visitor
www.cangelosi.com
→
Frontline DNS
CNAME to pages.dev
→
Cloudflare Pages
Site serves, cert auto
Broken today
Visitor
cangelosi.com
→
Frontline DNS
A records, no CNAME allowed at apex
→
Cloudflare for SaaS
409, needs paid Apex Proxying

A CNAME is illegal at a zone apex. Cloudflare proves apex ownership only by CNAME, or by Apex Proxying, which is Enterprise with allocated static IPs and account team pricing.

What is already built (verified on the account today)

PieceStateWhat that means here

The options

Decisions I need from you

Progress saves on this device. Safe to close and come back.