Add Environment Validator TSG: AzStackHci_DNS_ActiveDirectoryDomainName (Active Directory Domain Name Resolution)#309
Open
1008covingtonlane wants to merge 2 commits into
Conversation
…me (Active Directory Domain Name Resolution) Customer remediation guide for the DNS Active Directory domain name resolution check. Documents both reported names (AzStackHci_DNS_ActiveDirectoryDomainName aggregated and AzStackHci_DNS_Test_ActiveDirectory_DomainName_Resolution per-node detail), where the failure appears, the failure signatures, node identification, consequences, the DNS-client / conditional-forwarder remediation, and a glossary. Live-validated Grade A on Azure Local 23H2 build 2607. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new Environment Validator troubleshooting guide (TSG) documenting how to diagnose and remediate failures of the DNS Active Directory domain name resolution validator (AzStackHci_DNS_ActiveDirectoryDomainName / AzStackHci_DNS_Test_ActiveDirectory_DomainName_Resolution), and indexes it from the EnvironmentValidator README.
Changes:
- Introduces a customer-facing TSG with detection paths (health check JSON,
Get-SolutionUpdate, Event Log, portal), remediation, and verification steps for AD domain DNS resolution failures. - Adds a README entry linking to the new troubleshooting guide.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| TSG/EnvironmentValidator/Troubleshooting-DNS-ActiveDirectory-DomainName-Resolution.md | New TSG documenting diagnosis/remediation/verification for the AD domain DNS resolution Environment Validator check. |
| TSG/EnvironmentValidator/README.md | Adds the new TSG to the Environment Validator index list. |
…cap Get-WinEvent - Filter HealthCheckResult.EnvironmentChecker.*.json so the newest file is not a non-Environment-Validator result (avoids false no-failures). - Add -MaxEvents 2000 to the Event ID 17205 query for responsiveness. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
What
Adds a customer-facing Environment Validator troubleshooting guide for the DNS Active Directory domain name resolution check, plus a README index entry.
This check confirms that each Azure Local node can resolve the cluster's Active Directory domain name (the AD domain FQDN) against every configured DNS server. It runs at deployment, add-node, and the pre-update health check, and most often blocks a pending update or an add-node operation. It is reported under two names, both documented here:
AzStackHci_DNS_ActiveDirectoryDomainName(the rolled-up, per-cluster result)AzStackHci_DNS_Test_ActiveDirectory_DomainName_Resolution(the per-node, per-DNS-server detail result)Contents
Get-SolutionUpdate, EventID 17205, Azure portal)Validation
Live-validated end to end on Azure Local 23H2 (build 2607): the documented failure was injected on a node, the check failed with the documented signature and was discoverable on the documented surfaces, the documented remediation was applied, and the check returned to success. The guide is consistent with the Environment Validator source for this check.
This is a customer network and Active Directory configuration check (owned by the customer's AD or DNS administrator). It is not a Microsoft software defect and not an OEM hardware or firmware issue.