From owner-freebsd-isp  Mon Feb 12 17:43: 8 2001
Delivered-To: freebsd-isp@freebsd.org
Received: from mail.tcworks.net (mail.tcworks.net [216.61.218.4])
	by hub.freebsd.org (Postfix) with ESMTP id 0052137B491
	for <freebsd-isp@FreeBSD.ORG>; Mon, 12 Feb 2001 17:43:05 -0800 (PST)
Received: from tcworks.net (creed.tcworks.net [216.61.218.6])
	by mail.tcworks.net (8.10.2/8.10.2) with ESMTP id f1D1dCT92688;
	Mon, 12 Feb 2001 19:39:12 -0600 (CST)
Message-ID: <3A889199.D8342910@tcworks.net>
Date: Mon, 12 Feb 2001 19:44:57 -0600
From: Chris Cook <ccook@tcworks.net>
X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mitch Collinsworth <mitch@ccmr.cornell.edu>
Cc: Corey Ralph <corey.ralph@datafast.net.au>,
	freebsd-isp@FreeBSD.ORG
Subject: Re: Bind problems
References: <Pine.LNX.4.10.10102122019130.22516-100000@ruby.ccmr.cornell.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I had a similar problem after upgrading via the ISC source... it wanted
/etc/named.conf instead of /etc/namedb/named.conf.  I had to run named
like so:  "/usr/sbin/named -c /etc/namedb/named.conf -u bind -g bind" .  

- Chris


Mitch Collinsworth wrote:
> 
> Did you install from the freebsd port or from the ISC source?
> Was your previous install from the same source?  They (last time
> I looked, admittedly a few months back) look in different places
> for their configuration file.  Maybe you're not reading the .conf
> (or .boot) file you think you are?
> 
> -Mitch
> 
> On Tue, 13 Feb 2001, Corey Ralph wrote:
> 
> > Hi all,
> >
> > I am having a problem with one of my nameservers since upgrading bind
> > after the advisory last week.
> >
> > It runs slave for all our zones.  It has stopped updating its zone
> > files.  Doing it manually using /usr/libexec/named-xfer works fine.  I
> > tried setting the path to it in the options just incase it was looking
> > in the wrong place, that didn't help.  There are no relevant messages in
> > the logs.
> >
> > Has anybody seen this before?
> >
> > Also, I am considering switching to djbdns to avoid this constant
> > upgrading.  Any experiences with this?  Would bind 9 be a better choice?
> >
> > Cheers,
> > Corey Ralph
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-isp" in the body of the message
> >
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message