unable to map membership of 1 vm to a local DNS in Azure

Amit Mohanty 60 Reputation points
2024-04-01T06:33:49.81+00:00

H Team ,

I have created a 2 VM . 1st vm used as Local DNS server installed Active directory domain service in subnetA of a new virtual network app-network with public ip. Added a new forest (root domain name ) called cloud2hub.com and set it up .After that i relogged into 1st vm and could see 1st vm is part of domain cloud2hub.com .

2nd VM installed witout public ip in subnetB of virtual network app-network & installed internet information service.

Logged into 1st vm on edge browser opened 2ndvm.internal.cloudapp.net/Default.html able to see page .

Then logged into 1st vm and inside that tried RDP to 2nd vm using private ip and clicked on workgroup and tried to change membership to domain cloud2hub.com.

But its throwing below error. Please help

ERROR***

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 "cloud2hub.com":

The error was: "DNS server failure."

(error code 0x0000232A RCODE_SERVER_FAILURE)

The query was for the SRV record for _ldap._tcp.dc._msdcs.cloud2hub.com

Common causes of this error include the following:

  • The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:

168.63.129.16

  • One or more of the following zones contains incorrect delegation:

cloud2hub.com

com

. (the root zone)

Thanks & Regards,

Amit Mohanty

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,446 questions
0 comments No comments
{count} votes

Accepted answer
  1. TP 94,811 Reputation points
    2024-04-01T06:48:39.82+00:00

    Hi Amit,

    A) In Azure portal, please navigate to your domain controller VM -- click Network settings blade, next on right click on the network interface. Once on network interface page, click on the ipconfig on right and set the Private IP address to Static.

    B) In Azure portal, please navigate to your Virtual Network -- DNS servers blade. Select Custom, and enter the private IP address of your domain controller.

    C) Inside of your domain controller VM, open DNS Manager, on left right-click on the server name -- Properties. On Forwarders tab, add 168.63.129.16 address.

    D) Restart the second VM (so that DNS settings change will take effect) and then join it to domain

    Please click Accept Answer and upvote if the above was helpful. If something is unclear add a comment below.

    Thanks.

    -TP

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.