#4 Probind and fedora 2 issues

[Anonymous]

It appears there is a problem with the default install of
bind and probind on Fedora Core 2.

Fedora core 2 install chroot bind. This is for security,
however probind does not know of the chrooted dir.

The problem it causes:

It creates db.zone files in /var/named.

However the chroot runs
in /var/named/chroot/var/named.

It can create the files fine, but when named starts it
starts chrooted thinking
that /var/named/chroot/var/named is the
actual /var/named and the db. files do not exists in that
directory.

Youc an update the path where the zones live in
probind, but that creates another problem. When it
writes the named.conf file it writes:

options {
directory "/var/named/chroot/var/named";
};

which when named runs in chroot mode, the dbfiles may
exists now in /var/named/chroot/var/named

but now bind is looking for the db files
in /var/named/chroot/var/named/chroot which doesnt
exisists because bind thinks you are in /var/named
(because of chroot) and there is no /var/named/chroot
in the chrooted directory. if that makes sense?