Skip to content

Commit d6ed5b4

Browse files
committed
resolve path
1 parent 871c38c commit d6ed5b4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ DNS servers are configured under Active Directory connections. A primary and sec
2525

2626
Azure NetApp Files requires an Active Directory connection for SMB and NFSv4.1 Kerberos functionality. Active Directory requires DNS for proper functionality. In most cases, Active Directory deployments are installed with DNS servers integrated with the domain controllers. This configuration is a [Microsoft best practice](/windows-server/identity/ad-ds/plan/dns-and-ad-ds) for both ease of use and to ensure all required DNS records are created for domain services.
2727

28-
:::image type="content" source="media/domain-name-system-concept/integrated-active-directory-dns.png" alt-text="Diagram of AD DNS configuration." lightbox="media/domain-name-system-concept/integrated-ad-dns.png":::
28+
:::image type="content" source="media/domain-name-system-concept/integrated-active-directory-dns.png" alt-text="Diagram of AD DNS configuration." lightbox="media/domain-name-system-concept/integrated-active-directory-dns.png":::
2929

3030
In some cases, external DNS servers (such as BIND) may be used in lieu of (or in addition to) Active Directory hosted DNS services. This is called a [disjointed namespace](/windows-server/identity/ad-ds/plan/disjoint-namespace).
3131

0 commit comments

Comments
 (0)