From owner-freebsd-questions Wed Oct 10 8: 9:39 2001 Delivered-To: freebsd-questions@freebsd.org Received: from quartz.bos.dyndns.org (quartz.bos.dyndns.org [66.37.218.198]) by hub.freebsd.org (Postfix) with ESMTP id CB0B037B426 for ; Wed, 10 Oct 2001 08:09:28 -0700 (PDT) Received: from localhost (twilde@localhost) by quartz.bos.dyndns.org (8.11.5/8.11.5) with ESMTP id f9AF9R003812 for ; Wed, 10 Oct 2001 11:09:27 -0400 (EDT) Date: Wed, 10 Oct 2001 11:09:27 -0400 (EDT) From: Tim Wilde X-X-Sender: To: Subject: Re: BIND9 In-Reply-To: <5.1.0.14.0.20011010110125.024c8d50@vmspop.rit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 10 Oct 2001, Matt Penna wrote: > Isn't it sufficient to simply specify the path to the new named binary by > setting the 'named_program' field in /etc/rc.conf? (E.g., > named_program="/usr/local/sbin/named") If not, I've learned something new, > yet again. That will probably work for booting, but you have to be careful when using bundled tools (dig, host, nslookup, nsupdate, etc). nsupdate in particular is one that's had some significant and important changes in BIND 9, so if you're doing dynamic updates, you're going to have to fiddle with your path, use absolute paths, or rename/remove the old binary (which is what I've done myself). Tim -- Tim Wilde twilde@dyndns.org Systems Administrator Dynamic DNS Network Services http://www.dyndns.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message