I'm running FreeBSD 9 and I recently instlaled bind98 from ports. Install went fine. However, my previous configuration (bind96) did not work with this version of BIND. Well, the configuration was okay, but the rc.conf setup didn't work. It looks like bind98 ignored my "named_flags" settings: Code: named_flags="-u bind -c /etc/named.conf" That path is relative to my chroot for BIND. bind98 seems to only want to load named.conf from the following location: /etc/namedb/named.conf All the other rc.conf settings are okay, but unless I have named.conf in /etc/namedb/, startup fails with the message: Code: /etc/rc.d/named: ERROR: get_pidfile_from_conf: /etc/namedb/named.conf does not exist (named) If I start named manually, it is able to pick up my configuration file. This works fine: named -u bind -t /var/chroot/named -c /etc/named.conf So, my question is: did something change in the way bind98 works in regards to the location of the configuration? Does it have to be in that specific location? Or, is there a bug in the /etc/rc.d/named startup script? Thanks for whatever information you can provide.