Hi, Here is my 'cheat sheet' for running chrooted bind9 within jail: o 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 ;) -- Clive Tong-I Lin | http://tongi.org | PGP KeyID: A008C03EReceived on Tue Oct 19 2004 - 12:14:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC