Johnny Hughes wrote:
> On Sun, 2005-06-19 at 02:17 +1200, Tom wrote:
>
>>Hi all.
>>
>>does anyone know if this has been resolved?
>>
>>Important Notice Users updating to CentOS 3.5 from CentOS 3.4 may
>>experience a problem with /etc/named.conf reverting to the default
>>state. This is due to a problem with the new caching-nameserver rpm
>>provided with CentOS 3.5. If the problem does occur, it can be easily
>>corrected by running the following command in a root shell:
>>
>>mv /etc/named.conf /etc/named.conf.CENTOS35UPDATE;mv
>>/etc/named.conf.rpmsave /etc/named.conf;/scripts/restartsrv_named
>>
>>For more information, please refer to this thread on the cPanel Forums:
>>http://forums.cpanel.net/showthread.php?p=191301#post191301
>>_______________________________________________
>
>
> It has not been fixed, because it is the normal behavior for upgrading
> caching-nameserver.
>
> RH has addressed this issue many times, here are some:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145244
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145094
>
>
> RH says that people should not use the /etc/named.conf or any other
> files produced by caching-nameserver (or even use caching-nameserver) on
> a machine that also contains named primary zones and leave caching-
> nameserver installed.
>
> Since it is the default behavior in RHEL is it also the default behavior
> in CentOS-3. It will probably never be changed.
thanks Johnny
regards
tom
