Skip to content

Commit 40a43ca

Browse files
Merge pull request #286640 from greg-lindsay/dns-upd
Update TXT record info
2 parents a831cc3 + a45444f commit 40a43ca

File tree

4 files changed

+6
-8
lines changed

4 files changed

+6
-8
lines changed

articles/dns/dns-reverse-dns-for-azure-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: dns
55
author: greg-lindsay
66
ms.service: azure-dns
77
ms.topic: how-to
8-
ms.date: 08/12/2024
8+
ms.date: 09/11/2024
99
ms.author: greglin
1010
ms.custom: devx-track-azurepowershell, devx-track-azurecli
1111
---
@@ -241,7 +241,7 @@ No. Azure supports a single reverse DNS record for each Azure Cloud Service or P
241241

242242
### Can I configure reverse DNS for IPv6 PublicIpAddress resources?
243243

244-
Yes. See [Azure support for reverse DNS](/azure/dns/dns-reverse-dns-overview#azure-support-for-reverse-dns).
244+
No. Azure DNS does not currently support reverse DNS (PTR records) for public IPv6 addresses.
245245

246246
### Can I send emails to external domains from my Azure Compute services?
247247

articles/dns/dns-reverse-dns-hosting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to use Azure DNS to host the reverse DNS lookup zones for
44
author: greg-lindsay
55
ms.service: azure-dns
66
ms.topic: how-to
7-
ms.date: 06/07/2024
7+
ms.date: 09/12/2024
88
ms.author: greglin
99
ms.custom: devx-track-azurepowershell, devx-track-azurecli
1010
ms.devlang: azurecli

articles/dns/dns-reverse-dns-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ manager: KumuD
66
ms.service: azure-dns
77
ms.topic: concept-article
88
ms.custom:
9-
ms.date: 06/10/2024
9+
ms.date: 09/12/2024
1010
ms.author: greglin
1111
---
1212

articles/dns/dns-zones-records.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.assetid: be4580d7-aa1b-4b6b-89a3-0991c0cda897
66
ms.service: azure-dns
77
ms.topic: concept-article
88
ms.custom: H1Hack27Feb2017
9-
ms.date: 11/21/2023
9+
ms.date: 10/30/2024
1010
ms.author: greglin
1111
---
1212

@@ -100,9 +100,7 @@ The DNS standards permit a single TXT record to contain multiple strings, each o
100100

101101
When calling the Azure DNS REST API, you need to specify each TXT string separately. When you use the Azure portal, PowerShell, or CLI interfaces, you should specify a single string per record. This string is automatically divided into 255-character segments if necessary.
102102

103-
The multiple strings in a DNS record shouldn't be confused with the multiple TXT records in a TXT record set. A TXT record set can contain multiple records, *each of which* can contain multiple strings. Azure DNS supports a total string length of up to 4096 characters`*` in each TXT record set (across all records combined).
104-
105-
`*` 4096 character support is currently only available in the Azure Public Cloud. National clouds are limited to 1024 characters until 4k support rollout is complete.
103+
The multiple strings in a DNS record shouldn't be confused with the multiple TXT records in a TXT record set. A TXT record set can contain multiple records, *each of which* can contain multiple strings. Azure DNS supports a total string length of up to 4096 characters in each TXT record set (across all records combined).
106104

107105
## Tags and metadata
108106

0 commit comments

Comments
 (0)