Upgrade BIND

[hello1]

Hello,

I have currently BIND 9.2.4 installed on the server . Can someone plz let me know the steps to upgrade bind on the server to 9.5.1 .

Thanks
Vince

 

[faris]

If you use Centos or Fedora, you'd use

yum update bind

You can update every out of date OS package using yum update (or yum upgrade)

For RedHat you'd use a utility called up2date instead.

For other OSes -- no idea

Faris.

 

[s3c0ndsky]

is it safe ?
will it break the plesk or not ?

thanks

 

[faris]

It is *mostly* safe.

There are some things to look out for.

1) /usr/sbin/suexec -- make a copy of this file before updating your system.
If apache (http) is upgraded, then your CGI scripts will stop working because /usr/sbin/suexec will be replaced during the update. But if you have previously made a copy, you can then overwrite the new file with your copy.

2) /etc/php.ini -- make a copy of this file before you upgrade, just in case it gets overwritten (it should not).

3) /etc/named.conf -- make a copy of this file. Also make a copy of /etc/sysconfig/named

4) Make sure you do not have bind-chroot or cacheing-nameserver installed. (Use: rpm -qa bind-chroot and then rpm -qa cacheing-nameserver to check). If you do have them installed, remove them using: yum remove bind-chroot and then yum remove cacheing-nameserver. When you remove them bind/named will probably stop working and everything will go wrong. To get things working again, copy the backup files you made in step 3 back, then issue the command: service named restart

There may be other little things that I've forgotten but hopefully not.

WARNING: Do this at your own risk. I may have made errors in my suggestions/instructions. I may have left out something vital. It would be sensible to make a backup of your system before doing anything, just in case something goes wrong.

Faris.

 

[s3c0ndsky]

hi faris,

thanks for the reply..
Will give it a try..
greatly appreciate it...

 

[faris]

This sort of thing can be very stressful when you do it the first few times.

I assume you are on a dedicated server?

You might consider installing Virtuozzo (or openVZ) for your next server. Even if you only have, say, one or two "Containers" (VPSes), it makes recovering from errors easy because you can backup and restore the entire VPS in a matter of minutes.

For example we have one Container running Plesk 8.2.1. It was time to upgrade to 8.6.x. I went through the upgrade motions and BANG - serious problem, Plesk borked. I could have spent an hour or so possibly fixing the borked upgrade, or possibly I would have failed. Instead I checked what had gone wrong, then restored the Container to the backup I had made just before trying the Plesk upgrade, fixed the problem that had caused the problem, and upgraded again. It all took 10 minutes and everything was fine this time.

Of course there are other ways to backup and restore that don't involve using virtualisation! e.g. 4psa's Total Backup, or just manually dumping databases and tarring directories, or using some other form of backup. In fact lvalics has a nice script that a few people have been using that backs everything up for you.

And when playing with things that might go wrong (Plesk updates in particular), backups can be a life saver.

I hope all goes well for you -- it should. You are not doing anything too dangerous. It is just necessary to make sure you have backups of the important config files in order to prevent things going horribly wrong if you do encounter a problem.

Faris.