DNS Down
- Thread starter asad78611
- Start date
Dave Burton
New Member
ns13.zoneedit.com, ns8.zoneedit.com, and ns1.zoneedit.com nameservers are all DOWN or malfunctioning! ns13 and ns8 are the two nameservers for one of my domains, so this outage has taken that domain down.
I'm a paid customer so I submitted a ticket:
"Some of your servers seem to be down, including ns13=45.76.95.243 and ns8=45.76.95.243 (BOTH of the nameservers for my geeksalive.com domain), and ns1=45.77.82.193 (one of the two for my burtonsys.com domain). My geeksalive.com site is down because of this!"
I got an automated email seven minutes ago, but no other response, so far.
I'm a paid customer so I submitted a ticket:
"Some of your servers seem to be down, including ns13=45.76.95.243 and ns8=45.76.95.243 (BOTH of the nameservers for my geeksalive.com domain), and ns1=45.77.82.193 (one of the two for my burtonsys.com domain). My geeksalive.com site is down because of this!"
I got an automated email seven minutes ago, but no other response, so far.
Dave Burton
New Member
Hey, I just noticed that ns8 and ns13 resolve to the SAME server.
Also, dns1.zoneedit.com = ns1.zoneedit.com = 45.77.82.193
But dns2.zoneedit.com = 45.79.110.158 which is not the same as ns2.zoneedit.com = 50.116.49.173 (which is still working, and answers DNS requests and pings)
Also, dns1.zoneedit.com = ns1.zoneedit.com = 45.77.82.193
But dns2.zoneedit.com = 45.79.110.158 which is not the same as ns2.zoneedit.com = 50.116.49.173 (which is still working, and answers DNS requests and pings)
Dave Burton
New Member
My sealevel.info web site is now also down, for the same reason -- its two nameservers are t2.zoneedit.com and ns13.zoneedit.com, which BOTH resolve to the SAME nameserver, 45.76.95.243, which is down.
Dave Burton
New Member
Still no response to my "Urgent" support ticket. However, ns1 is back up, and I experimentally determined that ns1.zoneedit.com=45.77.82.193 is correctly serving up my geeksalive.com and sealevel.info domain info, so I added that nameserver at the registrars, and my sites are back up.
Last edited:
Dave Burton
New Member
ns8 / ns13 / ts2 (45.76.95.243) is now answering pings, though it is still not serving up DNS info.
Dave Burton
New Member
Thanks for the update, El.
I did nslookups on a lot of zoneedit nameserver names, and found a LOT of synonyms:
ns1 is now 45.77.82.193 (same as ns9, t1 and dns1)
ns2 is now 50.116.49.173
ns3 is now 128.199.163.75
ns4 is now 139.162.196.199 (same as ns7)
ns5 is now 159.203.1.67
ns6 is now 45.77.23.227
ns7 is now 139.162.196.199 (same as ns4)
ns8 is now 45.76.95.243 (same as ns13 and t2)
ns9 is now 45.77.82.193 (same as ns1, t1, and dns1)
ns10 is now 45.79.110.158
ns11 is now 37.139.13.54
ns12 is now 139.162.196.199 (same as ns7)
ns13 is now 45.76.95.243 (same as ns8 and t2)
t1 is now 45.77.82.193 (same as ns1, ns9 and dns1)
t2 is now 45.76.95.243 (same as ns 8 & ns13)
dns1 is now 45.77.82.193 (same as ns1, ns9 and t1)
dns2 is now 45.79.110.158 (same as ns10)
The key to keeping your customers' sites from going down is to make sure that they all have two or more DIFFERENT nameservers. Two of my sites went down because, although I thought they had two nameservers, they actually just had two synonyms for the SAME single nameserver.
If you're going to have several names be synonyms for the same server, you need to search your database for customers which have been given those names for nameservers for their domains, and tell them what new nameservers they should use, to maintain redundancy of nameservers. Can you please do that, El.?
I did nslookups on a lot of zoneedit nameserver names, and found a LOT of synonyms:
ns1 is now 45.77.82.193 (same as ns9, t1 and dns1)
ns2 is now 50.116.49.173
ns3 is now 128.199.163.75
ns4 is now 139.162.196.199 (same as ns7)
ns5 is now 159.203.1.67
ns6 is now 45.77.23.227
ns7 is now 139.162.196.199 (same as ns4)
ns8 is now 45.76.95.243 (same as ns13 and t2)
ns9 is now 45.77.82.193 (same as ns1, t1, and dns1)
ns10 is now 45.79.110.158
ns11 is now 37.139.13.54
ns12 is now 139.162.196.199 (same as ns7)
ns13 is now 45.76.95.243 (same as ns8 and t2)
t1 is now 45.77.82.193 (same as ns1, ns9 and dns1)
t2 is now 45.76.95.243 (same as ns 8 & ns13)
dns1 is now 45.77.82.193 (same as ns1, ns9 and t1)
dns2 is now 45.79.110.158 (same as ns10)
The key to keeping your customers' sites from going down is to make sure that they all have two or more DIFFERENT nameservers. Two of my sites went down because, although I thought they had two nameservers, they actually just had two synonyms for the SAME single nameserver.
If you're going to have several names be synonyms for the same server, you need to search your database for customers which have been given those names for nameservers for their domains, and tell them what new nameservers they should use, to maintain redundancy of nameservers. Can you please do that, El.?
Hi Dave.
When we took over Zoneedit, there were many things which we've had to fix which were in a bad state of repair.
The current naming conventions are mostly what they were set to from years ago, however we've been slowly changing the namespace of the Zoneedit nameservers to fix this issue.
The problem is that we've had to do this without breaking compatibility with customers existing setups and it has been challenging.
We do plan on solving this, however I do not have an ETA.
When we took over Zoneedit, there were many things which we've had to fix which were in a bad state of repair.
The current naming conventions are mostly what they were set to from years ago, however we've been slowly changing the namespace of the Zoneedit nameservers to fix this issue.
The problem is that we've had to do this without breaking compatibility with customers existing setups and it has been challenging.
We do plan on solving this, however I do not have an ETA.
Dave Burton
New Member
Hi sproskin & El.
ns1 through ns8, and ns11, all seem to work, at the moment.
ns9, 12 & 13 are the same as ns1, 7 & 8, respectively.
ns10 / dns2 (45.79.110.158) is down.
It used to be that ZoneEdit assigned two specific nameservers for each domain name. (We could pay extra for additional nameservers.) But it appears that, currently, all nine unique servers return correct info for my domains.
So, are they all equivalent, now? Should I just add a few more of them in the registrar's records for each of my domains, for redundancy?
ns1 through ns8, and ns11, all seem to work, at the moment.
ns9, 12 & 13 are the same as ns1, 7 & 8, respectively.
ns10 / dns2 (45.79.110.158) is down.
It used to be that ZoneEdit assigned two specific nameservers for each domain name. (We could pay extra for additional nameservers.) But it appears that, currently, all nine unique servers return correct info for my domains.
So, are they all equivalent, now? Should I just add a few more of them in the registrar's records for each of my domains, for redundancy?
Dave Burton
New Member
sproskin & El., will you please answer that question?