Re: Move DNS from Windows 2000 Server to 2003 Domain Controller

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm in a very similar situation. Two W2K member servers with DNS and
different W2K DCs. I have not DCPromo'd any W2K3 servers yet (I've read all
the Forest and Domain Prep Docs). Should install DNS on one my W2K DCs and
then switch it to integrated? Will this make the W2K3 DCPROMO process go
better? I want to end up only having integrated DNS on the W2K3 servers.

Thanks!

"Kevin D. Goodknecht Sr. [MVP]" wrote:

Ricky wrote:
Current Setup:
(2) W2K3 SP1 Domain Controllers (domain functional level - Windows
Server 2003)
(2) W2K SP4 Servers running WINS, DHCP, DNS
(~25) Various servers W2K SP4 and W2K3 SP1
(~600) XP SP2 Clients

I have recently gained 2 servers W2K3 SP1. I want to move and
upgrade our DHCP and WINS services to the 2 new servers and move our
DNS to our Domain Controllers (The W2K servers running WINS, DHCP,
DNS will be decomissioned). The goal is to have a fully integrated
DNS Domain. I have searched blogs, newsgroups, google, etc for
information on moving a 2000 DNS server to a Windows 2003 domain. I
have found articles that dance around the subject but I want to
elimate all reasonable pitfalls.

Here is one thought (right or wrong)
Install DNS on the 2003 Domain Controllers wait a few days (maybe a
week) for them to sync.

In all likelihood, your Win2k servers won't sync up with the Win2k3 DNS
servers, even if you wait a month.
THe only way zones from a Win2k DNS will replicate from Win2k to a Win2k3,
is if the Win2k3 servers are replica DCs in the same domain as the Win2k DC.

You will have to use a secondary zone on the Win2k3 to transfer the zone.


Then update my DHCP scopes to point the DNS ( Domain Controllers )

Turn off the DNS Services from the old W2K servers

What about the SOA?

The SOA record is of little importance to an Active Directory domain. The
SOA is mainly for secondary servers so they know when to update their zone
data.

An aside - Since I am moving and updating all 3 (DNS, DHCP and WINS)
should DNS be first? If not what would be the better option. Thanks
for any information.

Yes, get DNS done first.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================



.

Relevant Pages

  • Re: build now, join later
    ... admin rights in a child domain. ... instance configure DNS for failover, ... requires more than two dozen servers, ... them to create the child domain and their DCs with it, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Default SOA and NS records with Windows 2000 AD Integrated DNS
    ... Just for AD integrated zones? ... Are these DCs your domain controllers for your internal ... We already had DNS ... servers setup for AD I'm sure it just made sense at the time to ...
    (microsoft.public.windows.server.dns)
  • Re: Slow Logins and Slow Boot-up
    ... The DCs all have static IP, Each with DNS servers (pointing to themselves ... Clients have DHCP with DNS pointing to the 2 DCs in my main site. ... in Remote Site Hosted off site Email server -- Firewall site VPN ...
    (microsoft.public.windows.server.active_directory)
  • Re: I can not figure out why?
    ... I have two windows 2000 DCs and two Windows 2003 DCs. ... all workstations new DNS to point the new DNS through the DHCP server ... you must be careful when selecting the new servers to be DNS servers. ... If the zone is ...
    (microsoft.public.windows.server.active_directory)
  • Re: ad and dns setup
    ... To fully rebuild DNS: ... changes immediately to all servers, this helps to speedup the process. ... Make sure that the _msdcs zone exists and the scope is set to ... Point each DC to Dc01, clear cache in both DCs, delete everything inside ...
    (microsoft.public.windows.server.active_directory)