Problem
Our primary domain example.com has DNS hosted on Cloudflare. If Cloudflare terminates our account, all DNS resolution breaks — not just CDN protocols, but the subscription URL itself.
Current State
sub.example.com → CF Pages (works)cdn.example.com, cdn2/3/4.* → CF proxied A records<backup-domain> → Vercel (backup sub, separate registrar)
What We Need
- Move DNS for
example.com to an external provider (Hetzner DNS, Cloudflare for only non-critical records, or Route53)
- OR acquire a third domain on a completely separate registrar/DNS
- Ensure at least one subscription URL survives a full CF account termination
Options
| Option |
Cost |
Effort |
Risk Mitigation |
| Hetzner DNS (free) |
$0 |
Low |
Moves DNS off CF, but lose CF proxy features |
| Route53 |
~$0.50/mo |
Medium |
Enterprise DNS, separate from all VPN providers |
| Keep CF DNS + add backup domain |
$10/yr |
Low |
Two independent paths |
| Vercel DNS for (current) |
$0 |
Done |
Already working as backup |
Status
<backup-domain> on Vercel is already our insurance policy- But if users only know
example.com and it goes down, they're stuck
- Need to document the backup URL prominently in client setup guides
Problem
Our primary domain
example.comhas DNS hosted on Cloudflare. If Cloudflare terminates our account, all DNS resolution breaks — not just CDN protocols, but the subscription URL itself.Current State
sub.example.com→ CF Pages (works)cdn.example.com,cdn2/3/4.*→ CF proxied A records<backup-domain>→ Vercel (backup sub, separate registrar)What We Need
example.comto an external provider (Hetzner DNS, Cloudflare for only non-critical records, or Route53)Options
Status
<backup-domain>on Vercel is already our insurance policyexample.comand it goes down, they're stuck