newbie on bind -lame server

[Chip Old]

On Thu, 29 Mar 2001, "Peña, Botp" wrote:

> I got a lot of lame server messages (below is a sample).
> Do I need to worry?

The problem isn't on your name servers, it's on name servers that are
supposed to be authoritative for domains but are not.  It's an indication
of incorrect delegation, and is unfortunately VERY common.

For example, from your log:

Mar 29 22:55:34 proxy named[344]: Lame server on 'ssc.edu' (in
'ssc.EDU'?): [205.166.226.38].53 'NS1.GRANITECANYON.COM'

This means your name server was trying to look up an address in ssc.edu.
It was told by the root name servers that ns1.granitecanyon.com is
authoritative for ssc.edu.  But when your name server queried
ns1.granitecanyon.com for the address, ns1.granitecanyon.com claimed not
to be authoritative for ssc.edu.

You can duplicate the sequence of queries with dig, nslookup, or whatever.
The root name servers show ns1.granitecanyon.com and ns2.granitecanyon.com
as authoritative for ssc.edu.  However if you query either of those, they
refer you back to the root name servers.

-- 
Chip Old (Francis E. Old)               E-Mail:  fold at bcpl.net
Manager, BCPL Network Services          Voice:   410-887-6180
Manager, BCPL.NET Internet Services     FAX:     410-887-2091
320 York Road
Towson, Maryland 21204 U.S.A.