+ 0 Votes Bad idea bart777 6 years ago Per Microsoft you never want to have a multihomed DC. As you can see you get all kids of wierd issues not to mention the event log errors. Now, that being said, your main problem is that both servers are DCs. Since they are both performing this function you need to have them in DNS or replication may get a bit flakey. Really your best solution would be to either retire that 2nd DC or fix the application so that it doesn't talk to the 2nd server at all. Unless the app is trying to edit something in AD it shouldn't be bouncing around anyway. Perhaps a better idea would be to set up an alias for the app to look to and give that alias it's own DNS entry. You can then control where it points to. In the event that server1 has issues you can change DNS to point the alias to the 2nd box. This is the way I would go. I prefer having 2 DCs in the network just for my own sanity. With your current config the 2nd server would never kick in unless you were to manully move the cable. Good Luck + 0 Votes NO Jimmy Chow 4 years ago Don't use 2 DC in one network. Use primary DC and backup DC. + 0 Votes NO Jimmy Chow 4 years ago Don't use 2 DC in one network. Use primary DC and backup DC.