BIND CHROOT strange problem

[Eivind Olsen]

--On 30. oktober 2001 17:08 +0530 Anand R <anand.r at cybertech.co.in> wrote:
> Hi,
> 	Presently trying to implement Chroot BIND 9.1.3 on my Redhat Server
> 7.1. Well I tried to set up everything as instructed in the HOWTO, some
> documents and suggestions by this list members. However named exits with a
> fatal error message. The error message is as below:
>
> Oct 30 14:56:01 tux /chroot/named/bin/named[6590]: starting BIND 9.1.3 -c
> /chroot/named/etc/named.conf -u named -t /chroot/named
> Oct 30 14:56:01 tux /chroot/named/bin/named[6590]: using 1 CPU
> Oct 30 14:56:01 tux /chroot/named/bin/named[6592]: loading configuration
> from '/chroot/named/etc/named.conf'
> Oct 30 14:56:01 tux /chroot/named/bin/named[6592]:
> /chroot/named/etc/named.conf: open: file not found
> Oct 30 14:56:01 tux /chroot/named/bin/named[6592]: loading configuration:
> file not found
> Oct 30 14:56:01 tux /chroot/named/bin/named[6592]: exiting (due to fatal
> error)

The problem is that you're telling named to use the config-file 
/chroot/named/etc/named.conf
You should tell it to use /etc/named.conf (because when it reads the 
config-file, it has set the chroot() to /chroot/named already).

Did this make any sense?

-- 
Talk To You Later
Eivind Olsen