From owner-freebsd-isp Thu Jul 17 23:11:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01724 for isp-outgoing; Thu, 17 Jul 1997 23:11:34 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01718 for ; Thu, 17 Jul 1997 23:11:29 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id XAA24363; Thu, 17 Jul 1997 23:10:00 -0700 (PDT) Date: Thu, 17 Jul 1997 23:10:00 -0700 (PDT) From: Jim Shankland Message-Id: <199707180610.XAA24363@biggusdiskus.flyingfox.com> To: dan@dpcsys.com Subject: Re: Root nameservers messed up? Cc: isp@freebsd.org Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dan Busarow writes: > If you use 8.1.1 it shouldn't be any big deal.... Since 8.1.1 is > all userland you just build it, convert named.boot to named.conf, > kill the old named and startup the new one. Your DNS will only > be down for as long as it takes to load the zone files. Just thought I'd note I haven't found it quite that simple. Granted, I'm only an hour into this little project, but an hour was all I'd budgeted -- sort of thought this was going to be a no-brainer. It appears that the syntax of the named.conf file is different from that of the named.boot file of bind 4.x.x. Furthermore, all the documentation I pulled down from ftp.isc.org the other day describes the old boot file format; so far, the only reference for the new named.conf file format that I've found is the yacc grammar. I can live with that if I have to; but did I take a wrong turn somewhere? I think, just in case, I'll go to bed and get a fresh start in the morning .... Jim Shankland Flying Fox Computer Systems, Inc.