Comment by remram
8 months ago
What is "don't put your eggs in one basket" here? Your DNS has to point to something... and changing it will go through propagation delays, during which it will be down if you are banned suddenly.
It's not like you can have your domain/DNS somewhere else and point to Cloudflare IPs (to not put DNS and CDN in same basket). Cloudflare does not allow that setup.
You can't protect your website from your DNS provider or hosting provider suddenly kicking you off. You are going to be offline for a couple of days.
> You can't protect your website from your DNS provider or hosting provider suddenly kicking you off. You are going to be offline for a couple of days.
Sure you can. Colocate in two or three places. You're your own DNS provider and your own hosting provider. If one of your colocation companies doesn't like what you're doing for whatever reason, you use the other two until you replace that provider.
"Do it all yourself" is a far cry from "don't put all your eggs in the same basket". The latter principle I agree with, the former not so much.
And you are still unprotected from your DNS registrar kicking you out, directing your domain to some "customer terminated" page until you can find another registrar, and have new NS records propagate (days).
You're not really making any points, or at least none that're relevant to this discussion.
Let me summarize: businesses do silly and sometimes stupid things for irrational reasons, or for reasons they never care to divulge. To avoid what happened that led to this discussion, the most suitable solution is to not be at the whims of companies that don't communicate well.
The legal requirements of domain registrars are clearly spelled out, unlike the TOS from, say, Cloudflare which leaves tremendous amounts to the imagination. These are not the same at all.