I had a pb and several I've helped had the pb of named not loading because
the options {directory} for /etc was not set right. The recommenation is to
use fully qualified path to /dns/etc.
>The NT binaries when installed would not even resolve and outside name. Oh
>well, back to staring
>at the monitor... experience shows it's usually something simple but
>overlooked...
I had exactly this pb also, NT BIND on my Imail dedicated server, running
as a slave, would resolve its own zones, but nothing outside. Sorry, I
don't know how or when it started working just fine. and it was only later
that I got into named logging.
I strongly recommend that turn on full debugging and logging on that
machine watch what it does. As the cricket book points out, BIND logging is
very elaborate (ie, complex). Amazing amt of stuff going on. Here's my
logging statement which, I think, logs anything that happens:
logging
{
channel my_file {file "/etc/namedb/named.run"; severity debug;};
category default {my_file;};
category panic {my_file;};
category packet {my_file;};
category eventlib {my_file;};
category queries {my_file;};
};
This weekend I'm fighting why my two FreeBSD BIND slaves, running identical
named.conf files as NT BIND slave, fail to sync up with the master. NT
slave syncs beautifully. Delete all its etc/db.DOMAIN files, restart it,
and all the db.DOMAIN files are instantly pulled across from the
master. The FreeBSD slaves have "Err/TO getting serial# for
somedomain.com", but execute "dig @master-ns1.domain.com somedomain.com
axfr" or " - soa" perfectly.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
