Resolve Azure and on-premises DNS for Domain Controllers on both sides

Twumasi Yeboah Jr 25 Reputation points
2023-10-20T19:49:12.75+00:00

I am trying to join a domain controller in Azure to a Domain Controller on-premises. I have created a vpn and it's working. I have tried to resolve DNS in all ways I could think of, but to no avail. I've looked this up in many resources, but found nothing. Is there anyone here who has been successful with running On prem DC with in Azure DC? Please advise.

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
631 questions
Microsoft Entra
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,529 questions
0 comments
Accepted answer
  1. Anonymous
    2023-10-23T12:40:35.6633333+00:00

    main DC and the problem one are on different subnets so how are they going to have static ips from the same network?

    They wouldn't but they must both use the same static ip address of domain controller listed for DNS and no others such as router or public DNS. Also check the required ports are flowing between networks.

    https://video2.skills-academy.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts#windows-server-2008-and-later-versions

    --please don't forget to close up the thread here by marking answer if the reply is helpful--

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-20T20:01:23.17+00:00

    If you have two disconnected domain controllers then even if the domain names are the same they are in fact different domains so you would not be able to join them after the fact. The correct method would be to join an existing domain and then do the promo.

    Make sure the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS. Also check the required ports are flowing between networks.

    https://video2.skills-academy.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts#windows-server-2008-and-later-versions

    --please don't forget to close up the thread here by marking answer if the reply is helpful--