Hong Siew wrote:
Thanks for all your responses, still no joy, the following are from "tail -f /var/log/messages" command:
Starting BIND 9.2.2-P3 -u named -t /var/named/chroot Using 1 CPU Loading configuration from '/etc/named.conf' Named startup succeeded No IPv6 interfaces found Listening on IPv4 interface lo, 127.0.0.1#53 Listening on IPv4 interface eth0, 172.16.1.21#53 Command channel listening on 127.0.0.1#953 Zone aha/IN: loading master file aha.zone: file not found Running
Named just wouldn't find the aha.zone file. This file is definitely in /var/named/chroot/var/named directory (double and triple checked). The permissions are rw-r--r-- with named as the owner and group.
Also checked the /etc/sysconfig/named to make sure ROOTDIR=/var/named/chroot.
This may seem like a silly suggestion, but what do you have as a "directory" statement in your named.conf? It needs to be specified from the chrooted environment's point of view, so, for example, if your zone file is /var/named/chroot/data/foo.com, /var/named/chroot/etc/named.conf should contain:
directory "/data";
zone "foo.com" {
file "foo.com";
};That file and directory need to be readable by the named user. If you're setting up a slave server, the data directory also needs to be writeable by the named user.
In any case, a copy of the relevant portions of your named.conf might help us help you.
I recently set up three chrooted FC1 nameservers and they're running happily, so it -is- possible.
