Refine DNS setup instructions with PowerShell commands #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Owner
Author
|
Merging into my fork. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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