Beware of bind-9.2.4-8_FC3:20 (was BIND (Network Manager)

[Craig White]

On Fri, 2005-01-21 at 10:07 -0500, jim lawrence wrote:
> Quote:
> I would love to know if the same problem has occurred that I am struggling with.
> 
> Please look into your /var/named directory where you should find a few
> other directories and static links to the files which are actually
> located in the /var/named/chroot/var/named path. If you find that
> there are more files in the chroot path then make static links for the
> extra zone files back into the /var/named path. then try restarting
> the DNS service.
> 
> Friday I will get to look at this myself on another of my FC3 installs
> at work. I believe now that this is the initial problems I have had
> which I fixed by making the static links back to the non-chroot path.
> 
> Someone explain this to me?? 
----
Either you run named in chroot jail or you don't - your suggestion wants
to have it both ways...doesn't seem to be the right solution.

# cat /etc/sysconfig/named
# Currently, you can use the following options:
# ROOTDIR="/some/where"  --  will run named in a chroot environment.
#                            you must set up the chroot environment
before
#                            doing this.
# OPTIONS="whatever" -- These additional options will be passed to named
#                       at startup. Don't add -t here, use ROOTDIR
instead.

If you run named in chroot environment then just consider everything
relative to /var/named/chroot as the root directory.
i.e.
/var/named/chroot/etc/named.conf
/var/named/chroot/var/named/all_zone_files_etc.

so rather than making links to /var/named stuff, why not just mv the
files to where they are now expected to be...

mv /etc/named.conf /var/named/chroot/etc
mv /var/named/* /var/named/chroot/var/named

Craig