From owner-freebsd-questions Sun Oct 3 15: 0:28 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 3B4FD14D6D for ; Sun, 3 Oct 1999 15:00:24 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.59]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA5A50; Mon, 4 Oct 1999 00:00:23 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA56869; Mon, 4 Oct 1999 00:00:40 +0200 (CEST) (envelope-from asmodai) Date: Mon, 4 Oct 1999 00:00:40 +0200 From: Jeroen Ruigrok/Asmodai To: Richard Morte Cc: "freebsd-questions@FreeBSD.ORG" Subject: Re: NSLINT and DNS configuration Message-ID: <19991004000040.F35757@daemon.ninth-circle.org> References: <37F74CBD.FE1EE27D@sinclairassoc.force9.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <37F74CBD.FE1EE27D@sinclairassoc.force9.co.uk> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On [19991003 14:41], Richard Morte (ric@sinclairassoc.force9.co.uk) wrote: >Has anyone used nslint to check the dns configuration? I just used it >and it reports the following: > > missing address A localhost. -> 127.0.0.1 > missing pointer PTR localhost.at.home -> 127.0.0.1 > 127.0.0.1 in use by localhost.at.home & localhost. Had this before. Definately a configuration error. named.conf: zone "1.0.0.127.IN-ADDR.ARPA" { type master; file "db.127.0.0.1"; }; db.127.0.0.1: 1 IN PTR localhost.blah.org. db.blah.org: localhost IN A 127.0.0.1 [blah.org is fictional and only used for the example] >I have checked the configuration and localhost does seem to be clearly >mapped to 127.0.0.1 and vice-versa. This seems to be confirmed by the >final line of nslint's output. > >Are these "errors" due to nslint's inability to find it's way through >the config files ( I shouldn't trust nslint's output) or has it found >something I should investigate further (nslint is good and I've clearly >got it wrong)? nslint is 99% of the time correct. Remember, computer lexers and parsers interpret configurations aimed for computers better than humans ;) HTH, -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Fame is the perfume of heroic deeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message