named not starting on reboot
admin2 at enabled.com
Tue Feb 27 18:00:32 UTC 2007
> Noah wrote:
>> Hi there,
>> I am having troubles with named not starting on boot nor am I am able to
>> start it manually. I thought I have my chrootdir set correctly.
>> here are my settings in my rc.conf
>> ----s nip ----
>> named_flags="-c /etc/namedb/named.conf"
>> ---- snip---
>> here are the /var/log/messages error:
>> Feb 27 09:07:46 access2 named: /etc/named.conf:6: change directory
>> to '/var/named/etc/namedb' failed: file not found
>> Feb 27 09:07:46 access2 named: /etc/named.conf:6: parsing failed
>> Feb 27 09:07:46 access2 named: loading configuration: file not found
>> Feb 27 09:07:46 access2 named: exiting (due to fatal error)
> What are your permissions on /var/named ? how about
> /var/named/etc/namedb ? by default i think the chroot stuff expects or
> wants /etc/namedb to be a symlink to /var/named/etc/namedb, is this the
> case ?
> What is line 6 of your /etc/named.conf and why is named looking for this
> rather than /etc/namedb/named.conf as specified.
> I have the portsversion of 9.3 with DLZ on my laptop as a testbed and it
> works fine with
> named_flags="-c /etc/namedb/named.conf"
> So my guess is permissions or configuration file issue
acutally karol's post helped a great deal:
Here is a mistake. Is a 'directory' in /etc/namedb/named.conf set to
"/var/named/etc/namedb" is a global path, named starting in chroot won't
be able to see it. Just change it back to "/etc/namedb".
>> freebsd-questions at freebsd.org mailing list
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions