by zigzaggy on 12/30/20, 3:09 AM with 66 comments
by Waterluvian on 12/30/20, 4:06 AM
by echelon on 12/30/20, 4:13 AM
Godaddy did nothing to help the situation, and the thief had substantial monetary resources and threatened to get me tied up in court. He was ten years older, had an engineering income, and came from a family of lawyers. I was just a college student and felt powerless to do anything about it.
I assume it was social engineering. He had access to the server and database, but was never supposed to have domain name access.
Godaddy sucks.
Also, their founder kills elephants for sport. So there's that too.
[1] strategywiki.org
by kube-system on 12/30/20, 4:04 AM
by billp3 on 12/30/20, 6:57 AM
His nameservers have been set to DigitalOcean servers for well over a year. A GoDaddy rep wouldn't be able to change MX records on those nameservers. They would have to change the nameservers on his domain to GoDaddy servers and then add new MX records. That's more than just a simple MX record change and seems more unlikely to me.
Perhaps his DigitalOcean account was compromised?
by nathanyz on 12/30/20, 4:22 AM
by idorosen on 12/30/20, 4:29 AM
by dpcan on 12/30/20, 6:42 AM
If you have someone who decides to cut even 1 corner, it can be devastating to a domain owner.
I have hundreds of clients who have used them, and I've never been on the phone with GoDaddy and had them do any less than tell me to bug off if I don't have a pin or get the 2-factor auth code to verify myself.
by tmk1108 on 12/30/20, 4:59 AM
by illiniboy on 12/30/20, 6:16 AM
by ketamine__ on 12/30/20, 4:09 AM