Lame servers

[McNutt, Justin M.]

Hello all,

I am getting a very large number of 'lame server' errors in my server logs
(other people's servers, thank goodness).  However, when I got a copy of
'lamers' and ran it against my log files, well first of all it never
actually sends any mail, but secondly, for the vast majority of the entries
is says something like this:

-> 192.67.14.16 may be a lame delegation for 0.104.198.in-addr.arpa
   Looking up the hostmaster for 0.104.198.in-addr.arpa
   Hostmaster is hostmaster at kcls.org
   Is 192.67.14.16 listed as a NS for 0.104.198.in-addr.arpa?  No, skipping.

The log entry that generated this response is:

Nov  9 01:47:16 noc.missouri.edu named[28133]: Lame server on
'100.0.104.198.in-addr.arpa' (in '0.104.198.in-addr.arpa'?):
[192.67.14.16].53 't.ns.verio.net'

I also note that there are a great many lame server log entries for
192.67.14.16, but I digress...

The code in the 'lamers' script itself suggests that these may be 'spurious'
lame server delegations.  Is this what happens when a DNS server is no
longer authoritative for a zone, but my local name server still has old
authority information cached, or is there a real problem somewhere?  Further
dig-ing suggests that this is the case.

If not, what else should I be looking for?

If so, does this mean that due to the rather dynamic nature of the 'Net
lately that I'm doomed to see a zillion lame server messages in my logs all
the time?

Thanks!

Justin McNutt
Network Systems Analyst - Expert
DNPS, Mizzou Telecom
(573) 882-5183

"It's a kind of magic."

"There can be only one!"