On Sat, 1 Dec 2007, Charles Curley wrote:
I also found out that restarting from gbindadmin does not produce the
same output in syslog as running "/etc/init.d/bind9 start". Something
is screwy!
There are two configuration file trees, one under /etc and the other
under /var/named/etc, for named. The former is provided by the bind9
package, and the latter I conjecture by the gbindadmin package. Since
the latter is designed to run named in a chroot jail, I went with it by
modifying /etc/default/bind9 like so:
--------------------------------------------------
OPTIONS="-u bind -c /etc/named.conf -t /var/named"
# Set RESOLVCONF=no to not run resolvconf
RESOLVCONF=yes
--------------------------------------------------
Yeah, it's a good idea to run it chrooted.
I've never used gbindadmin before but it sounds like it wasn't as helpful
as it could be. :)
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
