--- Maciej ¯enczykowski maze@cela.pl wrote:
These may sound like really simple questions but I am questioning my basic beliefs since just learning now that for years I have been incorrectly configuring bind through named.conf and just found out I had a caching-dns rpm installed but did not know it.
I don't think it's a matter of what needs to be removed, but rather what needs to be added - zone declarations need to be added both in the main configuration file and their respective files...
But if that is the case and the rpm is just configuration files it would seem I was not running a caching-name server after all.
Other than my domains nothing here is related to the caching-dns server? I need named.ca so my primary can contact root servers and localhost is normal correct?
controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; }; zone "." { type hint; file "named.ca"; }; zone "localhost" { allow-update { none; }; type master; file "localhost.zone"; }; zone "0.0.127.in-addr.arpa" { allow-update { none; }; type master; file "named.local"; };
Cheers, MaZe.
On Tue, 15 Nov 2005, 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?
--- 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
__________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs