From owner-freebsd-questions@FreeBSD.ORG Tue Feb 27 01:52:55 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 6F52216A401 for ; Tue, 27 Feb 2007 01:52:55 +0000 (UTC) (envelope-from noah@juniper.net) Received: from borg.juniper.net (borg.juniper.net [207.17.137.119]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF7613C478 for ; Tue, 27 Feb 2007 01:52:55 +0000 (UTC) (envelope-from noah@juniper.net) Received: from unknown (HELO gamma.jnpr.net) ([172.24.245.25]) by borg.juniper.net with ESMTP; 26 Feb 2007 17:24:30 -0800 X-IronPort-AV: i="4.14,222,1170662400"; d="scan'208"; a="682288110:sNHT31434956" Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by gamma.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Feb 2007 17:24:30 -0800 Received: from [172.23.10.40] ([172.23.10.40]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Feb 2007 17:24:26 -0800 Message-ID: <45E38849.3090100@juniper.net> Date: Mon, 26 Feb 2007 17:24:25 -0800 From: Noah Garrett Wallach 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 X-OriginalArrivalTime: 27 Feb 2007 01:24:26.0320 (UTC) FILETIME=[04FED500:01C75A0E] Subject: 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 01:52:55 -0000 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