Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 354
  • Last Modified:

IP address swap from a primary DNS and WINS server to a new Windows 2008 R2 domain controller

I'll be going through a procedure to swap the IP address of our primary DNS and WINS server (windows 2003) over to one of our new windows 2008 R2 DCs.  This server is also a DFS namespace server.  Only the IP address will be moved over.  I've come up with some steps below that I could use some feedback on.  

1) Change the IP of the primary DNS and reboot
2) Check that the DNS SRV records have been updated to the new IP addresses
3) Give the new w2k8 DC the address that the primary DNS server had and reboot
4) Check that the DNS SRV records have been updated to the new IP addresses
5) Test: ping, nslookup, connectivity, authentication, replication, etc...
6) After a few days, power off the old primary DNS server for a week, then power on, demote and decommission

Some of the questions I have are:
Are there any glaring problems with doing this?
Will it be alright to do the IP changes and reboots in quick succession without waiting for DNS and replication to fully go through for each server change?
Any specific tests or utilities that would be good for verification?
Anything special for our Exchange system?
0
mbromb
Asked:
mbromb
  • 3
  • 2
1 Solution
 
Chris DentPowerShell DeveloperCommented:

2 and 4. Only the Host (A) Record, SRV records link back to the host name.

I'd add run "ipconfig /flushdns" on any other DCs and Exchange so they get the change immediately rather than waiting for the DNS record TTL to time-out.

There shouldn't be a problem changing the IP in quick succession.

DCDiag and the Event Logs should do for monitoring this change.

Chris
0
 
mbrombAuthor Commented:
Thanksfor quick reply!

To clarify, I only have to check that the A records are changed, and all else will be the same in DNS?

0
 
Chris DentPowerShell DeveloperCommented:

You should find that all SRV records and the CNAME under _mdsc link back to the server name.

The IP address is used for these records only:

"same as parent folder" - The domain name itself
DomainDnsZones subfolder - Lets you know which servers host the DomainDnsServers zone
ForestDnsZones subfolder - As above for ForestDnsZones
gc._msdcs.yourdomain.com - Global Catalog Host (A) records

If you can bring the old server onto its new IP and have it correct its own entries first (ipconfig /registerdns and restart netlogon) it will simplify matters, however if you can't it will still cope and figure it all out.

Chris
0
 
mbrombAuthor Commented:
ok.  I see what you're talking about.  I'll be assigning the new IP to the primary DNS server and rebooting to be thorough.  That will take care of the registration and netlogon service.  I'll do the same when moving the IP over to the new DC.  I'll let replication go through, check DNS records and flush DNS for the DCs and Exchange servers.

Thanks!
0
 
mbrombAuthor Commented:
Thank You!
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now