unable to join Azure VM to on-premise server

Question

Hello All,

I have created an Asure VM and connected it via Sonicwall site to site VPN to the local on prem physical server. I can ping both devices from each end.

when i try to join the VM to the physical server, i get the following error message.

An Active Directory Domain controller for the domain (physical server .local) could not be contacted. Ensure the domain name is typed correctly. If the name is correct, look at the details.

This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "hg19.local":

The error was: "DNS name does not exist."

(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.hg19.local

Common causes of this error include the following:

The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

8.8.8.8

192.168.1.5

One or more of the following zones do not include delegation to its child zone:

hgl19.local

local

zone

Accepted Answer

Hi Jamshid Javidi

As an original poster cannot accept their own answer, I am reposting it so that you can accept it an answer. Accepted answer will help other community members navigate to the appropriate solutions.

Issue: unable to join Azure VM to on-premise server

Solution: . I had to go to the VM networking interface and create a custom DNS pointing to the on-prem server.

If you have any further concerns, please do not hesitate to contact us.We are pleased to help you.

If the information is helpful, please click on "Upvote" and "Accept Answer" so that it would be helpful to other community members.

Answer

To connect your on-premises Windows Server 2016 (acting as the Primary Domain Controller) with an Azure VM that you want to set up as a second domain controller, you can indeed use a site-to-site VPN connection through your SonicWall router. This will allow your Azure VM to communicate with your on-premises network seamlessly.

Here are the steps to establish the connection:

Set Up a Site-to-Site VPN: Configure your SonicWall router to create a site-to-site VPN connection to your Azure virtual network. This will extend your on-premises network into Azure, allowing the Azure VM to access the on-premises domain controller.
Create an Azure Virtual Network: In Azure, create a virtual network that matches your on-premises network configuration. Ensure that the IP address ranges do not overlap.
Deploy the Azure VM: Create an Azure VM that will serve as the second domain controller. Ensure that it is configured to use the on-premises DNS server.
Join the Azure VM to the Domain: Once the VPN is established and the VM is running, you can join the Azure VM to your existing domain without disjoining the workstations. Use the domain credentials to join the VM to the domain.
Configure Domain Controller Roles: After joining the domain, promote the Azure VM to a domain controller using the Active Directory Domain Services role.

As for alternatives to a site-to-site VPN, you could consider using Azure ExpressRoute, which provides a private connection between your on-premises network and Azure. However, this is generally more expensive and may not be necessary for your setup.

References:

Share via

unable to join Azure VM to on-premise server

1 additional answer

Your answer