On Tue, May 25, 2004 at 10:11:34AM +0100, Hamilton, David (HPS) wrote:
> 1. which of the named.conf files needs to be correct, or should they be
The one in the chroot, but to save worrying symlink them :) (Make
sure the one outside the chroot is the symlink though)
> 2. Should the directory in the named.conf file be relative to the root
> or the chroot?
Relative to the chroot, but remember that when it's running the chroot
== / , so if the directory is physically at /chroot/bind/etc/namedb/
and the chroot is /chroot/bind/ then /etc/namedb is what should be in
the config file.
> 3. Is there anything else I should look out for.
You'll need to make a /dev/random inode within the chroot and make sure
there's a copy of /etc/localtime within it aswell. Use group writable
permissions for anywhere bind needs to write (location of pid file,
slave zones), make sure it's using as highuid/gid and putting the chroot
on a partition that's mounted noexec,nosuid never does any harm either.
Don't place any executables or libraries in the chroot, you don't need
If you want to use rndc, you'll need to make sure the rndc.key files or
config blocks are syncronised between the versions within the chroot and
the version in the real /etc.
Colm MacCárthaigh Public Key: colm+pgp at stdlib.net
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!