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
--
uklinux.net -
The ISP of choice for the discerning Linux user.
