IXFR problem BIND master to Win/DNS slave

[Treptow, Craig]

I think this is resolved with BIND 8.2.2-p7.  Look for a message on this list from davem408 at my-deja.com on 11/17/2000 regarding this.

-----Original Message-----
From: Karma Crayona [mailto:karmac at my-deja.com]
Sent: Monday, December 04, 2000 8:53 AM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: IXFR problem BIND master to Win/DNS slave


I've run into the problem with Win2K slave nameserver not accepting AXFR
from the BIND master in response to requests for IXFR, aka event 6524.
This appears to be a known problem documented at the MS support site
http://support.microsoft.com/support/kb/articles/Q260/0/21.ASP without
any mention of a resolution.

To try to work around this, I've enabled IXFR from the
Solaris7/BIND8.2.2p5 master to the Win2K/DNS slave with no success.
The BIND named.conf file has the following statements:

  option { maintain-ixfr-base yes; };

  server 10.25.181.53;
    support-ixfr yes;
  };

  zone "CorpusCristie.com" in {
    type master;
    file "CorpusCristie.zone";
    allow-transfer { 10.25.181.53; };
    ixfr-base "log/10-25-181-53.ixfr";
  };

Still, the Win2K/DNS box keeps sending IXFR requests every 2 minutes,
and the Solaris7/BIND box keeps responding with AXFR which is again
ignored.  What am I missing that would make BIND respond with the
requested IXFR?

Also, given that making the Win2K machine the master is not an option
for political reasons, does anyone know if there is a patch for either
WinDNS or BIND that resolves this problem?

Thanks in advance,

--
Karma C.


Sent via Deja.com http://www.deja.com/
Before you buy.