From owner-freebsd-questions Sun Aug 29 18:38:58 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id B1ED21520A for ; Sun, 29 Aug 1999 18:38:52 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.8.8/8.8.8) id VAA23100; Sun, 29 Aug 1999 21:37:55 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199908300137.VAA23100@cc942873-a.ewndsr1.nj.home.com> Subject: Re: named "caching only" In-Reply-To: <37C99CCF.BAFB8F64@tinet.ie> from Gareth Gunning at "Aug 29, 99 09:49:19 pm" To: ggunning@tinet.ie (Gareth Gunning) Date: Sun, 29 Aug 1999 21:37:55 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gareth Gunning wrote, > I diced to implement a caching name sever on my 3.1 box. > > So I, edited resolve.conf so: > nameserver 127.0.0.1 > nameserver ISP 1'st > nameserver ISP 2'nd Looks good... > put: > named_enable="YES" > named_flags="-b /etc/namedb/named.boot" > in rc.conf Err... Starting to get suspicious... > ran /etc/namedb/make-localhost > this executed successfully > > and I made /etc/named.boot so that: > directory /etc/namedb > primary 0.0.127.in-addr.arpa localhost.rev > forwarders ISP 1'st ISP 2'nd Very suspicious. Doesn't 3.1 come with BIND 8.*mumble-mumble* which uses a 'named.conf' by default, whereas the 'named.boot' file is associated with the older version of BIND. This looks like the old 'boot' file format instead of the 'conf' format you would want. What messages does named leave in your /var/log/messages when it starts up? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message