From owner-freebsd-questions Tue Apr 23 17:39:58 2002 Delivered-To: freebsd-questions@freebsd.org Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by hub.freebsd.org (Postfix) with ESMTP id 0181B37B41B for ; Tue, 23 Apr 2002 17:39:49 -0700 (PDT) Received: from wenk (H204.C233.tor.velocet.net [216.138.233.204]) by spitfire.velocet.net (Postfix) with SMTP id 57C03FB4598 for ; Tue, 23 Apr 2002 20:39:47 -0400 (EDT) Message-ID: <008f01c1eb42$1f301be0$b300a8c0@wenk> From: "Jeff Shevlen" To: References: Subject: [ SOLVED ] Re: bind 9.2.1rc2 chroot not starting Date: Tue, 23 Apr 2002 20:42:55 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 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 FTR, placing named.conf in the right directory helps! Freebsd defaults to /usr/local/etc/named.conf, so placing named.conf in, in my case, /path/to/root/usr/local/etc/, did the trick. This is useful information for those, like me, who ran the ISC version, which defaults to /path/to/root/etc/named.conf. > Hi, > > I can't seem to start bind in a chroot environment. I've checked file > permissions (750), and file ownerships (bind:bind). I've run > named-checkconf, and named-checkzone with success. I'm not sure > what's up. > > I ran bind 9.2 chroot with relative ease; and after rebuilding my box > and reinstalling the latest version, I can't seem to get it started. > I'm sure it's something simple I've missed, but I'm clued as to what > it is. > > # /usr/local/sbin/named -u bind -t /var/namedb/ > > [ Output from /var/log/messages: ] > Apr 24 03:05:19 ns1 named[212]: starting BIND 9.2.1rc2 -u bind -t > /var/namedb/ > Apr 24 03:05:20 ns1 named[212]: none:0: open: > /usr/local/etc/named.conf: file not found > Apr 24 03:05:20 ns1 named[212]: loading configuration: file not found > Apr 24 03:05:20 ns1 named[212]: exiting (due to fatal error) > > Line 2: "none:0" is not really telling me much, and I'm afraid I'm not > superslick with generating better debug output from the system, so I > haven't been able to gather much more information than this (apologies > for the lack thereof). > > I've got named.conf and named.root in /var/namedb/etc/ where they > should be. I've placed localtime in the root of chroot, /var/namedb/, > (this worked for me last time). My named.conf looks like this: > > [ START named.conf ] > options { > directory "/"; > pid-file "/named.pid"; > allow-query { any; }; > > forwarders { > xxx.xxx.xxx.xxx; > }; > > dump-file "/s/named_dump.db"; > }; > > zone "." { > type hint; > file "/etc/named.root"; > }; > > zone "0.0.127.IN-ADDR.ARPA" { > type master; > file "/etc/localhost.rev"; > notify no; > }; > > zone > "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT > " { > type master; > file "/etc/localhost.rev"; > }; > > zone "xxx.com" { > type master; > file "/m/xxx.com.db"; > allow-transfer { > xxx.xxx.xxx.xxx; > }; > }; > > controls { > inet * allow { any; } keys { "rndc-key"; }; > }; > > key "rndc-key" { > algorithm hmac-md5; > secret "xxxxxxxxxxxxxxxxxxxxxxxxxx"; > }; > > > logging { > > channel default_log { > file "/var/log/named.log" ; > severity info; > > print-category yes; > print-severity yes; > print-time yes; > }; > > channel default_debug { > file "/var/log/named.debug"; > severity dynamic; > print-category yes; > print-severity yes; > print-time yes; > }; > > channel default_stderr { > file ""; > severity info; > > print-category yes; > print-severity yes; > print-time yes; > }; > > channel null { > null; > }; > category "default" { default_log; default_debug; }; > category "general" { default_log; default_debug; }; > category "queries" { default_log; default_debug; }; > category "lame-servers" { default_debug; }; > category "security" { default_log; }; > category "xfer-in" { default_log; default_debug; }; ers > category "xfer-out" { default_log; default_debug; }; > category "notify" { default_log; default_debug; }; > }; > [ END named.conf ] > > Any help is appreciated. > > Jeff > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message