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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,12 +23,12 @@ 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.":::
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
27
28
28
> [!NOTE]
29
29
> Sharding is an architectural pattern. Azure doesn't provide a built-in feature or toggle to enable sharding.
30
30
31
-
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-flat-architecture.png" alt-text="Screenshot of sharded private DNS zones design with zones segmented by ownership and environment.":::
31
+
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-flat-architecture.png" alt-text="Screenshot of sharded private DNS zones design with zones segmented by ownership and environment." lightbox="media/sharding-private-dns-zones/dns-shard-flat-architecture.png":::
32
32
33
33
**Figure 1: Flat private DNS zone linked to many virtual networks compared to a sharded design with zones segmented by ownership and environment**
34
34
@@ -130,9 +130,9 @@ Sharding doesn't require new Azure features. Implement it by using existing Priv
130
130
131
131
- This approach is recommended for hub-and-spoke or hybrid architectures.
132
132
133
-
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-central-resolution.png" alt-text="Screenshot of sharded private DNS zones with selective virtual network links and centralized resolution.":::
133
+
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-central-resolution.png" alt-text="Screenshot of sharded private DNS zones with selective virtual network links and centralized resolution." lightbox="media/sharding-private-dns-zones/dns-shard-central-resolution.png":::
134
134
135
-
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-central-resolver.png" alt-text="Screenshot of sharded private DNS zones architecture with centralized resolution.":::
135
+
:::image type="content" source="media/sharding-private-dns-zones/dns-shard-central-resolver.png" alt-text="Screenshot of sharded private DNS zones architecture with centralized resolution." lightbox="media/sharding-private-dns-zones/dns-shard-central-resolver.png":::
136
136
137
137
**Figure 2: Sharded private DNS zones with selective virtual network links and centralized resolution**
0 commit comments