From owner-freebsd-isp  Mon Feb 12 17: 9:19 2001
Delivered-To: freebsd-isp@freebsd.org
Received: from corey.datafast.net.au (corey.datafast.net.au [203.123.67.4])
	by hub.freebsd.org (Postfix) with SMTP id BE5E337B4EC
	for <freebsd-isp@freebsd.org>; Mon, 12 Feb 2001 17:09:16 -0800 (PST)
Received: (qmail 20259 invoked by uid 1000); 13 Feb 2001 01:09:14 -0000
From: "Corey Ralph" <corey.ralph@datafast.net.au>
Date: Tue, 13 Feb 2001 12:09:14 +1100
To: freebsd-isp@freebsd.org
Subject: Bind problems
Message-ID: <20010213120914.B99396@corey.datafast.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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