Apologies for the delay. Our records show that your domain is set to third party name servers. You would need to contact your web host provider to determine any issue with these servers. However, your current settings are showing as configured properly. When you had posted your question originally, you had only recently set the name servers. It may have just required more time for the update to take effect. Propagation can take up to 48 hours.
So are you going to come back and address the actual problem with Dynadot's own nameservers being down, which they are, regardless of whatever the original poster's situation is?
A lot of my websites whose DNS are hosted by dynadot are going down since the past 4 hours. The nameservers ns2.dynadot.com and ns1.dynadot.com are showing as "Nameserver is unreachable." on the DNS lookup for the domains. Is this a known issue?
I am also experiencing issues with Dynadot nameservers... my domains have been unstable for the last several hours. dig queries on ns1 and ns2 timeout most attempts, and my domains only intermittently resolve. This is a critical outage... Dynadot support support chat says "Chat Busy"...
Same here. I'm getting intermittent issues connecting to my server (External Server, Dynadot DNS). The domains/dns I have at other registrars connecting to servers in the same datacenter have no issues. Luckily these are just my test servers.
There is definitely an issue with Dynadot's DNS servers as far as I can see. If I do a DNS trace, I get the following results:
Sending request to "ns1.dynadot.com" (52.34.35.173)
Timeout waiting for response
Sending request to "ns1.dynadot.com" (52.36.53.176)
Timeout waiting for response
Sending request to "ns1.dynadot.com" (52.35.76.183)
Timeout waiting for response
Sending request to "ns1.dynadot.com" (52.26.28.15)
Timeout waiting for response
Can't really tell. It seems like they did so gradually. Some online checkers still show "DNS Lookup Error".
I now decided to switch to Google Cloud DNS https://cloud.google.com/dns/ as a permanent safer solution. It's also faster.
I'm guessing it can take up to 6 hours for the whole network to know that I've switched DNS. As I'm seeing 6hrs as TTL for SOA and NS records in Google Cloud DNS for example. "A" records are 5 min, and they used to be 5 min here for me, but I'm guessing that in this case NS and SOA are the ones that matter. Although, I don't really know. If anyone knows, please, tell.
It's far from being the first Dynadot's DNS downtime.. I should have known better than to move nameservers back to Dynadot some time ago. It takes them sometimes many many hours to fix such things (DDOS, I suppose?), so I'd recommend to switch ASAP and not wait for a fix.
Still, nameserver info seems to not get resolved in many places of the world by random.
For future, decided to use nameservers from multiple companies. And to transfer my main websites from Dynadot..
Edit: not a 100% certain that the info didn't update everywhere, though, as it might be that the online checker service I used show same for Google and Facebook which is certainly untrue.
Sorry for the delayed response. Over the weekend (8/24~/8/25), there was a DDoS attack on our DNS servers so domains using our DNS were affected. Our team made some updates to mitigate the attack as quickly as possible, however, there's been a propagation delay since then. DNS cache expired and sites got back online on Aug 28. We apologies sincerely for the downtime of your domains and the inconvenience caused.
Our sincere apologies for the delayed response here. our Dynadot Name Servers were unavailable due to a DDoS attack on our servers. While our on-call engineering teams worked diligently to bring our servers back up as quickly as possible there was a crucial communication protocol that was overlooked by the team. All our customers should have received our email communication about it last week. We truly apologize for this incident.
Nameservers down