Hi all,

I have 2 DC's in a site that need IP's to be updated to reflect network changes.

Both DC's are DNS servers (ADI), DHCP servers (with manual redundant scopes, which are not changing). Each point to themselves for DNS and the other for secondary, with forwarding enabled to the forest root DNS servers.

Here's my plan:

On DC2:

  1. Change the primary (P) DNS server to point to DC1 and secondary (S) to itself
  2. Change all IP configuration (to reflect new IP segment & physically move the cable) 
  3. Test connectivity (pinging loopback adapter, IP, GW etc.)
  4. Flush the DNS resolver cache
  5. Re-register DNS names
  6. Check DNS entry for DC2 on DC1's DNS server
  7. Test name resolution on DC1 and subsequently DC2
  8. Change the P & S DNS server settings to point to itself and its replication partner or DC2
  9. Bounce the DNS and Netlogon services on DC2
  10. Check DNS entry on DC2 to verify correct name to IP entry (for DC2)
  11. Test name resolution on DC2 
  12. Change the DHCP client parameters (to reflect new DNS server and DHCP server) on both DC1 and DC2, restart DHCP server service on DC2
  13. Update secondary zone transfers for forest-wide locator records on master server (DC1)
  14. Repeat steps for DC1 when DC2 is operational with new IP configuration, except for few different things like master server for DC1 (for secondary zone transfers etc.)
I am just trying to verify my steps and see if I'm missing anything or any gotchas before proceeding...
 
Thanks,
List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to