Date: Tue, 5 Mar 2002 07:20:52 -0800 (PST) From: Greg Quinlan <gwq_uk@yahoo.com> To: FreeBSD-questions@FreeBSD.ORG Subject: Re: named BROKEN? Message-ID: <20020305152052.11397.qmail@web13302.mail.yahoo.com> In-Reply-To: <Pine.BSF.4.43.0203041148240.4557-100000@babelfish2.pursued-with.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Kevin, I heard you the first time! (That was an e-mail typo' I am sorry to say... it actually read 2002030401.. I should have cut & pasted instead of typing it). The date format of YYYYMMDD01 is always used! I have automated the DNS with shell scripts that plug-in automatically, the current date (any time the zone files are rebuilt), and this only happens when the /etc/hosts file changes. The only possible way this could have got out of sync is if the date on the system somehow was out of sync, but because the system uses "ntp", I find that hard to believe too. At no point are the files edited manually .... so you can see my dilemma. (I just find it almost impossible, to have had a larger serial number!) I will keep looking, but since all zone files are given exactly the same serial number each time the system automatically rebuilds these files (and the scripts rebuild all zone files every time) .... well, it is a puzzle why only one zone file fails. It is only a new system, so there is a remote possibility that the System date was initially out of sync when the hardware was delivered...a month ago, I will check older message files, but that does not make sense either based on what I have just said about how the files are built! Thanks Greg --- Kevin Stevens <Kevin_Stevens@pursued-with.net> wrote: > > > 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 > __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020305152052.11397.qmail>