bind config files with caching-nameserver.rpm

[texaganian]

Playing around a little with a lab network of virtual centos 5.3 machines.

I built a test DNS server and decided to see what the caching-nameserver.rpm package was all about.

And, of course, it works. Pretty painless if all you need is a caching server.

However, I'm a bit baffled how it is working. The only config file it creates is /var/named/chroot/etc/named.caching-nameserver.conf (with a sym link in /etc).

So I have two questions:

1. How does bind know to use this config file? I thought bind only looked for /etc/named.conf.

2. The symlink in /etc is actually to /var/named/chroot//etc/named.caching-nameserver.conf. Why the double slash after /var/named/chroot?

[Lazydog]

1. How does bind know to use this config file? I thought bind only looked for /etc/named.conf.

Redhat installs Bind in a chroot env. The starting script is told how to start Bind which then Bind thinks /var/named/chroot is the root of the system thus it thinks it is looking at /etc/namd.conf

2. The symlink in /etc is actually to /var/named/chroot//etc/named.caching-nameserver.conf. Why the double slash after /var/named/chroot?

Don't think this is right are you sure about the double slash?