You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-server/active-directory/deployment-operation-ad-domains.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,8 @@ If you use a single-label DNS name in your environment, clients might be unable
80
80
81
81
### How to enable Windows-based clients to send queries and dynamic updates when using single-label DNS zones
82
82
83
+
A Windows-based computer requires additional configuration to support single-label DNS names for Active Directory domains. Specifically, in a domain that has a single-label DNS name, the DC Locator service on an Active Directory domain member doesn't use the DNS Server service to locate domain controllers. You have to apply this additional configuration to all computers in all forests.
84
+
83
85
Consider the following configuration:
84
86
85
87
- Domain member computers reside in a forest that doesn't contain any single-label DNS domains.
@@ -99,9 +101,9 @@ These behaviors cause DNS resolution issues. To mitigate the issues, you have to
99
101
100
102
[!INCLUDE [registry important alert](../../../includes/registry-important-alert.md)]
101
103
102
-
##### Step 1: Change the DC locator configuration
104
+
##### Step 1: Change the DC Locator service configuration
103
105
104
-
On the Windows client computers (domain-joined, nondomain-joined, or Microsoft Entra ID-joined), follow these steps:
106
+
On the domain-joined Windows client computers, follow these steps:
105
107
106
108
1. In the Search box, enter regedit, and then select **Registry editor**.
107
109
1. Locate and select the `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters` subkey.
@@ -113,7 +115,7 @@ On the Windows client computers (domain-joined, nondomain-joined, or Microsoft E
113
115
114
116
##### Step 2: Change the dynamic update configuration for the DNS root zone or single-label DNS zones
115
117
116
-
Apply these changes to all DCs and members of domains that have single-label DNS names. If a domain that has a single-label DNS name is a forest root domain, apply these changes to all the DCs in the forest, unless the following individual zones are delegated from the *ForestName* zone: \_msdcs. *ForestName*, \_sites. *ForestName*, _tcp. *ForestName*, and \_udp. *ForestName*.
118
+
Apply these changes to all DCs and Windows clients (domain-joined, nondomain-joined, or Microsoft Entra ID-joined) that have single-label DNS suffixes. If a domain that has a single-label DNS name is a forest root domain, apply these changes to all the DCs in the forest, unless the following individual zones are delegated from the *ForestName* zone: \_msdcs. *ForestName*, \_sites. *ForestName*, _tcp. *ForestName*, and \_udp. *ForestName*.
0 commit comments