Migrate windows 2003 dns to bind

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.

Any additional feedback? Important This section, method, or task contains steps that tell you how to modify the registry. Your options There are two different ways you can migrate your DNS to Windows Server —although one is definitely better than the other. Your available options are: Manually copying the zone data files Manually performing a zone transfer It is recommended that you manually initiate a zone transfer to transfer the zone data from the old server to the new Windows Server DNS server, as it usually results in fewer errors.

Should you decide to go ahead and manually copy the zone data files, you need to manually verify the integrity of the zones. As well, you cannot directly migrate to an Active Directory-integrated zone when you manually copy the zone data files—Active Directory-integrated zones do not use the standard zone data files that you would be able to copy from one location to another.

If you are currently using standard zones and your long-range goal is to move to Active Directory-integrated zones, you will be able to do so after migrating the zone data using either available method. But what does this really entail? What must you do ahead of time? You first should determine what type of DNS system you are migrating from. Is it a Windows NT 4. I am not sure if I need to do the netlogon? I want dynamic records to sent to the Bind servers right away, name resolve right away, etc… Not sure about netlogon if anyone knows better please feel free to provide input.

Your email address will not be published. Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. Apparently they are using 3U prehistoric servers running Ubuntu server 8.

I'll get to install 2x 1U servers with Ubuntu server 9. I'd always avoid using Webmin. For a seamless zero-downtime migration, do one machine at a time. If not copy your bind archive remotely to your new server. Since I'm right in the middle of migrating our servers to new hardware, I'll toss into the ring for this one. First, if at all possible, do not expose your master server the one where all the changes should occur to the internet.

Even if it means building a small VM session to host a hidden master, it makes moving stuff around and keeping it secure far easier. Once the new master server hopefully hidden is ready, you can very easily go in and modify the particular conf file to point to the new master and viola!