From owner-freebsd-questions Tue Aug 19 13:22:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02952 for questions-outgoing; Tue, 19 Aug 1997 13:22:11 -0700 (PDT) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02947 for ; Tue, 19 Aug 1997 13:22:07 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.8.6/8.7.3) id XAA08161; Tue, 19 Aug 1997 23:21:44 +0300 (EEST) Date: Tue, 19 Aug 1997 23:21:44 +0300 (EEST) Message-Id: <199708192021.XAA08161@silver.sms.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Petri Helenius To: Doug White Cc: Paul , questions@FreeBSD.ORG Subject: Re: lame server? In-Reply-To: References: <2.2.32.19970809061623.0074d0c0@mail.thsos.com> X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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