Bind-8.2.2 compile question

[David R. Conrad]

Presumably you have some reason why you want to keep the old version around,
but I'd move it to a non-standard place (e.g., .old/).  The only other thing I
might suggest would be to double check to see that your start up scripts start
up BIND 8.2.2-P5 instead of your old version of BIND.

Rgds,
-drc

Sheer El-Showk wrote:
> 
> Hi,
> 
> I've recently upgraded some Linux systems from Bind-8.1.2 to Bind-8.2.2 by
> downloading the new source, compiling it in a seperate directory, shutting
> down the old bind version (/usr/sbin/ndc stop), and then doing a 'make
> install' in the new bind source directory.  Everything seems to be working
> fine, but I'm just worried that the bind install might not overwrite
> everything in the old install (I mean I'm sure I'm now running 8.2.2 -- I
> checked with nslookup, but I'm worried that files lying around from the
> old install might somehow pose a security hazard).  Is this the standard
> procedure for a bind upgrade?  Are there any security precautions I should
> take since the old version of bind had many known exploits and I never
> actually removed it?
> 
> Thanks,
> Sheer El-Showk