NSlookup results not the same as the data in named_dump.db

Chad Jackson chad at jackson.co.za
Fri Oct 5 23:00:13 UTC 2001

I have had three sysadmins check the file, they all think it looks fine. Its
real simple, some logging parameters and a list of servers allowed to
transfer, the secondary is on the list and access is allowed. As I wrote
earlier manual transfers work

Heres the file:
logging {
        channel my_syslog {
        syslog local2;
        severity info;
        category default { my_syslog; default_debug; };
        category panic { my_syslog; default_stderr; };
        category packet { default_debug; };
        category eventlib { default_debug; };
options {
        version "Whatcha looking at Jonny";
        directory "/var/named";
        dump-file "log/named_dump.db";
        statistics-file "log/statsfile";
        interface-interval 0;
        check-names master warn;
        notify yes;

zone "." {
        type hint;
        file "zones/root.cache";
include "etc/master_zones";
include "etc/slave_zones";

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Chris Parker
Sent: 06 October 2001 12:28
To: bind-users at isc.org
Subject: RE: NSlookup results not the same as the data in named_dump.db

Maybe an error in named.conf?

> ok the specific address is for the www.uskotec.com the ns1 and ns2 show
> as the address but in the dump_db and the zone file the
> is actually which it should be. When I do a ndc restart the
> log shows that the zone has loaded no errors and the db data shows what I
> want. Also if I do a named-xfer to the temp directory on ns2 the data is
> old info.

More information about the bind-users mailing list