CentOS - Jan 2005 - 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

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
_______________________________________________
CentOS mailing list
CentOS at caosity.org
http://lists.caosity.org/mailman/listinfo/centos

Yes, it did the same thing to me.  This is NOT a good thing at all.   
The default
should be to make the new named.conf as named.conf.rpmnew, not move the old
one out of the way.   And turning OFF a service is really bad.

Ed Clarke

Francois Caen wrote:
>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
>_______________________________________________
>CentOS mailing list
>CentOS at caosity.org
>http://lists.caosity.org/mailman/listinfo/centos
>  
>

Heads up if anyone removes the caching-nameserver rpm after they fix
their init scripts and replace their named.conf, it also renames your
named.ca to named.ca.rpmsave( I believe this happens when you uninstall
the caching-nameserver rpm, it also moves named.conf back to
named.rpmsave again).

So you have to move that back before you can successfully restart named.

Brent

-----Original Message-----
From: centos-bounces at caosity.org [mailto:centos-bounces at caosity.org] On
Behalf Of Johnny Hughes
Sent: Wednesday, January 12, 2005 9:02 AM
To: CentOS discussion and information list
Subject: RE: [Centos] bind and 3.4


On Wed, January 12, 2005 7:51 am, Lance Davis said:
> On Wed, 12 Jan 2005, Johnny Hughes wrote:
>
>> > This is an upstream issue ... AND ... according to redhat, you
>> shouldn't
>> > have caching-nameserver installed on a DNS server that is anything
>> other
>> > than a caching-nameserver :).  It is indeed the caching-nameserver
>> package
>> > that is causing the issue.
>> >
>>
>> As further clarification, I point exactly to the post:
>>
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=143558#c9
>>
>> I think you should put the new caching-nameserver back into the U4
>> directories ... this will happen anytime redhat issues an update to
>> caching-nameserver and is exactly by design.
>>
>> If you have DNS zones, remove caching-nameserver from that box...it
is
>> not
>> a caching-nameserver any longer
>
> Well I am also going by a post from parsley to the tao mailing list :-
>
>
http://mailman.taolinux.org/pipermail/tao-i386/2005-January/000104.html
>
> I dont think it is right for it to kill a working nameserver on an
update,
> whether or not people have it installed by mistake - ie if it is
already
> installed and the config files have been changd and the thing is
running,
> they should not be removed and the thing stopped - IMHO
>
> Lance
>
> --
I agree, _BUT_ the guy at RedHat is right ... The purpose of
caching-nameserver is to setup a "caching-only-DNS" box ... the only
way
to setup a "caching-only-DNS" box is to remove the current named.conf
file
and replace it with a new one that defines it as a "caching-only-DNS"
box
:)

The lesson learned is ... once you setup your box as a DNS zone control
box, backup the named.conf file and remove the package
caching-nameserver
... OR ... don't install it in the first place.

My guide has been updated to remove the caching-nameserver package after
finishing zone setup :).

-- 
Johnny Hughes
<http://www.HughesJR.com/>

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