[Centos] bind and 3.4

Wed Jan 12 14:02:03 UTC 2005
Johnny Hughes <mailing-lists at hughesjr.com>

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