Forum

Ultra40:~$ dig @ns2.dynadot.com dynadot.com

; <<>> DiG 9.16.1-Ubuntu <<>> @ns2.dynadot.com dynadot.com
; (4 servers found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Ultra40:~$ dig @ns1.dynadot.com dynadot.com

; <<>> DiG 9.16.1-Ubuntu <<>> @ns1.dynadot.com dynadot.com
; (4 servers found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Alright just moved my last domain here to namecheap, sad, I was a customer for a long time and had always recommended your services. Hope the money you saved not covering nights and weekends for outage support is worth the bad reputation you are earning. It was nice being a customer when you used to care.

Just a heads up for anyone facing this I just had to rush over one of my main domains to Digital Oceans Name Servers, you could do the same thing with AWS Route53, you will just have to port your DNS records over and point your NS records at Route53/DigitalOcean/Azure/GCP/Whatever is more reliable.

I am going to have to think about what this means for me as a customer in keeping Dynadot, what if this was a domain hijacking or security issue? There is really not even a freaking batphone number for emergencies? Been a customer for a long time, just blown away this is how they are doing business.

Not sure what it takes to let someone know, since I cant open a ticket, cant chat with support and cant call anyone?