Making Windows the new master of an existing DNS zone

[pxeboot]

What is the best method for making a Windows 2003 server the NEW master
of a zone that is presently being held by a Linux BIND server?

I'm thinking that first I make Win2k3 server the slave DNS for that
zone, do a zone transfer from BIND server, then promoting it to
primary/master. Then make BIND server the new slave for that zone.

Your thoughts?

 

[Kevin D. Goodknecht Sr. [MVP]]

What is the best method for making a Windows 2003 server the NEW
master of a zone that is presently being held by a Linux BIND server?

I'm thinking that first I make Win2k3 server the slave DNS for that
zone, do a zone transfer from BIND server, then promoting it to
primary/master. Then make BIND server the new slave for that zone.

You've got the idea, for best results you'll need to make sure NS records
and the SOA Primary Name Server is correct, resolves, with correct refresh,
retry, expire values and of course zone transfers are allowed to the BIND.

 

[pxeboot]

I assume that Windows will take care of changing the NS and SOA records
automatically after promotion or do I have to make these changes
manually?

 

[Kevin D. Goodknecht Sr. [MVP]]

I assume that Windows will take care of changing the NS and SOA
records automatically after promotion or do I have to make these
changes
manually?

It will if the zones are AD integrated standard Primary zones you'll have to
edit the SOA. Which is pretty easy to do with the DNS management console,
compared to BIND where you have to edit the zone file. All new zones will
have the machine's DNS name as the SOA Primary.