From owner-freebsd-isp Mon Jan 31 13: 7:47 2000 Delivered-To: freebsd-isp@freebsd.org Received: from altair.origenbio.com (altair.origenbio.com [216.30.62.130]) by hub.freebsd.org (Postfix) with ESMTP id 9E47A14CFD for ; Mon, 31 Jan 2000 13:07:40 -0800 (PST) (envelope-from dmartin@origen.com) Received: from origen.com (dubhe.origen [192.168.0.5]) by altair.origenbio.com (8.9.3/8.9.3) with ESMTP id PAA04506; Mon, 31 Jan 2000 15:05:11 -0600 (CST) (envelope-from dmartin@origen.com) Message-ID: <3895F8B4.3F4357C@origen.com> Date: Mon, 31 Jan 2000 15:03:48 -0600 From: Richard Martin X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: eddie@eaznet.com Cc: FreeBSD ISP Mailing List Subject: Re: Named Problem References: <3895EEBD.DA1B3220@eaznet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eddie, Sounds like you are not running named as root (which is a good thing) and/or your permissions are not set right or named.conf is wrong. First check thru your named.conf to make sure it is pointing to the db files in the right spot. You might also have someone else look at it in case of brain burn-thru resulting from staring at the screen for extended periods. DNS files in particular are that way. Check for who is running named, and make certain that this user (user 'bind' is probably already set up) has read and write privileges in the named db directory + all files therein Also 'bind' needs write permission on the named pid. If you are not running as root, you'll probably need to add options { pid-file "/var/named/named.pid" }; into the named.conf (bind V8) file. Create the /var/named directory and chown it to the named owner (bind or whoever) It is a very good idea not to run named as root, esp. with the recently publicized compromise in some versions of bind. If someone compromises named, then they only get to be 'bind', not root. Eddie - EAZNet Internet Services wrote: > > I have just installed FreeBSD 3.4-release. Everything seems to be > working properly, but I keep getting the following messages. Nmaed > seems to be working properly, I just would like to make sure I don't > have something set up incorrectly... > > Jan 31 10:53:45 amber named[289]: deleting interface [216.19.20.5].53 > Jan 31 10:53:45 amber named[289]: bind(dfd=20, [216.19.21.225].53): > Permission denied > Jan 31 10:53:45 amber named[289]: deleting interface [216.19.21.225].53 > Jan 31 10:53:45 amber named[289]: bind(dfd=20, [127.0.0.1].53): > Permission denied > Jan 31 10:53:45 amber named[289]: deleting interface [127.0.0.1].53 > Jan 31 10:53:45 amber named[289]: not listening on any interfaces > > I've checked permissions on everything I could think of and it all looks > ok. The web pages that operate at those addresses also seem to work ok. > > Any ideas? > > -- > Eddie Fry > eddie@eaznet.com > EAZNet Internet Services > 220 West 7th Street > Safford, AZ 85546 > (520) 348-0292 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message -- Richard Martin dmartin@origen.com OriGen Biomedical Tel: +1 512 474 7278 2525 Hartford Rd. Fax: +1 512 708 8522 Austin, TX 78703 http://www.cardiacdocs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message