4 ms·
Commented on the original outage: Hopefully with this outage Cloudflare will provide non-Enterprise plans a CNAME record, allowing us to not use Cloudflare DNS
by rob-olmos 6y ago
Commented on the original outage: Hopefully with this outage Cloudflare will provide non-Enterprise plans a CNAME record, allowing us to not use Cloudflare DNS and more quickly bypass Cloudflare if the need arises.
- stepstop 6y agoThat makes sense. What is the cost difference between those plans? (I’m not a Cloudflare user, just curious)
- jasongill 6y agoThe self service plans are free, $20, and $200 a month. Enterprise is $2000 a month and up (having recently been quoted on it)
- ReidZB 6y agoI'm pretty sure CNAME setups are allowed on the Business plan ($200/month). I had to set one up not too long ago.
- zamadatix 6y agoIf Cloudflare DNS is down how would that CNAME resolve? In the case that record is not hosted by Cloudflare DNS then why does it matter if it's a CNAME or not? Sorry, probably not familiar with the offering you're referring to.
- toast0 6y agoThe idea is you host in your DNS foo.example.org. CNAME blah.customer.cloudflare.whatever. with a ttl of loke 5 minutes Then when cloudflare goes down, you switch that to your origin server, or your static system is down page or something. Most of your traffic moves within 5 minutes and when you're satisfied Cloudflare is working again, you move traffic back. If you've delegated your domain to Cloudflare, you can switch your delegation at your registrar, and a lot of TLDs update their servers pretty quick, but the TTL is usually at least a day, so you'll be waiting a while for traffic to move.
- usr1106 6y agoBut now you have an additional point of failure. You would need a very reliable DNS provider to host that CNAME. It increases your flexibility when CF has an issue, bit it does not necessarily increase the reliability of your site.
- toast0 6y agoYes, but if all your fancy names are simply cnames, you can use normal zone transfers to copy between servers, and use servers from multiple providers. Most recursive resolvers will retry requests against multiple delegated name servers until they get one that responds (or they all fail to respond). It adds some delay, so you wouldn't want the servers to be down often, but it's tolerable.