[Centos] bind and 3.4

[Timothy Sandel]

On Wed, 2005-01-12 at 16:32 +0800, Ho Chaw Ming wrote:
> Yes. Happened on 20 of the servers we updated. It has to do with the
> caching-nameserver I believe. But yes, it caused some extra scrambling
> during the updates.  
> 
> -----Original Message-----
> From: centos-bounces at caosity.org [mailto:centos-bounces at caosity.org] On
> Behalf Of Francois Caen
> Sent: 12 January 2005 15:45
> To: centos at caosity.org
> Subject: [Centos] bind and 3.4
> 
> Hello,
> 
> I encountered a problem when upgrading from 3.3 to 3.4 on i386.
> 
> The machine is a production name server running bind. Looks like the new rpm
> moved my named.conf to .rpmsave and chkconfig'ed bind to off.
> 
> That's really bad. A more gentle behavior would have been to save the new
> named.conf to .rpmnew and not mess with initscripts.
> 
> Anyone else notice that?
> 
> Francois Caen

Here too.  Fortunately, I just did my tertiary dns first to test.  I've
been bit before by this kind of behavior before with
centos/redhat/fedora.  The latest being with the freeradius update.  The
pamauth module got renamed and no one could get authenticated.  I have
also been bit by postfix config renames. 

Timothy 


> _______________________________________________
> CentOS mailing list
> CentOS at caosity.org
> http://lists.caosity.org/mailman/listinfo/centos
> 
> 
> _______________________________________________
> CentOS mailing list
> CentOS at caosity.org
> http://lists.caosity.org/mailman/listinfo/centos