The Forefront TMG and ISA Server Forum can be found at htp://social.technet.microsoft.com/Forums/en/Forefrontedgegeneral/. Ace Fekay, who holds several certifications including MVP, MCT, MCITP/EA, and MCTS Windows 2008/R2 & Exchange 2007, can be found on his technical blogs and videos at http://www.delawarecountycomputerconsulting.com/. Please note that this post is provided as-is and confers no rights or guarantees. In regards to Solution 2, I agree with Mr X’s suggestion to review ISA, antivirus software, and/or Windows Firewall configurations.
As I am configuring a new domain on Azure boxes, which I have never done before, I am encountering communication issues that are causing me a lot of frustration. It’s worth noting that I am using traditional AD over Azure, not AAD. Despite my efforts, this has been an ongoing challenge for several days now.
The server for DC is VT-EDD while the domain is named VT-EDD.local. Additionally, the client is VT-EDD-IIS1, and resolving this issue will solve any potential issues with other clients in the future.
I added the IP for the DC and domain to the client’s host file to enable me to ping the server. Additionally, I updated the client’s DNS.
Despite my attempts to join the domain, I continue to encounter difficulties.
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 "VTT-EDD.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.VTT-EDD.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:
- One or more of the following zones do not include delegation to its child zone:
. (the root zone)
While I am able to successfully ping the domain and the DC by both IP and name, I am facing difficulties in joining it.
Upon setting up an ADDC in Azure, connecting the server to it, and including the DC’s IP in Azure’s DNS, I successfully finalized the procedure.