Great article. I think I might be the person who posted the idea of using system-config-bind to generate the zone files in the bind mailing list. Now, working on a bunch of remote servers, I was looking around to see if Fedora Core 8, and the newest version of bind, has resolved the problem (it hasn’t been resolved) and came across your excellent site.

With a bit of experimentation, I’ve learned that bind-chroot takes its .conf and zone files from the existing bind configuration. So, to be slightly more syntactically consistent (and also to point out that these files have to be properly permissioned for security purposes), I’m offering the following slight revision:

yum install system-config-bind (Do not install bind-chroot, yet.)
mv /etc/named.conf /etc/named.orig
cd /usr/share/system-config-bind/profiles/default
cp -p named.conf /etc/
chmod 640 /etc/named.conf
cp ./named/* /var/named/
chmod 640 /var/named/named*
chmod 640 /var/named/local*
vim /etc/named.conf (change named.root to named.ca)
yum install bind-chroot

All of the files and settings will be copied from the standard bind configuration to the jailed configuration. Looking forward to future collaboration!

Best,
Steven Stromer