IMHO, it's simpler to shorten the DHCP lease time to something like 4 hours, update the scope or global options in DHCP to reflect the new DCs settings and let the two DCs coexist for a few days, then demote the old one.
Kurt On Thu, Apr 3, 2014 at 1:38 PM, Datum Guru <[email protected]> wrote: > Are there any negatives to adding a second IP address (in the same subnet) > to a single NIC on a domain controller? > > The theory is there will be a "DNS Server IP." This is the IP that will be > set as the DNS server on static assignments and what DHCP hands out. > > Example: > Assume AD integrated DNS and all domain controller have DNS installed. > The DNS Server IP: 192.168.1.5 > > Domain controller DC-1 has the IP 192.168.1.10 and the additional IP > 192.168.1.5. > > When I want to retire DC-1 I would promote a new domain controller DC-2 > which would have the IP 192.168.1.20. When both domain controllers have > fully replicated and are functioning correctly I would remove the second IP > (192.168.1.5) from DC-1 and add it as a second IP to DC-2. > > At this point there is still 2 domain controllers functioning but DNS > clients that are pointing to 192.168.1.5 are using the new DC-2. > > Demoting the first DC-1 should not negatively effect any device after that. > There is no moving IPs from computer to computer or renaming computers. > > I have done much googling and have not found an answer to this question. > This is not multi-homed, everything is on the same subnet, and there is only > 1 NIC in each DC. > > Thanks, >
