You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/private-link/private-endpoint-dns.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: private-link
5
5
author: asudbring
6
6
ms.service: private-link
7
7
ms.topic: conceptual
8
-
ms.date: 03/07/2023
8
+
ms.date: 05/26/2023
9
9
ms.author: allensu
10
10
ms.custom: fasttrack-edit
11
11
---
@@ -30,6 +30,7 @@ You can use the following options to configure your DNS settings for private end
30
30
> Existing Private DNS Zones tied to a single service should not be associated with two different Private Endpoints as it will not be possible to properly resolve two different A-Records that point to the same service. However, Private DNS Zones tied to multiple services would not face this resolution constraint.
31
31
32
32
## Azure services DNS zone configuration
33
+
33
34
Azure creates a canonical name DNS record (CNAME) on the public DNS. The CNAME record redirects the resolution to the private domain name. You can override the resolution with the private IP address of your private endpoints.
34
35
35
36
Your applications don't need to change the connection URL. When resolving to a public DNS service, the DNS server will resolve to your private endpoints. The process doesn't affect your existing applications.
@@ -104,7 +105,9 @@ For Azure services, use the recommended zone names as described in the following
<sup>1</sup>To use with IoT Hub's built-in Event Hub compatible endpoint. To learn more, see [private link support for IoT Hub's built-in endpoint](../iot-hub/virtual-network-support.md#built-in-event-hubs-compatible-endpoint)
110
113
@@ -149,6 +152,8 @@ For Azure services, use the recommended zone names as described in the following
>In the above text, `{region}` refers to the region code (for example, **eus** for East US and **ne** for North Europe). Refer to the following lists for regions codes:
@@ -195,6 +200,8 @@ For Azure services, use the recommended zone names as described in the following
<sup>1</sup>To use with IoT Hub's built-in Event Hub compatible endpoint. To learn more, see [private link support for IoT Hub's built-in endpoint](../iot-hub/virtual-network-support.md#built-in-event-hubs-compatible-endpoint)
0 commit comments