News for hackers. Stuff that matters.

A comment on Cloudflare outage on July 17, 2020. Parent comment

Re:Cloudflare outage on July 17, 2020 by user5994461 on Saturday July 18, 2020 @08:58AM (#23881122)
>>> Spread your name servers, and use short-TTL weighted CNAMEs, defaulting to say, 99% Cloudflare, 1% your internal load balancer.

Which can't be done because it invalids the point of using CloudFlare!

CloudFlare is used to protect your site from DDoS attacks and ransoms. It has to hide the IPs of the servers otherwise attackers will DDoS the servers directly, bypassing CloudFlare.

[ Parent | on HN ]
Re:Cloudflare outage on July 17, 2020 by dorfsmay on Saturday July 18, 2020 @10:35AM (#23881628)
Then you use > 1 CDN and switch traffic away from the faulty one. Also, if you serve a very large amount (as in different, say tens of thousands of different images) of data, 1 % of traffic is not enough to keep the other CDN caches warm.

I know of at least one site that works this way which has allowed them to weather CDN outages.

[ Parent | on HN ]
Re:Cloudflare outage on July 17, 2020 by almost_usual on Saturday July 18, 2020 @02:06PM (#23883362)
This isn’t an uncommon setup for large corporations.
[ Parent | on HN ]
Re:Cloudflare outage on July 17, 2020 by godzillabrennus on Saturday July 18, 2020 @11:11AM (#23881894)
You can use cloudfront or another cloud WAF service as your alt DNS. I think Akamai has a solid one if you can afford it.
[ Parent | on HN ]
Re:Cloudflare outage on July 17, 2020 by phyzome on Saturday July 18, 2020 @09:32AM (#23881294)
You can also use CloudFlare for caching, or as a WAF, which you might not care about during a relatively short CloudFlare outage.
[ Parent | on HN ]