From owner-freebsd-questions Tue Jun 18 12:27:47 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA20571 for questions-outgoing; Tue, 18 Jun 1996 12:27:47 -0700 (PDT) Received: from Rigel.orionsys.com (root@rigel.orionsys.com [205.148.224.9]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA20558 for ; Tue, 18 Jun 1996 12:27:44 -0700 (PDT) Received: (from dbabler@localhost) by Rigel.orionsys.com (8.7.5/8.6.9) id MAA07090; Tue, 18 Jun 1996 12:25:20 -0700 (PDT) Date: Tue, 18 Jun 1996 12:25:20 -0700 (PDT) From: Dave Babler To: questions@FreeBSD.org Subject: Named learning disabilities? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Some time ago, I asked a question about "lame delegation" messages from named and received several answers that said, basically, they were beneign. I've begun to notice something else though... that contrary to what named is saying, it doesn't seem to be learning names: ---- Jun 18 11:04:18 Rigel named[67]: Lame server on '1.67.190.199.in-addr.arpa' (in '67.190.199.IN-ADDR.ARPA'?): [199.190.65.3].53 'NS.DX.NET': learnt (A=192.5.5.241,NS=128.8.10.90) Jun 18 11:18:53 Rigel named[67]: Lame server on '1.67.190.199.in-addr.arpa' (in '67.190.199.IN-ADDR.ARPA'?): [199.190.65.3].53 'NS.DX.NET': learnt (A=192.5.5.241,NS=128.8.10.90) Jun 18 11:23:08 Rigel named[67]: Lame server on '42.255.142.206.in-addr.arpa' (in '255.142.206.IN-ADDR.ARPA'?): [206.142.240.114].53 'ns1.cwix.net': learnt (A=205.136.1.33,NS=205.136.1.33) Jun 18 11:55:46 Rigel named[67]: Lame server on '1.67.190.199.in-addr.arpa' (in '67.190.199.IN-ADDR.ARPA'?): [199.190.65.3].53 'NS.DX.NET': learnt (A=192.5.5.241,NS=128.8.10.90) Jun 18 11:58:49 Rigel named[67]: Lame server on '42.255.142.206.in-addr.arpa' (in '255.142.206.IN-ADDR.ARPA'?): [206.142.240.114].53 'ns1.cwix.net': learnt (A=205.136.1.33,NS=205.136.1.33) ---- It seems to be saying that it is recording things, but runs into the same error/warning the very next time the path is looked up. Something misconfigured here? Where can I look? (my nameserver is provided by my ISP, which is, BTW, NS.DX.NET) -Dave