From owner-freebsd-questions@FreeBSD.ORG Sun Nov 25 22:16:11 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 190AB16A418 for ; Sun, 25 Nov 2007 22:16:11 +0000 (UTC) (envelope-from bsd@todoo.biz) Received: from newmail.rmm.fr (newmail.rmm.fr [87.98.206.99]) by mx1.freebsd.org (Postfix) with ESMTP id C6EAA13C459 for ; Sun, 25 Nov 2007 22:16:10 +0000 (UTC) (envelope-from bsd@todoo.biz) Received: from localhost (localhost [127.0.0.1]) by newmail.rmm.fr (Postfix) with ESMTP id 04C2C28417; Sun, 25 Nov 2007 22:58:58 +0100 (CET) X-Virus-Scanned: amavisd-new 2.5.2 (20070627) at rmm.fr Received: from newmail.rmm.fr ([127.0.0.1]) by localhost (newmail.rmm.fr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ug9ZbmJiSBCN; Sun, 25 Nov 2007 22:58:57 +0100 (CET) Received: from [192.168.0.201] (me.todoo.biz [82.66.93.242]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by newmail.rmm.fr (Postfix) with ESMTP id 8DC2C28415; Sun, 25 Nov 2007 22:58:57 +0100 (CET) Message-Id: From: bsd To: Liste FreeBSD In-Reply-To: <6c21f52f0a910238c10964614d1f1102@prodigy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v915) Date: Sun, 25 Nov 2007 22:58:52 +0100 References: <6c21f52f0a910238c10964614d1f1102@prodigy.net> X-Mailer: Apple Mail (2.915) Cc: jekillen Subject: Re: named problems 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: Sun, 25 Nov 2007 22:16:11 -0000 Bind works perfectly out of the box on most FBSD recent versions. You should not move things out of the path they have been setup to. Specially on FBSD /etc is reserved for system files. By default bind is installed in /var/named and should be kept there. If I was you I would : 1. install the latest bind version from the port // 2. make sure you don't touch things unless absolutely necessary. 3. copy paste of modify the /var/named/etc/namedb/named.conf so that =20 It corresponds to your needs. 4. make sure the /etc/rc.conf has the correct "named" values. 5. start it with the /usr/local/etc/rc.d/ script for named // Been runing this one with 1000 zones as both masters and slave never =20 had any problem. If you have more issue could give you a help on debuging bind. My advice : STICK TO THE FBSD RULES AND PATH unless you perfectly know =20= what you are doing. Le 25 nov. 07 =E0 20:19, jekillen a =E9crit : > Hello; > I am having some named problems: > The daemon will not start and run on system startup. > There is plenty of info on problems when named > is running, but not when it will not start. > I did get it to start after boot with > #named (su to root without - option) > It started and ran as demonstrated > with ps -aux. But the listing was > just user (me as mortal user) and > named as process (not as a path > to an executable, as is normal > for other processes). > The console messages at start up > gives me configuration file not found > errors. The files are there. > /etc/namedb/named.conf, rndc.key > /etc/namedb is a link to /var/named/etc/namedb where the config > files are. It is set up to be a slave server > for four domains. > How can I go about debugging this > situation? > My suspicions are ownership and permissions > are wrong, but how, and how to fix; ?? > Thanks in advance > Jeff k =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF Gregober ---> PGP ID --> 0x1BA3C2FD bsd @at@ todoo.biz =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF P "Please consider your environmental responsibility before printing =20 this e-mail"