From owner-freebsd-questions Sun Jul 14 10:18:47 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 6A49737B400 for ; Sun, 14 Jul 2002 10:18:42 -0700 (PDT) Received: from jeeves.velosystems.net (wsip68-15-85-238.oc.oc.cox.net [68.15.85.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6875443E65 for ; Sun, 14 Jul 2002 10:18:41 -0700 (PDT) (envelope-from steve@velosystems.net) Received: from localhost (localhost.velosystems.net [127.0.0.1]) by jeeves.velosystems.net (Postfix) with ESMTP id BB683A7B6; Sun, 14 Jul 2002 10:18:40 -0700 (PDT) Received: from daemon.velosystems.net (daemon.velosystems.net [192.168.1.11]) by jeeves.velosystems.net (Postfix) with ESMTP id 1D12AA524; Sun, 14 Jul 2002 10:18:33 -0700 (PDT) Subject: RE: Cannot start bind in samdbox? From: Steve Wingate To: Steve Wingate Cc: Lars Wittebrood , sroberts@dsl.pipex.com, FreeBSD-Questions Mailinglist In-Reply-To: <1026666556.77988.7.camel@daemon.velosystems.net> References: <2578F22C7A5515449899AF290E2D48321F69@lotus.ad.socruel.org> <1026666556.77988.7.camel@daemon.velosystems.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 14 Jul 2002 10:18:27 -0700 Message-Id: <1026667113.77988.13.camel@daemon.velosystems.net> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS perl-11 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, 2002-07-14 at 10:09, Steve Wingate wrote: > On Sun, 2002-07-14 at 03:11, Lars Wittebrood wrote: > > Stacey, > > > > Do you have the directory structure right in your sandbox? I have bind > > chrooted in /chroot/bind and my command to start it there is : > > > > /chroot/bind/named -u bind -g bind -t /chroot/bind -d 1 > > > > You have "-t /etc/namedb/s/" so you have to have the named binary and > > /etc/namedb/named.conf within the /etc/namedb/s directory structure. > > > > See http://www.psionic.com/papers/bindbsd.html for a HOW-TO. > > > > You don't have to move the binary to the chroot. You have to move the > conf file, which it's telling you in your error message. > > > # /usr/sbin/named -u bind -g bind -t /etc/namedb/s/ > can't open '/etc/namedb/named.conf' > > As soon as the "-t /etc/namedb/s/" is executed, bind switches to that > directory THEN begins looking for the conf files. It has NO ACCESS to > anything outside of that directory. The way you're entering that > command, your named.conf file would have to be in > /etc/namedb/s/etc/namedb/named.conf. > > I use the following /etc/rc.conf with BIND 9.x and it works fine. This > way BIND looks in it's current directory for the conf file, which would > be '/var/named'. > > named_enable="YES" > named_program="/usr/local/sbin/named" > named_flags="-t /var/named -u bind -c named.conf" > I should mention I'm running BIND chrooted, not jailed. However the Handbook instructions on running it in a jail do work perfectly if you follow them perfectly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message