From owner-freebsd-questions@FreeBSD.ORG Tue Feb 27 17:10:25 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD78C16A402 for ; Tue, 27 Feb 2007 17:10:25 +0000 (UTC) (envelope-from admin2@enabled.com) Received: from typhoon.enabled.com (typhoon.enabled.com [216.218.220.21]) by mx1.freebsd.org (Postfix) with ESMTP id BBF4F13C441 for ; Tue, 27 Feb 2007 17:10:25 +0000 (UTC) (envelope-from admin2@enabled.com) Received: from [172.23.10.40] (nat-service4.juniper.net [66.129.225.151]) (authenticated bits=0) by typhoon.enabled.com (8.14.0/8.14.0) with ESMTP id l1RHApFM070831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 27 Feb 2007 09:10:51 -0800 (PST) (envelope-from admin2@enabled.com) Message-ID: <45E465FB.5010600@enabled.com> Date: Tue, 27 Feb 2007 09:10:19 -0800 From: Noah User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: User Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: named not starting on reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 17:10:25 -0000 Hi there, I am having troubles with named not starting on boot nor am I am able to start it manually. I thought I have my chrootdir set correctly. here are my settings in my rc.conf ----s nip ---- named_enable="YES" named_uid="bind" named_program="/usr/local/sbin/named" named_flags="-c /etc/namedb/named.conf" named_chrootdir="/var/named" ---- snip--- here are the /var/log/messages error: Feb 27 09:07:46 access2 named[2058]: /etc/named.conf:6: change directory to '/var/named/etc/namedb' failed: file not found Feb 27 09:07:46 access2 named[2058]: /etc/named.conf:6: parsing failed Feb 27 09:07:46 access2 named[2058]: loading configuration: file not found Feb 27 09:07:46 access2 named[2058]: exiting (due to fatal error)