On Wed, 31 Dec 2008 10:03:45 -0500 (EST) lenny@edpausa.com wrote:
>
> bind 9.4.2/FreeBSD 7.0 seems to be ignoring many settings I enter in
> /etc/namedb/named.conf. zones are being properly served internally, but
> can't query or transfer from the outside.
> listen-on {216.154.117.227; 192.168.1.1;};
> listen-on-v6 { none; };
I wonder if the spaces around curly braces that named examples always
use are mandatory? As in listen-on { 216.154.117.227; 192.168.1.1; };
> tcp6 0 0 ::1.953 *.* LISTEN
> tcp4 0 0 127.0.0.1.953 *.* LISTEN
> tcp4 0 0 192.168.1.1.53 *.* LISTEN
Looks like it's not seeing named.conf, assuming that 216.154.117.227
exists as the address of a local interface at the time when named is
started, as Mel mentioned. This can be a problem with ppp or mpd ..
What does 'realpath /etc/named' say? Are you using the FreeBSD default:
% realpath /etc/namedb
/var/named/etc/namedb
% ls -l /etc/namedb
lrwxr-xr-x 1 root wheel 21 Dec 12 02:37 /etc/namedb -> /var/named/etc/namedb
If you run '/etc/rc.d/named stop' and then '/etc/rc.d/named start', what
shows up in /var/log/messages ?
What's in /etc/rc.conf concerning named ? Any clues from 'rndc status'?
cheers, Ian