Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Aug 1997 23:21:44 +0300 (EEST)
From:      Petri Helenius <pete@sms.fi>
To:        Doug White <dwhite@resnet.uoregon.edu>
Cc:        Paul <Apollo@thsos.com>, questions@FreeBSD.ORG
Subject:   Re: lame server?
Message-ID:  <199708192021.XAA08161@silver.sms.fi>
In-Reply-To: <Pine.BSF.3.96.970809141511.6064J-100000@localhost>
References:  <2.2.32.19970809061623.0074d0c0@mail.thsos.com> <Pine.BSF.3.96.970809141511.6064J-100000@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
Doug White writes:
 > > 
 > > Aug  7 22:19:05 bob named[86]: Lame server on '109.115.98.206.in-addr.arpa' (in
 > > '115.98.206.IN-ADDR.ARPA'?): [204.70.57.242].53 'ns2.mci.net': learnt (A=192.5.5
 > > .241,NS=204.70.128.1)
 > > 

 > They're harmless.  As Named references nameservers, if it discovers a dead
 > server, it makes a notation and avoids the server for a while.  No further
 > action is needed on your part. 
 > 
This is not exactly correct. Lame server is a server that is referred
to by NS records but does not contain information for the zone the NS
records claimed and in order for the client to figure out the server
MUST NOT be dead.

So it's a configuration error at the referring server.

Pete



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708192021.XAA08161>