I've been working on setting up two Azure VMs where one will serve as the Forest and the other as a Replica for Active Directory. I've installed the necessary AD and DNS features on both VMs. On the Forest VM, I added a DNS zone and created a dummy record for corp.example.com, and everything seems to be working well. However, when I try to promote the Replica VM to become a domain controller, I encounter an error stating it can't connect to the domain corp.example.com. I've configured the Replica's NIC in Azure to point to the Forest's IP and set its DNS to do the same. Can anyone help me troubleshoot this issue? What might I be missing?
2 Answers
It sounds like the Replica might not be resolving the domain correctly. You mentioned using nslookup, but if that fails from the Replica, it might be why it can't connect. Ensure that the DNS settings are correctly pointing to the Forest's IP address. If you're seeing the Forest's IP when you perform the lookup, you're on the right track.
Also, you might want to check your firewall settings on Azure to ensure there's nothing blocking the connection.
When you promoted your Forest to be a domain controller, did you use corp.example.com or example.com as your root domain name? Also, try running an nslookup for your root AD domain from the Replica. Does it return the Forest's IP?
Just a tip for the future: instead of naming your DCs 'forest' or 'replica', consider something more straightforward like DC1 and DC2 to avoid any confusion.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures