Blog Post

Azure Database Support Blog
10 MIN READ

Azure SQL DB Private Link / Private Endpoint - Connectivity Troubleshooting

FonsecaSergio's avatar
FonsecaSergio
Icon for Microsoft rankMicrosoft
Apr 06, 2020
In the article Azure SQL DB Connectivity Troubleshooting we have explored regular connectivity troubleshooting to Azure SQL DB, on this one we will explore connectivity troubleshooting using Private ...
Updated Aug 06, 2021
Version 20.0
azure sql
Connectivity
Private Endpoint
Private Link
FonsecaSergio's avatar
FonsecaSergio
Icon for Microsoft rankMicrosoft
Oct 19, 2020

KMS2222 the instructions can be found at https://techcommunity.microsoft.com/t5/azure-sql/using-failover-groups-with-private-link-for-azure-sql-database/ba-p/1272902

 

But considering what you said the problem could be related to DNS Name and TTL (Time to Live)... When you get a DNS registry it will be valid for usually 1h. If client is a VM you could do a IPCONFIG /flushdns... If webapp, a service restart probably may do the trick, or just need to wait for the TTL.

 

You can validate it using Kudu on WebApp and trying to check name resolution NSLOOKUP failoverserver.database.windows.net. It should point first to one region gateway, then to other one. Here is a sample of a NSLOOKUP I done on my failover name... You can see that currently lead to West Eu

 

nslookup failover.database.windows.net

Non-authoritative answer:
Name: westeurope1-a.control.database.windows.net
Address: 40.68.37.158
Aliases: failover.database.windows.net
primary.database.windows.net
primary.privatelink.database.windows.net