5 ms·
> we may also wildcard your DNS to localhost and set the TTL on your zone out to a year. You’ve been warned No, this is simply indefensible. There's simply no
by FDSGSG 7y ago
> we may also wildcard your DNS to localhost and set the TTL on your zone out to a year. You’ve been warned
No, this is simply indefensible. There's simply no way you could ever excuse this.
Suspending a customer domain is OK, this is not.
- Guvante 7y agoI think it depends on what you did. If you did something crazy like run a DDoS C&C layer off your subdomains then it would make perfect sense for them to respond like this. As others said every service reserves the right to do things like this, they just typically phrase differently. To quote GoDaddy: > You acknowledge and agree that GoDaddy and registry reserve the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on lock, hold or similar status, as either deems necessary, in the unlimited and sole discretion of either GoDaddy or the registry: .. snip .. (ii) to protect the integrity and stability of, and correct mistakes made by, any domain name registry or registrar, Emphasis mine and a bit snipped out since this is already long. This says if it affects their stability they can transfer your registration as they see fit. It doesn't include any protections on when you can change the domain or what they can change it to meaning blackholing you into localhost for a year is fine.
- FDSGSG 7y agoCome on. They made this threat in a very specific context, it has nothing to do with abusive activity like running a DDoS C&C. >As others said every service reserves the right to do things like this, they just typically phrase differently. To quote GoDaddy: Suspending a domain is standard practice, sabotaging one by setting long EOLs is not. It is dishonest to suggest that these are similar.
- mywittyname 7y agoIt sounds like they are doing society a favor.
- FDSGSG 7y agoBy going after DDoS victims? Care to explain further?
- danShumway 7y agoDeciding who they do and don't want to do business with is fine. It's not their job to protect vulnerable domains. Actively sabotaging someone so they can't take their business elsewhere is not OK -- especially when their offense boils down to, "we didn't tell you that someone else was attacking us." That's not doing anyone any favors except attackers. Bear in mind, the context here is not domains doing something awful or spamming people or mounting your own attacks. It's "somebody's attacking you, and we think that you suspected they would".
- deleted 7y ago[deleted]
- wstuartcl 7y agoI read it as tongue in cheek (to emphasize DO NOT DROP YOUR ACTIVE DDOS ON OUR SERVERS) and not something they actually would execute. Has anyone ever seen them do anything like this?
- chii 7y agoa threat is only as good as your willingness to execute it. If they don't actually intend to, the threat is meaningless.
- smnrchrds 7y agoYou are much braver than me. I do not dare read a contract (or the explanation of one) as tongue in cheek.
- nickodell 7y agoIf it's a joke, or sarcastic, why is it in a document labeled "Plain English Terms of Service?" For that matter, why follow it up with "You've been warned?" >Has anyone ever seen them do anything like this? No, I've never seen them do this. But at the same time, I'm not going to give them the opportunity.
- sgroppino 7y agoAgree - they can't roll back something like this if they get it wrong...
- deleted 7y ago[deleted]