I inherited an environment like that once. I could not figure out a way to keep Windows from registering the second NIC in DNS, and got rid of that configuration as soon as I could. I don't remember having problems that I couldn't work around, but I never liked that setup and got rid of it as soon as I could. This was Server 2003 AD.
On Mon, Apr 7, 2014 at 5:36 PM, Datum Guru <[email protected]> wrote: > Those are all multihomed configurations. I was asking for 2 IP's in the > same subnet on the same NIC. > > I guess failing to find anything that discourages this configurations > means there are not negatives. > > Thanks, > > > > On Mon, Apr 7, 2014 at 4:03 PM, Kurt Buff <[email protected]> wrote: > >> Don't know if these still apply, but take a look at the referenced KB >> articles here: >> >> http://social.technet.microsoft.com/Forums/windowsserver/en-US/a1583d7f-fa59-4497-89de-666d683e53a0/can-dc-be-multihomed-in-windows-2008-server >> >> Kurt >> >> On Mon, Apr 7, 2014 at 1:02 PM, Datum Guru <[email protected]> wrote: >> > If everything was DHCP that would be ideal. What if there are many >> devices >> > that have static IP info assigned. >> > >> > Is there any known issues with multiple IP's on domain controllers? >> > >> > >> > >> > On Thu, Apr 3, 2014 at 3:47 PM, Kurt Buff <[email protected]> wrote: >> >> >> >> 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, >> >> > >> >> >> >> >> > >> >> >> >
