From my understanding, DC1 should be pointing at DC2 as Primary DNS with its secondary DNS as 127.0.0.1 while DC2 points to DC1 as primary DNS with 127.0.0.1 in the secondary.
It really depends. If dc1 has to keep polling dc2 as the primary then there is a delay. If it points to itself then you don’t have as delay. When you have 100 users it doesn’t matter. But when you served 50k users you will see a difference
Mr. Salmon!!!! OMG How long has it been buddy. I will hit you up on Facebook as well. I just now turned back on my entire infrastructure at home. I needed this video cause I wanted to implement and try out some replication. Perfect follow along. Thanks buddy! Am I god awful or what? I have a main domain controller, this one with replication, nagios server (centos), 3 workstations, fog project server (imaging) and my main DC is running also WDS. Am I just a tad crazy...or that bored :)
the DNS should be set to the two DCs. example primary DNS will be DC1, and Secondary DNS will be IP of DC2. the goal is to allow for the client to hit either DNS if necessary.
@@PopoyTanke one issue is is DC1 online? can you ping it from DC2? I am assuming you are trying to promote DC2 and that's when your getting the error. Let me know if that's the case.
