How to resolve SQL Failover Group FQDN from Azure ADDS joined VM

Ajeet Singh 71 Reputation points
2023-05-02T04:34:56.1833333+00:00

Hi,

Given below is my setup:

VNet A: Hosts Azure ADDS endpoints in a subnet and a DNS Controller for the same in other Subnet

VNet B: Peered to VNet A and domain joined with Azure ADDS endpoints. It also has DNS Server settings pointing to VNetA for Domain authentication to VMs. This also has a private endpoint to sql serverA which is connected to SQL serverB (In different Vnet and different region) using failover groups.

Problem is that when i try to access the failover group FQDN it doesnt get resolved. I tried Private DNS resolver but it takes long to resolve the private IP and almost 50% of times my connection breaks to the SQL server via its failover group fqdn.

Whats the best way to achive this?

Thanks

Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
480 questions
{count} votes

Accepted answer
  1. KapilAnanth-MSFT 38,046 Reputation points Microsoft Employee
    2023-05-03T09:55:22.9333333+00:00

    @Ajeet Singh

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I see you have to resolve "failover group FQDN" and is failing.

    I suggested the following questions/checklist.

    • From where are you trying to resolve the FQDN?
    • From VNetA or VnetB
    • What do you mean by "failover group FQDN"?
    • Is it the FQDN of the Private EndPoint of a secondary SQL Server?
    • If so, do you have the Private DNS Zone integrated with the VM's VNet from where you are trying to resolve to?
    • In case of a custom DNS server, the Private DNS Zone must be integrated to the Vnet that is hosting the DNS server (VnetA)
    • Did you check if the Private DNS Zone that is integrated to the VNet has an entry for the secondary SQL Database?

    You informed, your private DNS Zone wasn't linked to the Domain Server (AADDS) VNet and this was the issue.

    Thanks,

    Kapil


    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments No comments

0 additional answers

Sort by: Most helpful