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-integration.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,7 @@ In a hub-and-spoke topology, a common scenario allows the creation of private DN
212
212
213
213
> [!NOTE]
214
214
> - Each DNS zone group can support up to five DNS zones.
215
+
> - Each DNS zone group can include only one private DNS zone per DNS zone name. For example, you can't associate more than one private DNS zone resource for `privatelink.blob.core.windows.net` to the same DNS zone group.
215
216
> - Adding multiple DNS zone groups to a single Private Endpoint isn't supported.
216
217
> - Delete and update operations for DNS records can be seen performed by **Azure Traffic Manager and DNS.** This is a normal platform operation necessary for managing your DNS Records.
0 commit comments