- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Also, interesting comment I found on HackerNews (HN):
This post was definitely demoted by HN. It stayed in the first position for less than 5 minutes and, as it quickly gathered upvotes, it jumped straight into 24th and quickly fell off the first page as it got 200 or so more points in less than an hour.
I’m 80% confident HN tried to hide this link. It’s the fastest downhill I’ve noticed on here, and I’ve been lurking and commenting for longer than 10 years.
I agree. It’s shitty for Cloudflare to just straight up destroy this company’s DNS, but also it seems like the company violated the ToS. They had about two weeks to migrate to something else, but instead they just continued debating with CF. Also, this company doesn’t have a secondary DNS server in case CF ever went down? That’s pretty stupid on their part. Redundant systems are key, I hope they learned that lesson haha
Isn’t CF advertising themselves as the solution to needing multiple DNS’ with their failsafes, switchovers and load balancing?
If I need to maintain multiple anyway, what’s the benefit of CF to begin with? There are a million CDNs out there I could use instead, if I still have to maintain the network architecture.
Do you believe everything that companies tell you? If Google or Apple tell you “we’re the solution to everything, you never need to buy anything else”, do you listen to them?
No, but if I use a service to solve a specific problem only to see the need to have a failover in place regardless, I might as well not use the service.
Regardless of what they tell you, if you care about uptime, you ensure this yourself. I feel this is 60% the company’s fault and 40% Cloudflare’s.
Thanks for actually reading my comment unlike the other guy