From owner-freebsd-isp Mon Feb 19 14:38:25 2001 Delivered-To: freebsd-isp@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 4056237B401 for ; Mon, 19 Feb 2001 14:38:23 -0800 (PST) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA52441; Mon, 19 Feb 2001 14:38:18 -0800 (PST) (envelope-from DougB@gorean.org) Message-ID: <3A91A059.25DDA2F4@gorean.org> Date: Mon, 19 Feb 2001 14:38:17 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Corey Ralph Cc: freebsd-isp@freebsd.org Subject: Re: Bind problems References: <20010213120914.B99396@corey.datafast.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. Have you checked the files it downloads this way for syntax errors? What happens if you try loading the zones after you download them by hand? BIND 8.2.3 and 9.1.* are much pickier about zone file syntax, so chances are that either the master nameservers are no longer authoritative for the zones, or your slave server won't load them because they contain syntax errors. Without knowing more details it's impossible to tell for sure. Good luck, Doug -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message