edwarner99@xxxxxxxxx wrote:
From: Gordon Messmer <yinyang@xxxxxxxxx>
Sounds like chroot isn't working, or isn't being
attempted. Are there
any interesting errors logged in /var/log/messages by
named? Does
/etc/sysconfig/named still say
"ROOTDIR=/var/named/chroot"?
I'm guessing here, but SELinux might be breaking > >
something. Does chroot work properly if you boot with
SELinux disabled?
I have never changed /etc/sysconfig/named. It is still
"stock". What lines have to be changed?
None. bind-chroot adds the line "ROOTDIR=/var/named/chroot" to that
file. Just check to make sure that's still in there.
I am running SELinux disabled.
OK, what about the messages log? If you restart bind, do you see
anything interesting there?
