DNS /Bind / Named/ Redhat /Help

[M_THACH_XUAN]

Ignore that bit about the hard links, it seems a symbolic link is OK with test
-f
Marc Thach Xuan Ky
marc.thach at tesco.net

>
>I did this on RH 6.1:
>binaries were in /usr/local/sbin so I hard-linked them into /usr/sbin.  My
>named is started via the rc.d files.  My kernel is 2.2.nn so I then altered
the
>/etc/init.d/named script so that named was not called with -u.  I notice that
>this script also does a test -f on the binaries so symbolically linked
binaries
>will not start out of this script file.  If you are starting named out of the
>rc.d files then you may need to change to hard links.
>Marc Thach Xuan Ky
>marc.thach at radianz.com
>
>>Ok, why is this so hard.
>>
>>I have bind 8.22 installed in /usr/sbin.  When I upgrade to bin 9.0, it puts
>>it in /usr/local/sbin.  I have created symbolics links from /usr/sbin/named
>>to /usr/local/sbin/named and I have also configured the
>>/etc/rc.d/init.d/named file to point to /usr/local/sbin and to use
>>/usr/local/rndc instead of /usr/sbin/ndc.
>>
>>Nothing works.   I am getting more errors and am obviously over complicating
>>the situation.
>>
>>Has anyone installed bind 9.0 on top of bind 8.22 on a
>>redhat 6.2 linux configuration?  What is the best way to remove bind 8.22
>>and install bind 9.0?  What is the best way to make sure it starts on boot
>>up? (chkconfig, rc.conf, rc.local, etc.)  If new programs are installed in
>>/usr/local/sbin , what is the best way to make sure all references to the
>>old program at /usr/sbin are no longer used?
>>
>>
>>
>>
>