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
saikovvuri's avatar
saikovvuri
Icon for Microsoft rankMicrosoft
May 27, 2020

Great , very informative article. 

 

Referring to the scenario "5 OnPrem -> VPN -> Azure Private Link (Custom DNS)", you mention that by adding the forwarder to the Azure DNS 168.63.129.16,  requests to FQDN of sql server should be able to resolve. 

However if you review this post https://github.com/dmauser/PrivateLink/tree/master/DNS-Integration-Scenarios#4-on-premises-dns-integration,  it mentions that

  • we will still need a custom DNS server inside the Azure VNET .
  • custom DNS server inside Azure will have a forwarding rule to 168.63.129.16
  • The on-prem DNS server will have forwarder to the custom DNS server inside Azure vnet

 

just checking on what your thoughts are on this and whether just forwarding rule to 168.63.129.16 from on-prem DNS server will work.

 

Thanks