Lame & Missing nameservers problem

jca · May 27, 2007

Hi, a friend of mine registered a new domain and I offered him "free" hosting. Now, the domain is yet not workins, so I went and did a DNS Report and found the following:

http://www.dnsstuff.com/tools/dnsreport.ch?&domain=avalonlinkshell.com

I really don't know what is wrong, as I have .net,.org and .com domains currently working great in my server. Any light on what the problem might be please share.

Thanks

Jose

nobaloney · May 27, 2007

Let's start at the beginning...

First, did you register the nameservers ns1.kastillo.org and ns2.kastillo.org at the registrar where kastillo.org is registered? that's the first step.

Second, are the IP#s 72.232.84.162 and 72.232.84.163 the IP#s registered for those nameservers?

Third, are both the IP#s answering on your server?

Fourth, is there a zonefile for kastillo.org on your server?

Fifth, does that zonefile contain A record entries for both ns1.kastillo.org and for ns2.kastillo.org?

Sixth, is there a zonefile for avalonlinkshell.com on your server?

Seventh, does that zonefile contain NS record entries showing both ns1.kastillo.org and ns2.kastillo.org?

For all the no answers, fix it so the answers are yes, and then post any errors you're still getting.

Jeff

jca · May 27, 2007

jlasman said:
Let's start at the beginning...

First, did you register the nameservers ns1.kastillo.org and ns2.kastillo.org at the registrar where kastillo.org is registered? that's the first step.

Yes

jlasman said:
Second, are the IP#s 72.232.84.162 and 72.232.84.163 the IP#s registered for those nameservers?

Yes

jlasman said:
Third, are both the IP#s answering on your server?

Yes

jlasman said:
Fourth, is there a zonefile for kastillo.org on your server?

Yes

jlasman said:
Fifth, does that zonefile contain A record entries for both ns1.kastillo.org and for ns2.kastillo.org?

Yes

jlasman said:
Sixth, is there a zonefile for avalonlinkshell.com on your server?

I did create it, but I think here is the problem.

jlasman said:
Seventh, does that zonefile contain NS record entries showing both ns1.kastillo.org and ns2.kastillo.org?

Yes

jlasman said:
For all the no answers, fix it so the answers are yes, and then post any errors you're still getting.

Jeff

I have another host (kemazon.com) hosted exactly the same which is working.

http://www.dnsstuff.com/tools/dnsreport.ch?&domain=kemazon.com

