Hello System Admins,
I got some very good advice from the following:
(Thank you VERY much!)
Parris B. Wood <pwood_at_widomaker.com>
Ian Mortimer <ian_at_physics.uq.edu.au>
My original posting is at the very end of this message.
I managed to do the upgrade using all the defaults and
was surprised how easy it was. Note that if you do the
installation like I did, you'll probably have to repeat it
whenever you upgrade the operating system. Here are the
steps that worked for me:
Upgrading BIND 4.9.3 to BIND 4.9.7 on DU 4.0B
----------------------------------------------
1. Downloaded BIND compressed tar file from www.isc.org,
uncompressed it, and put it in my build area. Once
I did this, it looked like this:
# ls -l /usr/local/sysadm/bind/bind-4_9_7-REL_tar
-rw-r--r-- 1 root system 7116800 Jun 18 11:49
bind-4_9_7-REL_tar
2. Did the "untar" to expand the distribution:
# cd /usr/local/sysadm/bind
# tar -xvf bind-4_9_7-REL_tar
3. Then I just followed the instructions in the INSTALL file
from the expanded distribution. (See the next couple of steps.)
I found nothing of interest to me in the README file -- it's a
little dated and I was only interested in a simple default
installation. The instructions in the file INSTALL
are simpler and more up-to-date.
4. I edited the file Makefile. The only change necessary was
to uncomment the 17 lines in the section following the comment:
#(DEC AXP OSF/1 Version 3.0 and after)
5. I did nothing to the file conf/options.h -- you can change
options by editing this file if you wish. I just took all
the defaults by not changing anything.
6. Then, while "sitting in" the dir /usr/local/sysadm/bind
(my distribution subdirectory) I invoked the make command:
# make
<<This compiled the distribution>>
7. Then, I invoked the make command again this way:
# make install
<<This installed the distribution>>
Note that you could run "make -n install" first just to see
where all the files will be installed, and thus get advanced
warning as to which of your current files will be replaced.
8. The new named executable ended up in /usr/sbin as
/usr/sbin/named, but since our current named was in /sbin
as /sbin/named, and that is where our system startup file
would look for it, I copied the new one there:
# cp /usr/sbin/named /sbin/named
Of course, an alternative is to alter the system startup
file to tell it to invoke named from /usr/sbin.
9. Finally, I restarted named to begin using the new one:
# ps -ef | grep named
<<This shows the pid of named and command used to start it>>
root 216 1 0.6 13:37:49 ?? 1:17.46
/sbin/named -b /etc/namedb/named.boot
# kill -9 216
# /sbin/named -b /etc/namedb/named.boot
The new Domain Name Service worked fine.
Paul Youngblood
---------------------------------------------------------
Original Posting
---------------------------------------------------------
Date: Mon, 20 Jul 1998 16:27:19 -0500 (CDT)
From: "Paul N. Youngblood" <youngbp_at_email.uah.edu>
To: alpha-osf-managers_at_ornl.gov
Subject: Upgrade to BIND 4.9.7 - defaults okay?
Followup-To: poster
Hello system admins,
I'm planning to upgrade BIND from 4.9.3 to 4.9.7 on the
machine which functions as our domain's SECONDARY BIND server.
Our version of DU is 4.0B, and we run Enhanced Security.
I downloaded the 4.9.7 distribution from www.isc.org, not
from Digital, if that makes any difference.
I want to do a "simple" default installation as described
in the distribution file "INSTALL", and I welcome any advice
you can give. According to the output of the command
"make -n install", it appears that just about everything
will be installed in the following directories -- did this
work for you, or do you recommend installing elsewhere?
/usr/lib
/usr/include
/usr/sbin
/usr/bin
Thank you very much for your time. I will summarize.
Paul Youngblood
University of Alabama in Huntsville
youngbloodp_at_uah.edu
Received on Wed Jul 22 1998 - 20:12:52 NZST