resolved then unresolved

[blutek]

Yesterday I thought that all the domains on the server had resolved. They seemed to be working fine and a tracert from home showed them all pointing to my server. However today, 90% of the sites that worked yesterday arent working. My customers are experiencing similar problems too. A ping and tracert from dnsstuff.com show their domains pointing to the correct server but these issues are still occuring. can anyone see these?

http://technicalhelp.org

http://tnbp.org/

http://kapillar.net/

[wunderlin]

all came up fine- 1st one says under construction, but it came up.

[knightfoo]

Whoa .. you've got a mess here.

All of those domains appear to be registered to ns1.geodns.net and ns5.blutekhosting.com .. at least that is what the root nameservers think:

$ host -t ns technicalhelp.org tld1.ultradns.net
technicalhelp.org NS ns1.geodns.net
technicalhelp.org NS ns5.blutekhosting.com
$ host -t ns tnbp.org tld1.ultradns.net
tnbp.org NS ns5.blutekhosting.com
tnbp.org NS ns1.geodns.net
$ host -t ns kapillar.net a.gtld-servers.net
kapillar.net NS ns1.geodns.net
kapillar.net NS ns5.blutekhosting.com

However, ns5.blutekhosting.com does not seem to be registered as a nameserver, and more importantly it does not resolve through the proper channels. The only reason anyone can get an answer for the IP address of ns5.blutekhosting.com is due to the glue records maintained on the root nameservers. Looking at the blutekhosting.com domain is a little more interesting:

$ host -t ns blutekhosting.com a.gtld-servers.net
blutekhosting.com NS ns1.geodns.net
blutekhosting.com NS ns5.blutekhosting.com
$ host -t ns blutekhosting.com 69.44.57.171
blutekhosting.com NS ns2.blutekhosting.com
!!! blutekhosting.com NS host ns2.blutekhosting.com does not exist
blutekhosting.com NS ns1.blutekhosting.com
!!! blutekhosting.com NS host ns1.blutekhosting.com does not exist

The 69.44.57.171 IP is what I found in the glue records, and I assume this is your nameserver at ServerBeach. Your nameserver does not seem to agree with the root nameservers as to what the NS records for blutekhosting.com should be. Also, the NS records that your nameserver is providing point to hostnames which do not resolve through any means. Additionally, ns5.blutekhosting.com does not resolve from your nameserver either, which will cause random failures if a nameserver does not pay attention to the glue records from the root nameservers.

It looks like you are trying to use GeoDNS for slave nameservers, however you do not have any NS records for ns1.geodns.net or ns2.geodns.net in any of your zones. If the NS records are not present, your nameserver will not notfy the GeoDNS nameserver that a new zone is available, and the GeoDNS nameservers will ignore the zone if it appears they are not supposed to be handling it. Since GeoDNS nameservers are not transferring the zones, anyone who askes ns1.geodns.net for information about your zones will get a "lame server" error. Between the GeoDNS nameservers not having any information and ns5.blutekhosting.com only resolving part of the time, it is surprising that your domains resolve at all.

You need to decide exactly what you want to do with your nameservers before you can start to fix this situation. If you plan on using ServerBeach for slave nameservers, this is what you need to do:

1. Start with blutekhosting.com. You need to add an A record for ns5 and correct your NS records. The A record for ns5 should point to the IP address of your master nameserver. You should have the following NS records:

blutekhosting.com. IN NS ns5.blutekhosting.com
blutekhosting.com. IN NS ns1.geodns.net
blutekhosting.com. IN NS ns2.geodns.net

You also need to register ns5.blutekhosting.com as a nameserver .. you can do this with the same company that you registered the domain with, and it is normally free.

2. After that is done, make sure the information gets transferred to the GeoDNS nameservers. You can do this with a few queries from your server:

$ host -t ns blutekhosting.com ns5.blutekhosting.com
$ host -t ns blutekhosting.com ns1.geodns.net
$ host -t ns blutekhosting.com ns1.geodns.net

All of those queries should return the same information.

3. Now you can start working on your other domains. In the zones for your other domains you should have the same NS records that you entered in Step 1. After you have added the NS records, wait about 30 minutes for the zone transfers. Then check the NS records with the same method as Step 2. All of the records should match from all 3 nameservers.

4. Modify the nameservers with the registrar of your domains to point to the NS records you configured for those domains in Step 3. These modifications will take 24-48 hours, so do not expect instant changes.


If this is not what you want to do, check out the ServerBeach DNS HowTo thread in the HowTos forum.

-knightfoo

[blutek]

my ns5.blutekhosting.com nameserver is registered. I did this a few days ago.

Server Name: NS5.BLUTEKHOSTING.COM
IP Address: 69.44.57.171
Registrar: ENOM, INC.
Whois Server: whois.enom.com
Referral URL: http://www.enom.com

[blutek]

ok i think we got it working now. we had to put ns2.geodns.net in the setup and edit resolve.conf file. ns5.blutekhosting.com is registered fine though and points to my primary IP. (69.44.57.171)

I am just waiting for a second IP which I ordered a couple days ago and then we are gonna use our server for the primary and secondary nameservers. ie ns5.blutekhosting.com and ns6.blutekhosting.com. Is their gonna be any downtime for my customers when they switch our secondary nameserver from ns1.geodns.net to ns6.blutekhosting.com providing ns6.blutekhosting.com is already fully registered?