From owner-freebsd-current Thu Sep 24 17:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17139 for freebsd-current-outgoing; Thu, 24 Sep 1998 17:11:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17115 for ; Thu, 24 Sep 1998 17:11:38 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id TAA28594 for ; Thu, 24 Sep 1998 19:11:32 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <024501bde819$0d037a00$c3e0d9cf@westbend.net> From: "Scot W. Hetzel" To: Subject: Re: DNS in CURRENT Date: Thu, 24 Sep 1998 19:11:31 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Studded >Handy upgrade guide: > >1. Make good, reliable backups of your current configuration, store them >in more than one physical location and TEST to make sure that you can >actually recover with them. :) That last step is often skipped by >people and you only find out that you're fubar at the worst possible >moment. > >2. Make sure that your *current* configuration is working as it should >be. At minimum I open up two windows to the server, start 'tail -f >/var/log/named.log' in one and then shut the server down in the other. I >watch the log while it shuts down, then start it up and watch it again >to make sure that there are no errors. Once I'm convinced that things >are working as advertised I proceed. If I have to make any changes to >make things go I repeat step one. > >3. Back up the current working binaries. First lesson on first day of >sysadmin school, make every change reversible. > >4. Unpack the BIND source and read the installation documentation. > >5. Compile and install that bad boy. :) > SKIP steps 4&5 and install/upgrade to 3.0-(CURRENT or BETA), BIND 8 installed by default. >6. Convert your named.boot file to named.conf using the >src/bin/named/named-bootconf.pl script. > >7. At this point I usually rotate the named logs so that I know I'll be >logging the new stuff in new logs but this is optional. > >8. Make sure that you're watching the log in one window (tail -f above) >and then start up the new named in the other and with luck watch >everything work the way it should. :) > > At times BIND 8 will find bogons in your zone files that were >not a >problem for older versions of BIND 4. Underscores in host names are very >common errors that pop up after an upgrade, as are various problems with >CNAME's. You might want to give the html documentation for the config >file a look two or three times before you start it up. There are some >options you can tailor to increase named's efficiency based on your >particular needs. Several of those options were compile options with >BIND 4. > Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message