I'm having a rough time finding any documentation on the "new" /etc/rc.d/named startup script. I made a big jump from BIND 9.6-ESV (built with the "replace base" option) to dns/bind99, so a crusty old named.conf is in the mix as well.
My prior rc.conf directives were pretty brief, not more than this:
Now I'm attempting something like this:
That results in a very quiet failure:
Nothing in the logs.
Here's my questions:
- In the above rc.conf snippets, I'm not clear on which named.conf location to point to - the one that's symlinked in from /etc or the one inside the chroot? Both fail.
- named.conf contains options that also set file paths, I'm not clear on which of those are relative to the chroot or the real root (for example the directory option) - doing anything other than commenting this out gives errors from named-checkconf during startup.
- Am I missing a way to get the rc.d/named script to output some more info when it fails? I'd at least like to see what args it's passing to
Lastly, if I start it by hand like so, no problems:
edit: here's the result of setting
My prior rc.conf directives were pretty brief, not more than this:
Code:
named_enable="YES"
named_flags="-u bind -t /var/named"
Code:
named_enable="YES"
named_program="/usr/local/sbin/named"
named_conf="/etc/namedb/named.conf" # Path to the configuration file
named_flags="" # Use this for flags OTHER than -u and -c
named_uid="bind" # User to run named as
named_chrootdir="/var/named" # Chroot directory (or "" not to auto-chroot it)
named_chroot_autoupdate="YES" # Automatically install/update chrooted
# components of named. See /etc/rc.d/named.
named_symlink_enable="YES" # Symlink the chrooted pid file
named_wait="NO" # Wait for working name service before exiting
named_wait_host="localhost" # Hostname to check if named_wait is enabled
named_auto_forward="NO" # Set up forwarders from /etc/resolv.conf
named_auto_forward_only="NO" # Do "forward only" instead of "forward first"
Code:
Starting named.
/etc/rc.d/named: WARNING: failed to start named
Here's my questions:
- In the above rc.conf snippets, I'm not clear on which named.conf location to point to - the one that's symlinked in from /etc or the one inside the chroot? Both fail.
- named.conf contains options that also set file paths, I'm not clear on which of those are relative to the chroot or the real root (for example the directory option) - doing anything other than commenting this out gives errors from named-checkconf during startup.
- Am I missing a way to get the rc.d/named script to output some more info when it fails? I'd at least like to see what args it's passing to
named
.Lastly, if I start it by hand like so, no problems:
/usr/local/sbin/named -u bind -t /var/named -c /etc/namedb/named.conf
edit: here's the result of setting
rc_debug="YES"
and trying to start - note that the "-c" option to specify the config file is missing:
Code:
/etc/rc.d/named: DEBUG: run_rc_command: doit: /usr/local/sbin/named -t /var/named -u bind
/etc/rc.d/named: WARNING: failed to start named