Problems Chrooting under Bind 9

[Mark_Andrews at isc.org]

> I'm trying to start up named using
> 
> named -u named -g named -t /usr/local/etc.  That results in the message
> below
> 
> # /usr/local/sbin/named -u named -g named -t /usr/local/etc
> usage: named [-c conffile] [-d debuglevel] [-f|-g] [-n number_of_cpus]
>              [-p port] [-s] [-t chrootdir] [-u username]
> named: extra command line arguments
> 
> I then try starting it w/out the -g flag and the following error is log to
> messages on my system
> 
> Nov  2 17:20:59 bind9 named[498]: [ID 866145 daemon.notice] starting BIND
> 9.2.1
> -u named -t /usr/local/etc
> Nov  2 17:20:59 bind9 named[498]: [ID 866145 daemon.error] none:0: open:
> /usr/lo
> cal/etc/named.conf: file not found
> Nov  2 17:20:59 bind9 named[498]: [ID 866145 daemon.crit] loading
> configuration:
>  file not found
> Nov  2 17:20:59 bind9 named[498]: [ID 866145 daemon.crit] exiting (due to
> fatal
> error)
> 
> The questions I have is why doesn't the -g work in the first example.  How
> come named won't start when I just use -u and -t flags. /usr/local/etc is
> where all config, etc files are located so not sure why it's complaining
> there.

	Because '-g' has a different meaning in BIND 9.  The groups will be
	set from the /etc/passwd and /etc/group files, see initgroups().

	Because the chroot() takes effect before the open().  Named is
	actually attempting to open /usr/local/etc/usr/local/etc/named.conf.

	Mark
 
> Any insight would be appreciated
> 
> Thanks,
> 
> Bill

	
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org