Problems with Name Servers.

[rocketcity]

I'm having problems getting name servers to resolve.

I did the initial setup of DA per the instructions on http://www.directadmin.com/newinstall.html After seting up the domain, adding additional IP addresses, creating the name servers via the "Reseller" link and then verified the name servers in the "Admin" section.

name servers are ns1 & ns2 .rocketcityhosting.com
IP are 67.132.246.2 & .3

I then register the name servers with the current registrar. I have verified that both name servers have propogated the root servers and the both have the correct IP addresses. **( I have not pointed the domain to the name server yet )** It has been 5 days since name servers were registered.

I have checked both in DA "Service Monitor" & via ssh to the server that "named" is running.

(from server (ps -aux))
"named 3745 0.0 0.3 46924 3408 ? Ssl 13:52 0:00 named -u named"

(from DA)
DirectAdmin 1.24.4 Running
Named 9.2.5 Running

When I go to DNS Report everything pass's except for "NS" see link: http://www.dnsreport.com/tools/dnsreport.ch?domain=rocketcityhosting.com

I can do a dig @67.132.246.4 & get a return on the domain "rocketcityhosting.com" (only zone file currently setup), along with the name server info.

I am running fedora core 3 with the latest updates for that version.

Any help would be much appreciated.

 

[nobaloney]

Huntsville, eh? I was expecting Cape Canaveral .

It sure doesn't look like your nameservers are registered.

Why do I say that?

When I do a dig as follows:

dig @e.gtld-servers.net ns1.rocketcityhosting.com

I don't get any A records, but only get NS records as the authority:

rocketcityhosting.com. 172800 IN NS dns1.peel2.com.
rocketcityhosting.com. 172800 IN NS dns2.peel2.com.

Which is exactly what I get when I do a dig on rocketcityhosting.com.

Which means to me that the gtld servers cannot find your nameservers and want me to query dns1.peel2.com, and dns2.peel2.com.

(If they were registered properly, then the gtld servers should have been able to find A records for them.)

But when I query dns1.peel2.com and dns2.peel2.com, dig tells me it can't find the A records for the peel2.com nameservers.

First step would be to check with your registrar and make sure the nameservers are registered.

Jeff

 

[rocketcity]

odd, of course this is not a dig but when I do a whois for ns1 or ns2 for rocketcityhosting.com against whois.internic.net, I get the following response.

Server Name: NS1.ROCKETCITYHOSTING.COM
IP Address: 67.132.246.2
Registrar: ENOM, INC.
Whois Server: whois.enom.com
Referral URL: http://www.enom.com

not fulling understanding all that is happening in the back ground. It seems odd that Internic & Verisign (if they are not the same) show the same info. In the mean time, I will have to try & contact the registrar in the morning to see what they can tell me.

Thanks for your response.