failed NT4 zone transfers

Kimberly O'Brien/OTT/OTI Kimberly_O'Brien at oti.com
Thu Nov 15 23:48:02 UTC 2001


I have two RedHat 7.0 servers for my internal DNS, the primary running 
bind 9.1.3 and the secondary running bind 8.2.4.
The zone transfers work just fine between the two of them.

In addition, I have an NT4sp3 server running bind 8.2.5 that I need to be 
able to secondary only some of the zones from the master. But I cannot 
seem to get the zone transers to work. I cannot see any errors in the 
files and I know that transfers do work to the other RedHat server.  I do 
have basic communications between the two servers and the master is setup 
to allow transfers to the NT box. The NT server can resolve the names of 
the primary and secondary which it has in a local zone file.

Can anyone help?

Here's the log file from the NT server:

15-Nov-2001 17:50:46.000 os: directory c:\winnt\system32\dns is 
world-writable
15-Nov-2001 17:50:46.000 config: cannot set resource limits on this system
15-Nov-2001 17:50:46.000 load: hint zone "" (IN) loaded (serial 0)
15-Nov-2001 17:50:46.000 load: master zone "oti.com" (IN) loaded (serial 
2001111501)
15-Nov-2001 17:50:46.000 load: master zone "207.26.10.in-addr.arpa" (IN) 
loaded (serial 2001090701)
15-Nov-2001 17:50:46.000 default: listening on [10.26.207.3].53 (TCP/IP 
Interface 1)
15-Nov-2001 17:50:46.000 default: Forwarding source address is 
[0.0.0.0].2182
15-Nov-2001 17:50:46.000 default: Ready to answer queries.
15-Nov-2001 17:51:14.000 xfer-in: Err/TO getting serial# for "vame.net"
15-Nov-2001 18:10:14.000 xfer-in: Err/TO getting serial# for "vame.net"

And the named.conf:

options {
        listen-on { 10.26.207.3; };
        directory "c:\winnt\system32\dns";
};
zone "." {
        type hint;
        file "named.root";
};
zone "oti.com" {
        type master;
        file "oti.db";
};
zone "207.26.10.in-addr.arpa" {
        type master;
        file "207.rev";
};
zone "vame.net" {
        type slave;
        file "vame.db";
        masters { 10.26.192.40; };
};

In addition, here's the zone file from the master:

$ORIGIN vame.net.
$TTL    24h
@       24h IN SOA      bapa.oti.com. infott.oti.com. (
                        2000102501      ;Serial
                        3h              ;Refresh
                        1h              ;Retry
                        7d              ;Expire
                        3h )            ;NXDOMAIN cache TTL

                IN NS   bapa.oti.com.
                IN NS   mumu.oti.com.

vame.net.        IN MX            10 www.oti.com.
www                IN CNAME  www.oti.com. 

I've been through the archives and it mentioned something about being 
authoritative, which the primary is:

# dig vame.net

; <<>> DiG 9.1.3 <<>> vame.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28783
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;vame.net.                      IN      A

;; AUTHORITY SECTION:
vame.net.               10800   IN      SOA     bapa.oti.com. 
infott.oti.com. 2000102501 10800 3600 604800 10800

;; Query time: 298 msec
;; SERVER: 10.26.192.40#53(10.26.192.40)
;; WHEN: Thu Nov 15 18:13:06 2001
;; MSG SIZE  rcvd: 86




More information about the bind-users mailing list