DNS records lost on ns1.geodns.net & ns2.geodns.net

[vabtz]

All DNS records which I have set to use my server ( My_ip removed ) as the master DNS server have failed to resolve.

Some notes:

-> All DNS records have ns1.geodns.net & ns2.geodns.net listed in the NS records.

-> the host command does not show the domains are in the nameserver records of ns1.geodns.net & ns2.geodns.net.

-> host command shows that the domains are correctly pointed to my ip via my local dns

-> Problem first was noticed today @ 9:00 pm EST

-> DNS Tool shows that the zones are configured to use my server ( **Server Ip removed **) as the master

-> Zone files look fine to me...

:confused:

any one have any ideas ?

[Monsoonstorm]

I don't know but there is a problem with my servers DNS. Domain names stoped resolving at about the same time.

[Brendan]

I have the exact same problem. I have ns1 and ns2.geodns.net setup to slave to my dns, but both of those machines have lost the records for my domains.

[Brendan]

burned a ticket on this. I'll let you know what I hear back...

[vabtz]

Originally posted by Brendan
burned a ticket on this. I'll let you know what I hear back...

Same here....

I got a email back that looked like it was a automated response:

Basically it said it queried ns1 and found that the zone was AFU and told me to fix it. Double checked my zone files and they were fine, bind was up, and no error messages to be found. So replied they need to check further.

[vabtz]

For the record I am using Cpanel and we had a recent layer 2 upgrade is any one else here using Cpanel ?

More to the point is any one having this issue not using Cpanel ?

[Brendan]

I have Plesk on both of my servers that affected by this problem.

[knightfoo]

If you submit tickets under the category "ServerBeach DNS Tool" then it should not cost you a troubleshooting ticket. If you did use a troubleshooting ticket and the problem is on our end, then the ticket will be refunded.

As for this particular issue, we are still investigating. As far as I can tell, the errors started around 4-5PM today and only the slave zones are being affected .. all zones configured as "master" in the DNS Tool are still working properly. I'm afraid I can't provide much more detail right now, but I have notified the appropriate people to have this taken care of.

-knightfoo

[Monsoonstorm]

Looks like my "slaves" all turned to "master" in the DNS tool. I'm glad I had only one. My site is not resolving but all my client site are:).

[mroy]

I'm glad I'm not the only one with this problem. I noticed it at 3:30 MST. There's only one domain that resolves at the moment. When I initially set the server up it was the only domain that the geodns.net slaves wouldn't pick up for over a week, so I pointed it to my server for dns resolution. I should've done that for all the others before today and they would at least be resolvable now.

[knightfoo]

Fixed .. I think. I hope. :) It looks like all of the slave zones are working now, though I haven't had the chance to verify the several thousand slave zones that we are maintaining.

-knightfoo

[mroy]

Woohoo!!! My sites are back!

[knightfoo]

I just did a count and all of the zones are being loaded into both nameservers properly. At this time it is safe to say that any DNS resolution problems you may be experiencing are not a result of the GeoDNS nameservers misbehaving.

-knightfoo

[elderban]

Well, I have 5 domains on one of my servers. Three of them are using the Geo DNS servers, and the other two are using an outsourced DNS server.

The three on the geodns servers are not resolving, however the ones that are on the outsourced DNS server are working fine.

So, I'd say it's defenitely a geodns problem.

[Jeanna]

None of the sites on either of my servers is resolving. All use GEODNS. We only use the SB domain tool.

[TheInitiative]

My server is hosting just one domain, so I'm not using slaves, control panels, etc. Just using ns1.geodns.net and ns2.geodns.net. My site was resolving until atleast midnite eastern time last nite, now it's not. It's very frustrating that there is no support phone number. I guess I'll submit a ticket and wait until somebody feels like helping me.

[Shaned]

Over 90% of my domains are not working/resolving only use sb dns tool also..The ones that are working are having email issues for the most part..slow or not going through..
The domains that are working are very slow in responding

[Jeanna]

Both of my servers just started resolving again.

[Shaned]

Yep..Mine too it seems now

[TheInitiative]

I'm good now, too.

[elderban]

Well...now my other server is not resolving.

Things aren't looking good for SB right now.

When I brought my sites here, there was a lot of problems with lost packets, routing problems, and pages took forever to load.

Now, none of my sites are resolving...

:(

[knightfoo]

All of the master and slave zones are loading properly. However, there are 226 slave zones on our DNS servers which are not transferring because the master nameserver is unreachable (7 unreachable) or the master nameserver is refusing transfers (219 refusing transfers). When configuring slave zones in the DNS Tool, you need to make sure the master nameserver is accessible to and will allow transfers from the following IP addresses:

66.139.72.14 (ns1.geodns.net)
66.139.72.20 (ns2.geodns.net)

If you are experiencing problems with your slave domains not working, please make sure you do not have any firewalls which may be blocking the above IP addresses. You should also check your logs to see if there have been transfer attempts that were denied. We are building a list of slave zones which are failing and will be contacting the customers responsible for those zones on Monday (via the ticketing system). Please do not submit tickets regarding this issue until you have verified that the configuration on your own server is correct.

-knightfoo

[elderban]

I'm using geodns for both my master and slave.

But, all of my sites seem to be working now.

[knightfoo]

Originally posted by elderban
I'm using geodns for both my master and slave.

But, all of my sites seem to be working now.

The notice above only applies to zones which are configured as "slave" in the DNS Tool. All domains configured as "master" never stopped working. There may have been a problem with your local resolver, because even if ns1.geodns.net and ns2.geodns.net went down it would take 24 hours for the cache to expire from your local nameserver. Unless of course you are using ns1.geodns.net and ns2.geodns.net as your resolvers, in which case I will have to flog you with my hardback copy of DNS & Bind. :)

-knightfoo

[elderban]

Welp, you may as well start flogging... :rolleyes:

I use webmin as my control panel, and haven't quite mastered setting up a DNS through it, nor have I mastered DNS's at all. :)

[knightfoo]

Originally posted by elderban
Welp, you may as well start flogging... :rolleyes:

I use webmin as my control panel, and haven't quite mastered setting up a DNS through it, nor have I mastered DNS's at all. :)

If your server is in San Antonio, the following nameservers should be in your /etc/resolv.conf:

66.139.72.6
66.139.72.22

If your server is in Virginia, you should use these nameservers in /etc/resolv.conf:

69.44.56.86
69.44.56.102

San Antonio servers have a 66.* IP address and Virginia servers have a 69.* IP address .. the nameservers will not work across datacenters, so make sure you pick the right one.

-knightfoo

[elderban]

Yeah...I've got that set up. They're set up as:

nameserver 66.139.72.6
nameserver 66.139.72.22
nameserver 66.139.72.14
nameserver 66.139.72.20

[knightfoo]

Originally posted by elderban
Yeah...I've got that set up. They're set up as:

nameserver 66.139.72.6
nameserver 66.139.72.22
nameserver 66.139.72.14
nameserver 66.139.72.20

You need to drop the last 2, those are the GeoDNS nameservers.

-knightfoo