[CentOS] Beware - Yum 3.5 to 3.6 upgrade replaces named.conf

[Michael Rock]

I am sure I never specifically installed the caching
name server but a rpm -q caching-nameserver yields
version 7.3-3_EL3.

I usually just select the DNS option during the GUI
install and look to make sure bind is listed (perhaps
the caching name server is automatically checked). 
There after I ended up editing the named.conf or used
webmin that in turn edited the named.conf.

So ultimately I some how ended up with a caching name
server I do not need.  So if I got this right 

1. remove rpm -e caching-nameserver
2. copy my zones from named.conf-rpmsave to
named.custom
3. do not use webmin since it edits named.conf or
reconfigure it to edit named.custom

Should anything be specifically removed from
named.conf or named.custom having to do with the
caching name server?

Did I miss anything here?

Thanks guys.


--- Johnny Hughes <mailing-lists at hughesjr.com> wrote:

> > A real name server doesn't also need
> caching-nameserver installed ... it
> will lookup zones it doesn't control.
> 
> caching-nameserver is what you would install if you
> didn't need to
> control any domains and wanted a local DNS server.
> 
> caching-nameserver is just bind and some config
> files that don't have
> any zones in the named.conf file
> 
> If you install caching-nameserver you are saying
> that you want a DNS
> machine that doesn't control zones.
> 
> If you remove the package caching-nameserver, it
> will save your
> named.custom and named.conf files as rpmsave files
> ... just move them
> back into place afterwards and leave
> caching-nameserver removed.
> > _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com