Problem transferring a zone

[Kevin Darcy]

Looks like a zone transfer has gotten "stuck" somehow, or at least named
thinks the zone transfer is in progress when it actually isn't. On top of
that, the output from the NT side indicates that its nameserver doesn't
like the NOTIFY responses for some reason, and that's why it keeps
re-sending the NOTIFYs. BTW, RFC 1996 recommends 5 retries with an
"additive or exponential backoff for the retry interval". Sounds like the
NT nameserver is blatantly disregarding that recommendation. Of course,
with a refresh set to 15 minutes and a retry set to 10 minutes, you should
be expecting rabid zone-checking behavior anyway.

There are a couple zone-transfer-related bugs fixed in the 8.2.4 betas.
Maybe upgrading will fix the problem.


- Kevin

John Oliver wrote:

> We run a slave zone for wiseowl.com  The last transfer we saw had a
> serial number of 2001042901  Since then, he's obviously made some sort
> of change, but we aren't getting the new zone (yes, he's updating his
> serial #!).  He's running the DNS server that comes with Windows NT
> (yes, I know... but it *was* working... :-) ).
>
> On my side, I see:
>
> May  3 16:31:51 ns named[8699]: rcvd NOTIFY(wiseowl.com, IN, SOA) from
> [207.110.31.70].3732
> May  3 16:31:51 ns named[8699]: NOTIFY(SOA) for zone already xferring
> (wiseowl.com)
>
> ...over and over again.
>
> On his side, he gets a godawful mess...
>
> http://www.john-oliver.net/dns.txt
>
> Can anyone decipher that MS gibberish and tell me what he needs to do to
> fix his zone?
>
> --
> John Oliver, System Administrator        http://www.allegiancetele.com
> ConnectNet, an Allegiance Telecom company    http://www.connectnet.com
> 6370 Lusk Blvd. Ste F103                                (858) 638-2020
> San Diego, CA. 92121                               FAX: (858) 623-1505