From owner-freebsd-questions@FreeBSD.ORG Tue Sep 20 22:50:05 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 C614D16A420 for ; Tue, 20 Sep 2005 22:50:05 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id B41BD43D49 for ; Tue, 20 Sep 2005 22:50:03 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (patr530-a212.otenet.gr [212.205.215.212]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with ESMTP id j8KMnxeS012529; Wed, 21 Sep 2005 01:50:00 +0300 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j8KMncb4001659; Wed, 21 Sep 2005 01:49:38 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j8KMnb1b001658; Wed, 21 Sep 2005 01:49:37 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 21 Sep 2005 01:49:37 +0300 From: Giorgos Keramidas To: Lisa Casey Message-ID: <20050920224936.GA1646@flame.pc> References: <002601c5be2d$ddf19510$d580a23f@lisac> <43308733.3050303@azimainc.com> <004301c5be32$429b8da0$d580a23f@lisac> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004301c5be32$429b8da0$d580a23f@lisac> Cc: freebsd-questions@freebsd.org Subject: Re: Bind not starting on startup on new system 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, 20 Sep 2005 22:50:06 -0000 On 2005-09-20 18:25, Lisa Casey wrote: >>The only place it should be looking for it is in the path that >>named.conf is pointing to it. which if its the default is >>/etc/namedb/master. Is it there, or if not, where is named.conf >>looking for it. >> >>This seems obvious and i'm sure you've looked, but i hit a very >>similar issue a few days ago....and it was pointing to not path, >>which would be /etc/namedb. > > Thanks, that solved that problem. I had overlooked the obvious answer. > named.conf 's default directory is /etc/namedb but I had localhost.rev > in /etc/namedb/M (which is my master directory). I copied it to > /etc/namedb, that should fix that. Alternatively, you can fix your named.conf to point to the right place.