question

KeiMoon-3644 avatar image
0 Votes"
KeiMoon-3644 asked ·

Unable to join to the domain

I have a vNet, say vNet_1, with AADDS. Then I created another vNet, say vNet_2, and peering it to the vNet_1. I thought I could join my server in vNet_2 to the domain, which exists already. But I am getting "AD Domain Controller could not be contacted" error. I thought peering would solve the issue because when I created a VM in vNet_1, joining to the domain worked without any issue. I am new to Azure, there must be something that I am not thinking correctly.

azure-ad-domain-services
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AndreasBaumgarten avatar image
0 Votes"
AndreasBaumgarten answered ·

Hi @KeiMoon-3644 ,

If you login in a VM in the vNet_2 subnet are you able to successfully ping your domain name of AADDS?
or instance ping yourdomain.org?
The error message points to the fact the VM can't "find" the domain to join.

Which DNS Server is configured in the vNet_1? Which DNS Server is configured in vNet_2?

Maybe this helps:
https://docs.microsoft.com/de-de/azure/active-directory-domain-services/tutorial-configure-networking#configure-dns-servers-in-the-peered-virtual-network


(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.