My domain not working(ns7.zoneedit.com and ns12.zoneedit.com)

S

Shinoj

New Member
Hi,

My domain is not resolving - the issue started a couple of hours back :

> www.mymonedero.com.
Server: ns12.zoneedit.com
Address: 205.164.42.100

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to ns12.zoneedit.com timed-out
> server ns7.zoneedit.com.
Default Server: ns7.zoneedit.com
Address: 205.164.42.99

> www.mymonedero.com.
Server: ns7.zoneedit.com
Address: 205.164.42.99

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to ns7.zoneedit.com timed-out
>

Also, pelase check here :

http://network-tools.com/nslook/Def...&class=1&port=53&timeout=5000&go.x=23&go.y=13

Regards,
Shinoj.
 
Same problem here on ns7 and ns12. No response from either. Tried through various web resolvers and local networks.
 
Same here - ns7 and ns12 (as well as a couple others, I think) seem to be down. I just tried adding a couple of Zoneedit servers that still appear to be working but it will take a while to propagate out. I don't think they have any kind of emergency weekend support.
 
Same here, would appreciate a fix. I can't seem to find a way to change my name servers to ns8 or ns13, so I guess I'm stuck until zoneedit fixes?
 
I've been having the problem since last night from ns3.zoneedit.com and ns7.zoneedit.com. I just added ns13.zoneedit.com and ns8.zoneedit.com to my ns records on zoneedit and on my domain registrar. The domain is resolving now. Very strange. First problem in 12 years.
 
D Williamson said:
I've been having the problem since last night from ns3.zoneedit.com and ns7.zoneedit.com. I just added ns13.zoneedit.com and ns8.zoneedit.com to my ns records on zoneedit and on my domain registrar. The domain is resolving now. Very strange. First problem in 12 years.
Click to expand...

Same here...waiting for DNS to propagate so email and web sites are available again... pretty rough... at least 4 hours with no reply from zonedit.
 
Belatedly, we had an issue with the NYC POP that day and our monitors did not pick it up. We're reviewing the monitoring situation and will be faster on a remedy in the future. We're used to this type of outage being a DDoS attack and our monitors are heavily geared toward that. This incident wasn't a DDoS.

This brings another issue to light. The new nameserver architecture is split across four main DC's, NYC, Miami, Zurich and San Jose. Because the legacy domains were assigned their 2 nameservers in a pseudo-random fashion, there was no sure way to split the legacy ns1-ns17 nameservers around the 4 POP's in a way that guaranteed everybody would be in 2 distinct POP's - in this case ns7 and ns12 are both in the NYC POP.

We've populated NS8 with NS7's data, if you are currently delegated to NS7 and NS12 you could change NS7 and substitute NS8.zoneedit.com

That will put you in two separate POPs and you'd get more redundancy in a situation like this.

My lateness weighing in on this is because I've been out of the country on March Break (still am), sorry about that.
 
You must log in or register to reply here.
Back
Top