I am running Netware 5.1 SP8 and named.nlm version 5.12g. I have several zones / subzones for which this server is authoritative.

I also have a secondary zone, say x.y.z, defined on my Netware DNS. The master for this zone x.y.z is hosted on a *nix server running a BIND 9 nameserver.


The named.conf for the *nix BIND server is as follows:
server 2.3.4.5 {
transfer-format one-answer;
};

zone "x.y.z" {
type master;
file "/var/named/x.y.z.hosts";
allow-transfer {
1.2.3.5;
2.3.4.5;
};
notify yes;
also-notify {
2.3.4.5;
};
};

zone "3.2.1.in-addr.arpa" {
type master;
file "/var/named/1.2.3.rev";
allow-transfer {
1.2.3.5;
2.3.4.5;
};
};

zone "0.0.127.in-addr.arpa" {
type master;
file "/var/named/127.0.0.rev";
};

logging {
category lame-servers { null; };
channel my_xfer_out {
file "/var/named_xfer_out";
severity debug 5;
};
category notify { my_xfer_out; };
channel my_notify {
file "/var/named_notify";
severity debug 5;
};
category notify { my_notify; };
};

options {
forwarders {
2.3.4.5;
};
};


The nslookup response from the master (*nix BIND 9) server is as follows:
> server 1.2.3.4

Default Server: devl2.x.y.z
Address: 1.2.3.4

> x.y.z

Server: devl2.x.y.z
Address: 1.2.3.4

x.y.z
primary name server = devl2.x.y.z
responsible mail addr = root.devl2.x.y.z
serial = 1103753607
refresh = 10800 (3 hours)
retry = 3600 (1 hour)
expire = 604800 (7 days)
default TTL = 60 (1 min)
x.y.z nameserver = drdc1.x.y.z
x.y.z nameserver = devl2.x.y.z
devl2.x.y.z internet address = 1.2.3.4
drdc1.x.y.z internet address = 1.2.3.5


The nslookup response from the secondary (Netware) DNS server is as follows:
> server 2.3.4.5

Default Server: mstc-dnsdhcp.a.b.c
Address: 2.3.4.5

> set type=soa
> x.y.z

Server: mstc-dnsdhcp.a.b.c
Address: 2.3.4.5

x.y.z
primary name server = devl2.x.y.z
responsible mail addr = root.devl2.x.y.z
serial = 1103753614
refresh = 10800 (3 hours)
retry = 3600 (1 hour)
expire = 604800 (7 days)
default TTL = 3600 (1 hour)
x.y.z nameserver = drdc1.x.y.z
x.y.z nameserver = devl2.x.y.z
drdc1.x.y.z internet address = 1.2.3.5
devl2.x.y.z internet address = 1.2.3.4


Now, here is my problem:

Yesterday, I deleted domain x.y.z from my Netware NDS, recreated it, and did a manual zone import via "named -zi x.y.z. All was well & good. The serial numbers on both were at 1103753604.

So, to test the updates, my *nix administrator changed his serial number (on the master DNS) to 1103753607. The following excerpt from his BIND log shows some errors:
zone 3.2.1.in-addr.arpa/IN: sending notifies (serial 1103753608)
zone 0.0.127.in-addr.arpa/IN: sending notifies (serial 1103754486)
zone x.y.z/IN: sending notifies (serial 1103753605)
zone 3.2.1.in-addr.arpa/IN: sending notify to 2.3.4.5#53
zone 3.2.1.in-addr.arpa/IN: notify response from 2.3.4.5#53: NOTIMP
zone 0.0.127.in-addr.arpa/IN: sending notify to 2.3.4.5#53
zone x.y.z/IN: sending notify to 2.3.4.5#53
zone 3.2.1.in-addr.arpa/IN: sending notify to 2.3.4.5#53
zone x.y.z/IN: sending notify to 2.3.4.5#53
zone 0.0.127.in-addr.arpa/IN: notify response from 2.3.4.5#53: NOTIMP
zone x.y.z/IN: notify to 2.3.4.5#53 failed: timed out
zone x.y.z/IN: notify to 2.3.4.5#53: retries exceeded

Now, I am left with the serial number on the master (*nix BIND) DNS at 1103753607, & the serial number on the secondary DNS (Netware) is 1103753614!

I am at a total loss as to why the notify/update process caused such erroneous results (ranging from timeouts, to NOTIMP messages, to serials on the secondary being advanced beyond the master).

What is going on????

Thanks.