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/dns/private-dns-resiliency.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,6 @@ In this example:
24
24
- The private zone azure.contoso.com is linked to VNets in three different regions. Autoregistration is enabled in two regions.
25
25
- A temporary outage occurs in region A.
26
26
- Regions B and C are still able to successfully query DNS names in the private zone, including names that are autoregistered from region A (ex: VM1).
27
-
- Region B can add, edit, or delete records from the private DNS zone as needed.
28
27
- Service interruption in region A doesn't affect name resolution in the other regions.
29
28
30
29
The example shown here doesn't illustrate a disaster recovery scenario, however the global nature of private zones also makes it possible to recreate VM1 in another VNet and assume its workload.
0 commit comments