Skip to content

Commit dd08e89

Browse files
committed
docs: Add lightbox feature to DNS sharding images
1 parent bd45ae8 commit dd08e89

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

articles/dns/sharding-private-dns-zones.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,12 @@ A centralized private DNS zone might seem simpler during early adoption. However
2323

2424
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.
2525

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":::
2727

2828
> [!NOTE]
2929
> Sharding is an architectural pattern. Azure doesn't provide a built-in feature or toggle to enable sharding.
3030
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":::
3232

3333
**Figure 1: Flat private DNS zone linked to many virtual networks compared to a sharded design with zones segmented by ownership and environment**
3434

@@ -130,9 +130,9 @@ Sharding doesn't require new Azure features. Implement it by using existing Priv
130130

131131
- This approach is recommended for hub-and-spoke or hybrid architectures.
132132

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":::
134134

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":::
136136

137137
**Figure 2: Sharded private DNS zones with selective virtual network links and centralized resolution**
138138

0 commit comments

Comments
 (0)