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

Chad Jackson chad at jackson.co.za
Fri Oct 5 23:43:48 UTC 2001


The missing bracket is in the file, I seem to have lost it with the cut and
paste. Here is the section out of the masters file and the actual zone file.

zone "uskotec.com" {
        type master;
        file "zones/master/uskotec.com.";
};

$TTL 14400
$ORIGIN uskotec.com.
@ SOA ns1.btgnet.co.za. dnstech.btgnet.co.za. 2001100601 28800 7200 604800
86400
$INCLUDE /var/named/zones/include/nameservers
$INCLUDE /var/named/zones/include/newscname
$INCLUDE /var/named/zones/include/client_queuemx
@               MX      10      mail.uskotec.com.
dataway         A       209.203.43.80
eb2000          A       209.203.43.80
extranet        A       209.203.43.74
localhost       A       127.0.0.1
mail            A       209.203.43.71
interchange     A       209.203.43.77
www.i-pension   A       209.203.43.77
i-pension       A       209.203.43.77
pss             A       209.203.43.81
home            A       209.203.43.77
www             A       196.41.203.30




-----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 01:18
To: bind-users at isc.org
Subject: RE: NSlookup results not the same as the data in named_dump.db



It appears that you are missing the open bracket "{" after allow-transfer.
Not sure if this would cause the problems you are experiencing or not.

What does the entry in etc/master_zones look like for usktec.com?

ie.

zone "foorbar.com" in {
        type master;
        file "db.foobar.com";
};

-----Original Message-----
From: Chad Jackson [mailto:chad at jackson.co.za]
Sent: Friday, October 05, 2001 4:00 PM
To: bind-users at isc.org
Subject: RE: NSlookup results not the same as the data in named_dump.db



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;
        allow-transfer

                196.3.176.34;
                196.3.167.186;
                196.41.203.67;
        };
};
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
> 196.3.164.11 as the address but in the dump_db and the zone file the
address
> is actually 196.41.203.30 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
the
> old info.




More information about the bind-users mailing list