From owner-freebsd-security Thu Nov 11 11:42:28 1999 Delivered-To: freebsd-security@freebsd.org Received: from broccoli.graphics.cornell.edu (broccoli.graphics.cornell.edu [128.84.247.53]) by hub.freebsd.org (Postfix) with ESMTP id 8FC0614BF4 for ; Thu, 11 Nov 1999 11:42:10 -0800 (PST) (envelope-from mkc@Graphics.Cornell.EDU) Received: from graphics.cornell.edu by broccoli.graphics.cornell.edu with ESMTP (1.37.109.16/16.2) id AA298389320; Thu, 11 Nov 1999 14:42:00 -0500 Message-Id: <199911111942.AA298389320@broccoli.graphics.cornell.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dan Busarow Cc: matt , freebsd-security@FreeBSD.ORG Subject: Re: BIND NXT Bug Vulnerability In-Reply-To: Your message of "Thu, 11 Nov 1999 10:25:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Nov 1999 14:41:59 -0500 From: Mitch Collinsworth Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >bind builds perfectly from the source. > ># make stdlinks ># make clean ># make depend ># make all ># make install > >Done. It looks for named.conf in /etc instead of /etc/namedb but we >have named_flags available or you can just symlink /etc/namedb/named.conf >to /etc/named.conf which is what I do. > >You could also edit src/port/freebsd/Makefile.set and change >DESTETC to suit. Does DESTETC really control this? I was poking around looking for why it was looking in /etc rather than /etc/namedb and found this. Then I looked back at my 8.1.2 install which was from the ports and defaults to /etc/namedb and DESTETC was set to /etc there as well. Oddly, the default ISC install creates an /etc/namedb/named.conf, but the named it creates looks for /etc/named.conf. Weird. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message