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.
484 questions
ASR replication with private endpoints
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 49%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMJ%3C/text%3E%3C/svg%3E)
Morgan Jones
1
Reputation point
I have had success creating private endpoints on the azure file sync service. I'm running into issues getting it set up for Azure Site Recovery.
Created the endpoint through the portal. Included azure privatelink dns zone.
My azure DNS servicer has a conditional forwarder for siterecovery.windows.azure.com to 168.63.129.16
When I do NS lookup from this DNS server I get a Non-existent domain error.
When I do NS lookup like this: nslookup siterecovery.windowsazure.com 168.63.129.16 I get the same Non-Existent domain error.
I'm expecting to see the private IP and the name myvaultname.wus2.siterecovery.windowsazure.com when I do the NSlookup.
It seems that siterecovery.windowsazure.com comes back as a non-existent domain from the Azure DNS service.
Other services such as file.core.windows.net resolve just fine from the same DNS service. I have replicated this in two different environments.
{count} votes
-
SadiqhAhmed-MSFT 40,446 Reputation points Microsoft Employee2020-11-04T13:33:03.997+00:00 @Morgan Jones , thank you for posting your query on Microsoft Q&A forum!
How does your DNS infrastructure looks like? Hub and spoke topology? Is your DNS either on-prem or azure vm based? Did you enable manage identity? Is your environment compliance with the pre-requisites?
https://video2.skills-academy.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints -
Morgan Jones 1 Reputation point
2020-11-04T19:28:30.28+00:00 I have replicated this in a single VNET as well as in a hub and spoke. Using Azure VM based DNS. Managed Identity and meet all the pre reqs. The built in Azure DNS resolver does not resolve siterecovery.windowsazure.com
Linking the basic setup guide does not resolve the issue or provide a path forward to a solution.
-
SadiqhAhmed-MSFT 40,446 Reputation points Microsoft Employee
2020-11-05T18:55:46.43+00:00 @Morgan Jones Can you provide a diagram of how you have DNS configured?
Please include the Azure private DNS zones and the DNS forwarders in Azure and also including the vnet links you have configured from the private DNS zone?
Sign in to comment