Corrected DNS usage #3967
Corrected DNS usage #3967
Conversation
Updated the documentation to specify PowerShell commands for DNS verification and system restart. nslookup, in Windows, does not use the Windows DNS client resolver. It has an independent resolution engine. The Resolve-DnsName PowerShell cmdlet uses the Windows DNS client resolver. Resolve-DnsName must be used when testing whether a Windows role, feature, service, or application can correctly resolve a DNS name. Because Resolve-DnsName uses the exact same Win32 API calls (DnsQueryEx()) as Windows, while nslookup does not, which can lead to false positive or negative lookups. Internal to Microsoft, you can read more about this topic at: https://aka.ms/NoNsLookup
Refine DNS setup instructions with PowerShell commands
|
@JamesKehr : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 2c39a14: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull Request Overview
This PR updates DNS configuration documentation to use PowerShell commands instead of legacy cmd commands, aligning the documentation with modern Windows administration practices.
- Replaced
nslookupwithResolve-DnsNamePowerShell cmdlet - Updated code block language identifiers from
cmdtopowershell - Clarified command type in instructional text
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
3 participants
Updated the documentation to specify PowerShell commands for DNS verification and system restart.
nslookup, in Windows, does not use the Windows DNS client resolver. It has an independent resolution engine. The Resolve-DnsName PowerShell cmdlet uses the Windows DNS client resolver.
Resolve-DnsName must be used when testing whether a Windows role, feature, service, or application can correctly resolve a DNS name. Because Resolve-DnsName uses the exact same Win32 API call (DnsQueryEx()) as other Windows processes. While nslookup does not. This can lead to false positive or negative lookups.
Internal to Microsoft, you can read more about this topic at: https://aka.ms/NoNsLookup