Skip to content

Commit 857b8cd

Browse files
Merge pull request #313687 from asudbring/dns-faq-patch
Add auto-registration FAQ entries and fix duplicate image in DNS docs
2 parents 5dfac45 + ac5275f commit 857b8cd

2 files changed

Lines changed: 14 additions & 6 deletions

File tree

articles/dns/dns-faq.yml

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
author: asudbring
77
ms.service: azure-dns
88
ms.topic: faq
9-
ms.date: 09/23/2024
9+
ms.date: 03/25/2026
1010
ms.author: allensu
1111
title: Azure DNS FAQ
1212
summary: |
@@ -225,6 +225,19 @@ sections:
225225
Internationalized domain names (IDNs) encode each DNS name by using [Punycode](https://en.wikipedia.org/wiki/Punycode). DNS queries are made by using these Punycode-encoded names.
226226
227227
To configure IDNs in Azure DNS, convert the zone name or record set name to Punycode. Azure DNS doesn't currently support built-in conversion to or from Punycode.
228+
229+
- question: |
230+
What happens to auto-registered DNS records if I disable auto-registration on a virtual network link?
231+
answer: |
232+
Disabling auto-registration on an existing virtual network link immediately deletes all DNS records that were automatically registered through that link. Virtual machine records will be deleted and will only be available if they are manually re-created or auto-registration is re-enabled in the virtual network link settings.
233+
234+
> [!WARNING]
235+
> The records are permanently deleted. Use caution when modifying auto-registration settings on an existing virtual network link.
236+
237+
- question: |
238+
Can I recover auto-registered DNS records after they have been deleted?
239+
answer: |
240+
Auto-registered DNS records that have been deleted cannot be restored.
228241
229242
additionalContent: |
230243

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

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -128,11 +128,6 @@ Sharding doesn't require new Azure features. Implement it by using existing Priv
128128

129129
- This approach is recommended for hub-and-spoke or hybrid architectures.
130130

131-
:::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":::
132-
133-
:::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":::
134-
135-
**Figure 2: Sharded private DNS zones with selective virtual network links and centralized resolution**
136131

137132
## When to use sharding
138133

0 commit comments

Comments
 (0)