Need to transfer a zone from BIND 4.x to Win2k standard primary DNS server

[Joseph S D Yao]

On Thu, Jul 12, 2001 at 08:44:00AM +1000, Mark.Andrews at nominum.com wrote:
> > However, he must list your server as a slave server, or (a) you will
> > never receive NOTIFYs of changes to the zone [and so will only upodate
> > when the zone expires],
> 
> 	This is hogwash unless there are insane SOA timer values.  The
> 	server will just revert to using the old refesh/retry alogrithm.

Yah, I treated that too hastily, didn't I?  The slave server does check
every REFRESH seconds to see whether the SERIAL in the SOA has changed;
if so, it initiates a transfer.  If the check fails, the slave server
tries again every RETRY seconds.  If no zone change has occurred [per
the serial number] in EXPIRE seconds, a zone transfer is done anyway.
Cf. RFC 1034 et al.

I don't know why I was thinking of totally static zones.  ;-(

Anyway, I realized later that he is swapping his old AIX/BIND 4.x DNS
master for a new MSW2K/MS DNS master, not adding a slave.  But he can
transfer the zones over by making the new guy act like a slave at
first, then telling it that it is now the master.  At least, using BIND
he could; I don't know about MS DNS, perhaps there is another mailing
list or newsgroup in support of that.  Also, the post-transfer format
of a zone file is ugly[1] under BIND; I have no idea what the internal
representation is for MS DNS.

There is a version of BIND available for MSW-NT; I don't know whether
it runs or works on MSW2K.

[1] Your standards may differ; but slave/zone.* does not meet my
aesthetic needs.  ;-)

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
OSIS Center Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.