udpate

Author: v-lianna

support/windows-server/active-directory/active-directory-domain-join-troubleshooting-guidance.md

@@ -151,51 +151,9 @@ To resolve this error, follow these steps:
 2. Verify that the joining client has network connectivity to the DC over the required ports and protocols used by the applicable operating system (OS) versions. Domain join clients connect a helper DC over TCP port 135 by the dynamically assigned port in the range between 49152 and 65535.
 3. Ensure that the OS, software and hardware routers, firewalls, and switches allow connectivity over the required ports and protocols.
 
-### Error code 0xA8B
+### Error code 0xa8b
 
-> An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.
-
-Here's an example from the *netsetup.log* file:
-
-```output
-mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: status of verifying DNS A record name resolution for '<DC name>.<domain>.<tld>': 0x2746
-mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: failed to find a DC in the specified domain: 0xa8b, last error is 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpDsGetDcName returned: 0xa8b
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: Function exits with status of: 0xa8b
-mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0xa8b
-```
-  
-Error 0xA8B occurs if:
-
-- The workgroup computer being joined points to an invalid DNS server.
-- The DNS server(s) used by the joining computer is invalid, is missing the required zones, or is missing the required records for the target domain.
-- The target Active Directory domain contains a problematic DNS name.
-- Network problems exist on the workgroup computer, the target DC, or the network used to connect the client and target DC.
-
-To resolve this error, follow these steps:
-
-1. Verify that the computer being joined points to valid DNS server IP addresses. Invalid examples include:
-
-   - A stale or non-existent ISP DNS server on the corporate intranet.  
-   - A DNS server in an error state that prevents it from loading the *_msdcs.\<Forest Root Domain>* or target AD domain zones or resolving queries for those zones. Event ID 4521 may be logged.
-
-2. Verify that all DNS servers configured on the client host the required zones and valid records for a DC in the target domain. Check for the following misconfigurations:
-   - Forward lookup zone for the target AD domain is missing.
-   - The *_msdcs* forward lookup zone is missing.
-   - The *_msdcs.\<Forest Root Domain>* zone doesn't contain a Lightweight Directory Access Protocol (LDAP) SRV record for a DC in the target domain.
-   - Host A record is missing from the target AD domain zone.
-   - Host A record is present but contains the wrong IP address for the target DC.
-   - The host A record is present but was registered by a network interface that isn't accessible to the client computer.
-
-3. Check for special names in the target Active Directory domain that require additional configuration:
-
-   - Single-label DNS name
-   - Disjoint Namespace
-   - All numeric top-level domains (TLDs) or TLDs containing numeric characters
-
-4. Check for network problems on the workgroup computer, target DC, or the network connecting the computer and the target DC:
-   - A broken Network Interface Card (NIC) on the client computer or the target DC
-   - A broken network switch that drops network packets between the client and target DC
+For more information, see [Error code 0xa8b: An attempt to resolve the DNS name of a DC in the domain being joined has failed](error-0xa8b-resolve-dns-fail.md).
 
 ### Error code 0x40
 

support/windows-server/active-directory/error-0xa8b-resolve-dns-fail.md

@@ -5,7 +5,7 @@ ms.date: 03/19/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
-ms.reviewer: kaushika, raviks, v-lianna
+ms.reviewer: kaushika, raviks, herbertm, v-lianna
 ms.custom:
 - sap:active directory\on-premises active directory domain join
 - pcy:WinComm Directory Services
@@ -48,9 +48,9 @@ To resolve this error, follow these steps:
 1. Verify that the computer being joined points to valid DNS server IP addresses. Invalid examples include:
 
     - Invalid Internet Service Provider (ISP)-provided DNS servers.
-    - ISP-provided DNS servers that don't host the AD domain zone.
+    - ISP-provided DNS servers that doesn't host the AD domain zone.
     - A stale or nonexistent DNS server on the corporate intranet.
-    - A corporate network DNS server that don't host the AD domain zone.
+    - A corporate network DNS server that doesn't host the AD domain zone.
     - A corporate network DNS server in an error state that prevents it from loading the `_msdcs.<forest root domain>` or target AD domain zones, or from resolving queries for those zones. Event ID 4521 might be logged.
 
 2. Verify that all DNS servers configured on the client host the required zones and valid records for a DC in the target domain. Check for the following misconfigurations:
@@ -73,4 +73,4 @@ To resolve this error, follow these steps:
     - A broken Network Interface Card (NIC)  on the client computer or the target DC.
     - A broken network link.
 
-You can use tools like [nslookup](/windows-server/administration/windows-commands/nslookup) to verify availability and content of DNS records from the client end, and use tools like [ping](/windows-server/administration/windows-commands/ping) or [tracert](/windows-server/administration/windows-commands/tracert) to check reachability of IP addresses. You can use [PortQry](../networking/portqry-command-line-port-scanner-v2.md) to try specific DC UDP and TCP server ports. A starting point for DC server ports is [Configure firewall for AD domain and trusts](config-firewall-for-ad-domains-and-trusts.md).
+You can use tools like [nslookup](/windows-server/administration/windows-commands/nslookup) to verify availability and content of DNS records from the client end, and use tools like [ping](/windows-server/administration/windows-commands/ping) or [tracert](/windows-server/administration/windows-commands/tracert) to check reachability of IP addresses. You can use [PortQry](../networking/portqry-command-line-port-scanner-v2.md) to try specific DC UDP and TCP server ports. A starting point for DC server ports is [Configure firewall for AD domain and trusts](config-firewall-for-ad-domains-and-trusts.md).