Skip to content

Commit e720944

Browse files
Merge pull request #301737 from netapp-manishc/patch-37
Update domain-name-system-concept.md
2 parents 4b5f4da + 4c7c1ee commit e720944

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-netapp-files/domain-name-system-concept.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: whyistheinternetbroken
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 01/29/2025
8+
ms.date: 06/24/2025
99
ms.author: anfdocs
1010
---
1111
# Understand Domain Name Systems in Azure NetApp Files
@@ -485,7 +485,7 @@ Ensure you meet the following DNS configuration requirements:
485485
- If a DNS alias is required, use a CNAME record. Point the CNAME record to the A/AAAA records for Azure NetApp Files.
486486
- If you're not using dynamic DNS updates, you must manually create an A record and a PTR record for the AD DS computer accounts created in the AD DS Organizational Unit (specified in the Azure NetApp Files AD connection) to support Azure NetApp Files LDAP Signing, LDAP over TLS, SMB, dual-protocol, or Kerberos NFSv4.1 volumes.
487487
- For complex or large AD DS topologies, [DNS Policies or DNS subnet prioritization might be required to support LDAP enabled NFS volumes](understand-guidelines-active-directory-domain-service-site.md#ad-ds-ldap-discover).
488-
- If DNS scavenging is enabled (where stale DNS entries are automatically pruned based on timestamp/age) and dynamic DNS was used to create the DNS records for the Azure NetApp Files volume, the scavenger process might inadvertently prune the records for the volume. This pruning can lead to a service outage for name-based queries. Until this issue is resolved, manually create DNS A/AAAA and PTR entries for the Azure NetApp Files volume if DNS scavenging is enabled.
488+
- If DNS scavenging is enabled (where stale DNS entries are automatically pruned based on timestamp/age) and dynamic DNS was used to create the DNS records for the Azure NetApp Files volume, the scavenger process might inadvertently prune the records for the volume. This pruning can lead to a service outage for name-based queries. Until this issue is resolved, manually create DNS A/AAAA and PTR entries for the Azure NetApp Files volume if DNS scavenging is enabled. Azure NetApp Files will not remove or delete PTR records in any conditions.
489489
490490
## Next steps
491491

0 commit comments

Comments
 (0)