[CentOS] Beware - Yum 3.5 to 3.6 upgrade replaces named.conf -- not a YUM issue ...

Jim Perrin jperrin at gmail.com
Tue Nov 15 20:00:57 UTC 2005


On 11/15/05, Bryan J. Smith <thebs413 at earthlink.net> wrote:
> Michael Rock <mikerocks65 at yahoo.com> wrote:
> > So looked like another smooth ride, well until today I
> > noticed my domains dropped off the net. Too bad I did
> > not check the bind gui or look at /etc/named.conf
> > after the yum update since it was replaced with a
> > generic version from 3.6.
> > Luckily I copied /etc/named.conf-rpmsave to named.conf
> > and I am back in business, well at least in 24 to 72
> > hours for the rest of the world :(
>
> Has nothing to do with YUM.
> It has to do with RPM.

Close. It has to do with RH policy.


> Now I agree you should _never_ see this out of a RHEL/CentOS
> update.  That's the whole purpose of backporting changes in
> RHEL/CentOS updates -- to _avoid_ this from every occurring.

RHEL tries. the named.conf file says to not edit it, and to use
named.custom. Some people don't follow the directions. see bugs:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145094
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145244

>
> But apparently it did.

And it will continue to for as long as people do what redhat perceives
as the "wrong" thing.

Yes this post is mostly a dupe of what I just posted under the
original thread. People keep changing subjects and choking gmail.

--
Jim Perrin
System Architect - UIT
Ft Gordon & US Army Signal Center



More information about the CentOS mailing list