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/sharding-private-dns-zones.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,6 @@ A centralized private DNS zone might seem simpler during early adoption. However
23
23
24
24
Sharding mitigates this risk by ensuring DNS changes are scoped to a clearly defined set of workloads and virtual networks. Each zone represents an ownership or operational boundary, reducing unintended impact across unrelated services.
25
25
26
-
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-flat-diagram.png" alt-text="Screenshot of flat private DNS zone linked to many virtual networks compared to a sharded design with zones segmented by ownership and environment." lightbox="media/sharding-private-dns-zones/dns-shard-flat-diagram.png":::
27
-
28
26
> [!NOTE]
29
27
> Sharding is an architectural pattern. Azure doesn't provide a built-in feature or toggle to enable sharding.
0 commit comments