From owner-freebsd-questions Sun Jul 14 3:32: 4 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83E8A37B400 for ; Sun, 14 Jul 2002 03:32:00 -0700 (PDT) Received: from smtp.infracaninophile.co.uk (happy-idiot-talk.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2AEE43E3B for ; Sun, 14 Jul 2002 03:31:59 -0700 (PDT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost.infracaninophile.co.uk [IPv6:::1]) by smtp.infracaninophile.co.uk (8.12.5/8.12.5) with ESMTP id g6EAVsbo025693; Sun, 14 Jul 2002 11:31:54 +0100 (BST) (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost) by happy-idiot-talk.infracaninophile.co.uk (8.12.5/8.12.5/Submit) id g6EAVnb4025692; Sun, 14 Jul 2002 11:31:49 +0100 (BST) Date: Sun, 14 Jul 2002 11:31:49 +0100 From: Matthew Seaman To: Stacey Roberts Cc: FreeBSD-Questions Subject: Re: Cannot start bind in samdbox? Message-ID: <20020714103149.GB25158@happy-idiot-talk.infracaninophi> References: <1026640255.97896.9.camel@Demon.vickiandstacey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <1026640255.97896.9.camel@Demon.vickiandstacey.com> User-Agent: Mutt/1.5.1i 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 Sun, Jul 14, 2002 at 10:50:54AM +0100, Stacey Roberts wrote: > I'm trying to set named up on a box here, following the handbook as > well as FBSD Unleashed - but I cannot seem to get bind started and going > in a sandbox. >=20 > This is the error I keep getting: > # /usr/sbin/named -u bind -g bind -t /etc/namedb/s/ > can't open '/etc/namedb/named.conf' > # If your named.conf file is in the usual place, /etc/namedb/named.conf, then it's going to be inaccessible to named once it's performed the chroot(2) to /etc/named/s You need to replicate all of the file structure of /etc/namedb to your chroot directory. Try this: mkdir /var/named cd / tar -cf - etc/namedb | (cd /var/named ; tar -xvpf - ) Now when you start up named, use the command line: /usr/sbin/named -u bind -g bind -t /var/named named should then be happily reading the file /var/named/etc/namedb/named.conf thinking that it's actually /etc/named.conf Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Tel: +44 1628 476614 Marlow Fax: +44 0870 0522645 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message