Moving DNS to New Server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All,
I'm looking to retire an old Win2K DC running DNS. It's hosting my
single ADI zone. I've set up a new server as a DC. I was going to
follow the MS KB Article which says convert the zone to Standard, copy
the zone files and move the zones registry key, etc.

I followed a similar KB article and moved DHCP with no problem,
including exporting and importing the registry key. However, I
discovered that I don't have a Zones sub-key at the path indicated in
the article. One of the threads in this group said to copy this:
HKLM/SYSTEM/CCS/Services/DNS key

rather than this:

HKLM/SYSTEM/CCS/Services/DNS/Zones

which is in the KB article.

Will that work for me?

Another thread pointed out that an ADI zone will replicate to any DNS
server running on a DC. I installed and started DNS on the new server,
and I see that it has replicated.

Can I just update the IP address on the new server to match the old
one, so that I don't have to update my DHCP server and make my DHCP
clients reboot?

Thanks,

-jb

Jonathan Sherry
Classic Media
(e-mail address removed)
 
Hi All,
I'm looking to retire an old Win2K DC running DNS. It's hosting my
single ADI zone. I've set up a new server as a DC. I was going to
follow the MS KB Article which says convert the zone to Standard, copy
the zone files and move the zones registry key, etc.

I followed a similar KB article and moved DHCP with no problem,
including exporting and importing the registry key. However, I
discovered that I don't have a Zones sub-key at the path indicated in
the article. One of the threads in this group said to copy this:
HKLM/SYSTEM/CCS/Services/DNS key

rather than this:

HKLM/SYSTEM/CCS/Services/DNS/Zones

which is in the KB article.

Will that work for me?

Another thread pointed out that an ADI zone will replicate to any DNS
server running on a DC. I installed and started DNS on the new server,
and I see that it has replicated.
Click to expand...

GeeWiz :) all this explaining to get to a virtually unrelated question?
Can I just update the IP address on the new server to match the old
one, so that I don't have to update my DHCP server and make my DHCP
clients reboot?
Click to expand...

Can you move the IP? Yes, but that would be changing the IP address of a DC
which may be more of a headache than you would want.
This may lead to needing to reboot the DC and fixing DNS registrations for
both DCs before you demote the first DC.
It may be a simpler solution to update the DHCP scope and have the clients
reboot over the weekend and leave the first DC up until you have verified
that all clients are using the new DC. You are going to need to move the
Global Catalog and transfer the FSMO roles before you can demote the old DC
and remove it, and I would make sure the new DC is running without errors
before you do this. So it should give you plenty of time to push the new DNS
IP out to the clients.
 
Kevin brings up some good points, I go into some details on these side
issues.

http://www.pbbergs.com
Select articles and select the article decommissioning a dc

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks guys, this is great info. One piece I left out: the new DC is
actually DC #3, and I'm decomissioning DC #1.

I seem to be in good shape:
All the roles except schema owner already reside elsewhere.
DC#1 no longer has Global Catalog.
DHCP already migrated.

Paul recommends installing DNS before promoting the DC. I did it the other
way, but I'm still seeing my Zone. This should mean I'm good to go, right?

Since I've dawdled a bit, I'll just do the switch before my building-wide
power outtage this weekend (infrastructure upgrades). I shouldn't even be
chasing down laggards on Monday.

Thanks guys!

-jb
 
Back
Top