>we may also wildcard your DNS to localhost and set the TTL on your zone out to a year. You’ve been warned
Maliciously tampering with customer DNS configs to DoS them for extended periods? Fucking incredible.
>We are NOT a DDoS Mitigation Service. Yes, we have a lot of DDoS mitigation in place. No, this isn’t here so that you can get cheap DDoS mitigation. You cannot use any services here if you are, have been or think you may be the direct target of a DDoS attack. Contact us instead for a referral to a real DDoS mitigation company. If you come on this system knowingly bringing a DDoS on your heels we shut down service (we may also wildcard your DNS to localhost and set the TTL on your zone out to a year. You’ve been warned).
All things notorious for attracting DDoS attacks.
Sometimes ransom but CloudFlare has kind of killed that line of business.
Also, there's a long tail of totally garbage behavior in the DNS space. At my last job, as part of moving our domains off of Dyn/Oracle, we delegated the domains to our self hosting via the domain registry, and changed the NS records at Dyn to point only at our self hosting, but we were still seeing a steady trickle of traffic to Dyn after 30 days.
However, I don't see why changing your nameservers would help if your resolver was always hitting a cache entry with a 1yr TTL.
but, devils advocate, maybe it's just there to scare off potential spammers/scammers?
Having worked at an ISP in security/spam/abuse, these people are a huge drain on resources.
That's not a professional relationship to me. And I would hazard a guess that if I tried to contract with EasyDNS and added clauses that gave myself similar amounts of power over them, they wouldn't be as trusting of me.
The point of a legal document is to set explicit boundaries, not to set a "tone" to the relationship or scare off scammers. Setting tone is what your FAQ is for.
Why are you engaging in these bizarre mental gymnastics to defend this? The threat is made in a context strictly unrelated to spammers/scammers.