From owner-freebsd-questions@FreeBSD.ORG Tue Feb 27 17:21:22 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 A06D716A412 for ; Tue, 27 Feb 2007 17:21:22 +0000 (UTC) (envelope-from noah@juniper.net) Received: from kremlin.juniper.net (kremlin.juniper.net [207.17.137.120]) by mx1.freebsd.org (Postfix) with ESMTP id 51ED413C4C6 for ; Tue, 27 Feb 2007 17:21:22 +0000 (UTC) (envelope-from noah@juniper.net) Received: from unknown (HELO gamma.jnpr.net) ([172.24.245.25]) by kremlin.juniper.net with ESMTP; 27 Feb 2007 09:21:19 -0800 X-IronPort-AV: i="4.14,226,1170662400"; d="scan'208"; a="663207291:sNHT33587684" Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by gamma.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Feb 2007 09:21:19 -0800 Received: from [172.23.10.40] ([172.23.10.40]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Feb 2007 09:21:18 -0800 Message-ID: <45E4688D.6060101@juniper.net> Date: Tue, 27 Feb 2007 09:21:17 -0800 From: Noah Garrett Wallach User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Derek Ragona References: <45E38849.3090100@juniper.net> <6.0.0.22.2.20070227084100.02563750@mail.computinginnovations.com> In-Reply-To: <6.0.0.22.2.20070227084100.02563750@mail.computinginnovations.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Feb 2007 17:21:18.0968 (UTC) FILETIME=[B199AF80:01C75A93] Cc: User Questions Subject: Re: named not starting during boot 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:21:22 -0000 Hi there, I dont have a user name named. I have a user named bind. so bind is what I am going with. named_enable="YES" named_uid="bind" named_program="/usr/local/sbin/named" named_flags="-c /etc/namedb/named.conf" named_chrootdir="/var/named" cheers, Noah Derek Ragona wrote: > In the newer versions of bind you need to add to /etc/rc.conf: > named_uid="username" > you want to run named as. > > -Derek > > At 07:24 PM 2/26/2007, Noah Garrett Wallach wrote: >> Hi there, >> >> named is not starting when I reboot a FreeBSD 6.2 server and I cant >> figure out why. >> there are no error mesasges in /var/log/messages during the boot >> process. >> >> even when I manually start there are no error messages. >> >> # grep named /etc/rc.conf >> named_enable="YES" >> # pkg_info | grep bind >> bind9-9.3.4 Completely new version of the BIND DNS suite with >> updated D >> >> >> >> # grep BIND messages >> Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3 >> Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3 >> Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> # /etc/rc.d/named stop >> # /etc/rc.d/named start >> # grep BIND messages >> Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3 >> Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3 >> Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> Feb 26 17:23:46 access2 named[1005]: starting BIND 9.3.4 -c >> /etc/namedb/named.conf >> >> any clues please? >> >> Cheers, >> >> Noah >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> MailScanner thanks transtec Computers for their support. >> >