Saturday, July 7, 2007

chrooted bind9 within jail

First, make sure the the /etc/namedb is correctly symlinked to
/var/named/etc/namedb. make distribution (part of jail building
process) does _not_ do it rignt.

o Assuming your jail is at /d/jails/myjail, and the hostname is myjail,
now issue

# cd /d/jails/myjail/var/named/dev
# mknod random c 245 0; mknod null c 2 2

o finally, put 2 lines in myjail:/etc/rc.conf
named_enable="YES"
named_chroot_autoupdate="NO"

That's all. I've deployed several 5.3 boxes since the frist day bind
got chrooted, without noticeable problem.

PS, if it's the first time your cute bind9 booting up, run
make-localhost and fix named.conf. there's no 127.0.0.1 within jail ;)