Skip to content

Commit 083d18c

Browse files
authored
Update incorrect CRUD operation
1 parent fe91c2f commit 083d18c

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

articles/dns/private-dns-resiliency.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ In this example:
2424
- The private zone azure.contoso.com is linked to VNets in three different regions. Autoregistration is enabled in two regions.
2525
- A temporary outage occurs in region A.
2626
- 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.
2827
- Service interruption in region A doesn't affect name resolution in the other regions.
2928

3029
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

Comments
 (0)