Ok just saw this, then ignore my last post. So it does not come back if it ever gets updated is 'yum clean all' sufficient.
The reason I ask is there is so much stuff I have gotten rid of in the last year and always seems to come back. For example cups and linux printing rpms. I must have removed them so many times in the last year from these boxes.
--- Johnny Hughes mailing-lists@hughesjr.com wrote:
On Tue, 2005-11-15 at 15:23 -0800, Michael Rock wrote:
If it is just config files then perhaps even
though I
removed the rpm it is still a caching name server since the config files are unchanged?
Can someone tell me what needs to be removed from named.conf so it is not a caching named server?
You are now good to go ... since caching-nameserver is not installed anymore, it will not get updated.
SO ... it won't re-write your config files and you will live happily ever after
There was nothing wrong with your config files before ... just when caching-nameserver is installed, you can't manually update the config files because they will get replaced on the next caching-nameserver update.
--- Johnny Hughes mailing-lists@hughesjr.com
wrote:
On Tue, 2005-11-15 at 15:47 -0700, Craig White wrote:
On Tue, 2005-11-15 at 16:26 -0600, Johnny
Hughes
wrote:
On Tue, 2005-11-15 at 13:47 -0800, Michael
Rock
wrote:
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
- remove rpm -e caching-nameserver
- 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?
named.conf is OK for the config file ... it
won't get changed on future
updates
Did I miss anything here?
Thanks guys.
probably a bugzilla entry to upstream provider
to
maybe create an
'artificial' conflict between the 2 packages
so
that you can't install
both accidentally.
caching-nameserver is just the config files ...
it
requires bind to be installed too
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
__________________________________ Yahoo! FareChase: Search multiple travel sites in
one click.
http://farechase.yahoo.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
__________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com