So really I don't know what's wrong. I feel (since I don't have any evidence) that directadmin did not create the dns configuration for the domain.

Here is the dns detail view for the domain in Directadmin:
http://www.jocoque.net/avalonlinkshelldns.jpg

nobaloney · May 27, 2007

Unfortunately you updated the jpg with the wrong permissions; I can't see it

.

Jeff

jca · May 27, 2007

jlasman said:
Unfortunately you updated the jpg with the wrong permissions; I can't see it .

Jeff

Fixed... My mistake

LionRock · May 27, 2007

jlasman said:
Let's start at the beginning...
First, did you register the nameservers ns1.kastillo.org and ns2.kastillo.org at the registrar where kastillo.org is registered? that's the first step.

What do you mean register ? Where I define IP's for my DNS servers ? On my DA server or at my domain registrar where I have registered domain which one Im using with DA ?

Regards

jca · May 28, 2007

LionRock said:
What do you mean register ? Where I define IP's for my DNS servers ? On my DA server or at my domain registrar where I have registered domain which one Im using with DA ?

Regards

I think (or at least what I answered) that ns1 & ns2.kastillo.org are registered as nameservers with my domain registrer (where I bought it).

nobaloney · May 28, 2007

Log in through the shell, and run this command:

Code:

$ dig +trace avonlinkshell.com

You'll see the command stops at the gtld servers.

Then run:

Code:

$ dig @a.gtld-servers.net avalonlinkshell.com

You'll see that the gtld servers cannot get an answer from the nameservers.

Then run:

Code:

$ dig @a.gtld-servers.net ns1.kastillo.org

You'll see that the gtld servers cannot find the location of ns1.kastillo.org.

Then run:

Code:

$ dig @a.gtld-servers.net ns2.kastillo.org

You'll see that the gtld servers cannot find the location of ns2.kastillo.org.

You'll have to check with the registrar where kastillo.org was created; either you haven't properly registered the nameservers there, or they didn't properly register the nameservers with the root.

Jeff

DirectAdmin Support · May 28, 2007

This error is the key I think:

Code:

FAIL Lame nameservers ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame: 
72.232.84.162
72.232.84.163

So try:

Code:

dig avonlinkshell.com @127.0.0.1

If you get no IP, then either
- the domain isn't in the named.conf ..
- or there is a syntax error in the zone db file(check /var/log/messages after restarting named).
- or named is chrooted and not even checking your files: http://help.directadmin.com/item.php?id=128

John

jca · May 28, 2007

Thanks John, I ran the command you say and this is the answer I got:

Code:

# dig avonlinkshell.com @127.0.0.1

; <<>> DiG 9.2.4 <<>> avonlinkshell.com @127.0.0.1
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8785
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13

;; QUESTION SECTION:
;avonlinkshell.com.             IN      A

;; AUTHORITY SECTION:
.                       386657  IN      NS      E.ROOT-SERVERS.NET.
.                       386657  IN      NS      F.ROOT-SERVERS.NET.
.                       386657  IN      NS      G.ROOT-SERVERS.NET.
.                       386657  IN      NS      H.ROOT-SERVERS.NET.
.                       386657  IN      NS      I.ROOT-SERVERS.NET.
.                       386657  IN      NS      J.ROOT-SERVERS.NET.
.                       386657  IN      NS      K.ROOT-SERVERS.NET.
.                       386657  IN      NS      L.ROOT-SERVERS.NET.
.                       386657  IN      NS      M.ROOT-SERVERS.NET.
.                       386657  IN      NS      A.ROOT-SERVERS.NET.
.                       386657  IN      NS      B.ROOT-SERVERS.NET.
.                       386657  IN      NS      C.ROOT-SERVERS.NET.
.                       386657  IN      NS      D.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET.     473057  IN      A       198.41.0.4
B.ROOT-SERVERS.NET.     473057  IN      A       192.228.79.201
C.ROOT-SERVERS.NET.     473057  IN      A       192.33.4.12
D.ROOT-SERVERS.NET.     473057  IN      A       128.8.10.90
E.ROOT-SERVERS.NET.     473057  IN      A       192.203.230.10
F.ROOT-SERVERS.NET.     473057  IN      A       192.5.5.241
G.ROOT-SERVERS.NET.     473057  IN      A       192.112.36.4
H.ROOT-SERVERS.NET.     473057  IN      A       128.63.2.53
I.ROOT-SERVERS.NET.     473057  IN      A       192.36.148.17
J.ROOT-SERVERS.NET.     473057  IN      A       192.58.128.30
K.ROOT-SERVERS.NET.     473057  IN      A       193.0.14.129
L.ROOT-SERVERS.NET.     473057  IN      A       198.32.64.12
M.ROOT-SERVERS.NET.     473057  IN      A       202.12.27.33

;; Query time: 12 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 29 00:08:00 2007
;; MSG SIZE  rcvd: 454

And if I check kemazon.com (a working domain) this is what I get:

Code:

# dig kemazon.com @127.0.0.1

; <<>> DiG 9.2.4 <<>> kemazon.com @127.0.0.1
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54009
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;kemazon.com.                   IN      A

;; ANSWER SECTION:
kemazon.com.            14400   IN      A       72.232.84.162

;; AUTHORITY SECTION:
kemazon.com.            14400   IN      NS      ns1.kastillo.org.
kemazon.com.            14400   IN      NS      ns2.kastillo.org.

;; ADDITIONAL SECTION:
ns1.kastillo.org.       14400   IN      A       72.232.84.162
ns2.kastillo.org.       14400   IN      A       72.232.84.163

;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue May 29 00:09:33 2007
;; MSG SIZE  rcvd: 125

So something is bad with the named

DirectAdmin Support · May 29, 2007

1) restart named.
2) Check the /var/log/messages for any errors regarding named, and that db file.
3) check your named.conf (usually /etc/named.conf depending on OS) and compare with www.directadmin.com/named.conf. They should be similar for the most part (except for the domains you've added to your system, which should show up at the bottom of yours)

John

jca · May 29, 2007

I discovered that named puts more things in messages than what tail shows. It turns out it was chroot indeed, so I changed it according to the knowledge base and its working (resolving) the domain great now =) I'm waiting for my pc to work with the domain, else everything seems to be great.

Thanks

Jose

Lame & Missing nameservers problem

jca

Verified User

nobaloney

NoBaloney Internet Svcs - In Memoriam †

jca

Verified User

nobaloney

NoBaloney Internet Svcs - In Memoriam †

jca

Verified User

LionRock

Verified User

jca

Verified User

nobaloney

NoBaloney Internet Svcs - In Memoriam †

DirectAdmin Support

Administrator

jca

Verified User

DirectAdmin Support

Administrator

jca

Verified User