lame server error help

[awingnut]

I have 2 subnets for which I have created reverse lookup tables. One seems to be OK but the other gives me "lame server resolving ..." errors in my server log. I can't seem to see what is wrong with my entries to save my life. Can someone please tell me exactly what that error message means so I can fix the problem?

All my searches for this error message say it is an invalid DNS entry. I already know that but what makes the entry invalid and what entry is it (NS, PTR, SOA)?

TIA.

 

[elgrandeperro]

Look at the NS record for the zones and see if it groks with what you think is authoritative. Usually it is a zone that has a NS records, but that entry doesn't think it is authoritative for that zone.

gene

 

[awingnut]

Thanks for the reply. Everything looks copacetic. The 'lame' zone appears identical to the one that works (except the obvious differences). What makes it think it is not authoritive for that zone? I thought that was what the NS records mean.

 

[elgrandeperro]

Is it complaining about YOUR domain or others? A query
to your server to a domain (not yours) that isn't setup
correctly will generate the error.

I looked at my setup (bind) and we just:

logging {
category lame-servers { null; };

};

gene

 

[awingnut]

It is complaining about MY domain.

 

[elgrandeperro]

Yes, the NS records determine who is authoritative.

Run nslookup in interactive debug mode:

if your net is a.b.c.d and the failing server is at v.x.y.z
and the domain/network is e.f.g.in-addr.arpa.

nslookup - v.x.y.z
>set debug
>set type=ns
>e.f.g.in-addr.arpa.


dig has equivalent syntax ( but I use nslookup )

gene

 

[elgrandeperro]

If your DNS server is internet accessible, you could run it against

http://www.dnsreport.com,

using the e.f.g.in-addr.arpa. entry as input.

gene

 

[awingnut]

Thanks for the help. I'm don't know what I'm supposed to look for but there is nothing that looks like an error and all the information returned seems correct.