It sucks because up until the “sales team” rugpull, they’re the cheapest (and closest to reality) for bandwidth cost, virtually all the other CDN providers charge astronomical prices and their margins are hundreds to thousands of percentage.
If the costs are mostly variable in how much they serve up, and uptime is sufficiently important, maybe have two CDNs and use the other one as a fallback when things start going tits-up?
I assume that the way that this works is that I host content at www.foo.com and they have their nameserver resolve www.foo.com to different IPs based on the geolocation of the browsing user’s IP.
Is it possible to convert www.foo.com to a CNAME that can be redirected away from their nameservers? Like, I make www.foo.com be a CNAME directed at www.foo-cloudflare-cdn.com. They own www.foo-cloudflare-cdn.com, they serve A or AAA queries there on their nameservers. But if I want fallback, I update the CNAME to point at www.foo-backup-cdn.com, which is served by a different CDN.
Are there technical barriers to that, do you know?
We need to break up Cloudflare.
It sucks because up until the “sales team” rugpull, they’re the cheapest (and closest to reality) for bandwidth cost, virtually all the other CDN providers charge astronomical prices and their margins are hundreds to thousands of percentage.
If the costs are mostly variable in how much they serve up, and uptime is sufficiently important, maybe have two CDNs and use the other one as a fallback when things start going tits-up?
Cloudflare tries to enforce pretty strong vendor lock in by requiring you use their nameservers.
Also subdelegate domains are an “enterprise” feature, so no luck there.
Basically the CDN market sucks, not a shocker Netflix, Google, Valve, and many others operate their own.
Hmm.
I’m not familiar with the constraint.
I assume that the way that this works is that I host content at www.foo.com and they have their nameserver resolve www.foo.com to different IPs based on the geolocation of the browsing user’s IP.
Is it possible to convert www.foo.com to a CNAME that can be redirected away from their nameservers? Like, I make www.foo.com be a CNAME directed at www.foo-cloudflare-cdn.com. They own www.foo-cloudflare-cdn.com, they serve A or AAA queries there on their nameservers. But if I want fallback, I update the CNAME to point at www.foo-backup-cdn.com, which is served by a different CDN.
Are there technical barriers to that, do you know?
We just should not use cloudflare. Why is everybody still trying to use cloudflare.
It drives me nuts. The default answer on all network problems: why don’t you just use cloudflare? No! No no.
Counterpoint: I find networking challenging, and I’m not particularly accountable for the natural consequences of not knowing how stuff works.
This could end fine for everyone? Maybe an AI will understand it for me. (This is sarcasm. I agree with you.)