From owner-freebsd-questions Mon Mar 4 11:52:59 2002 Delivered-To: freebsd-questions@freebsd.org Received: from babelfish2.pursued-with.net (adsl-66-125-9-242.dsl.sndg02.pacbell.net [66.125.9.242]) by hub.freebsd.org (Postfix) with ESMTP id 42F0237B402 for ; Mon, 4 Mar 2002 11:52:57 -0800 (PST) Received: from babelfish2.pursued-with.net (babelfish2.pursued-with.net [192.168.168.43]) by babelfish2.pursued-with.net (8.11.6/8.11.6) with ESMTP id g24JtG104995; Mon, 4 Mar 2002 11:55:16 -0800 (PST) (envelope-from Kevin_Stevens@pursued-with.net) Date: Mon, 4 Mar 2002 11:55:16 -0800 (PST) From: Kevin Stevens Reply-To: Kevin_Stevens@pursued-with.net To: Greg Quinlan Cc: FreeBSD-questions@FreeBSD.ORG Subject: Re: named BROKEN? In-Reply-To: <20020304191053.78438.qmail@web13304.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 4 Mar 2002, Greg Quinlan wrote: > Hi All, > > This is the full message with error!! > > starting (/etc/namedb/named.conf). named 8.3.1-REL Mon Mar 4 10:51:18 EST > foo.com:/usr/obj/usr/src/usr.sbin/named > Mar 5 04:55:18 bsd named[624]: limit files set to fdlimit (1024) > Mar 5 04:55:18 bsd named[624]: master zone "foo.com" (IN) rejected due to > errors (serial 2002030501) > Mar 5 04:55:18 bsd named[625]: Ready to answer queries. > > Any ideas? > > Thanks > > Greg YES! As said before, FIX YOUR SERIAL NUMBERS! You had a serial number of 200204something before, now you have 200203something. This WILL NOT WORK. Do you understand that number is NOT parsed as a date? Updated zone files must have HIGHER numbers. If you screwed the zone up originally by trying to use a Euro date such as 2002270201, you can't just randomly start using lower numbers. I don't remember how to fix numbering, I think it involves using a higher legitimate number with a very short expiration period, letting it expire, and restarting with a new lower one. But I'm not sure, you need to find a BIND resource somewhere. You may possibly have other problems with the zone file, but it WILL NOT WORK until you fix the screwed-up serialization. Stop posting until you fix that. For that matter, the whole issue is one for a BIND list, not FreeBSD. KeS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message