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
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ appliesto:
14
14
---
15
15
# Configuring Active Directory domains that use single-label DNS names
16
16
17
-
This article provides information about the deployment and operation of Active Directory (AD DS) domains that use single-label DNS names.
17
+
This article provides information about the deployment and operation of Active Directory Domain Services (AD DS) domains that use single-label DNS names.
18
18
19
19
_Original KB number:_ 300684
20
20
@@ -23,10 +23,10 @@ This article provides application compatibility information for scenarios in whi
23
23
For the following reasons, create new Active Directory domains that have fully qualified DNS names:
24
24
25
25
- You can't use an internet registrar to register single-label DNS names.
26
-
- When joined to single-label domains, client computers (both domain-joined and non-domain joined) and domain controllers require additional configuration to dynamically register DNS records in single-label DNS zones.
27
-
- Client computers and domain controllers might require additional configuration to resolve DNS queries in single-label DNS zones.
26
+
- When joined to single-label domains, client computers (both domain-joined and non-domain joined) and domain controllers require extra configuration to dynamically register DNS records in single-label DNS zones.
27
+
- Client computers and domain controllers might require extra configuration to resolve DNS queries in single-label DNS zones.
28
28
- Some server-based applications are incompatible with single-label domain names. Newly released applications might not support single-label DNS names, and applications that support single-label DNS names might drop that support in the future.
29
-
- Transitioning from a single-label DNS domain name to a fully qualified DNS name is non-trivial and consists of two options:
29
+
- Transitioning from a single-label DNS domain name to a fully qualified DNS name is nontrivial and consists of two options:
30
30
31
31
-[Migrate](https://www.microsoft.com/download/details.aspx?id=19188) users, computers, groups, and other states to a new forest.
32
32
- Rename the existing domain.
@@ -45,7 +45,7 @@ Best-practice Active Directory domain names consist of one or more subdomains th
45
45
- contoso.com
46
46
- corp.contoso.com
47
47
48
-
The top-level domain occupies the rightmost label in a domain name. A large number of top-level domains are available. Common top-level domains include the following:
48
+
The top-level domain occupies the rightmost label in a domain name. A large number of top-level domains are available. Common top-level domains include the following examples:
49
49
50
50
- .com
51
51
- .net
@@ -93,7 +93,7 @@ Client access to the domains that have single-label DNS names fails if NetBIOS n
93
93
94
94
[!INCLUDE [registry important alert](../../../includes/registry-important-alert.md)]
95
95
96
-
On the Windows client computers (domain-joined, non-domain joined, or Entra ID-joined), follow these steps
96
+
On the Windows client computers (domain-joined, non-domain joined, or Microsoft Entra ID-joined), follow these steps
97
97
98
98
1. Change the domain controller locator configuration by following these steps:
99
99
@@ -161,7 +161,7 @@ Check the DNS servers to make sure that root servers aren't created unintentiona
161
161
162
162
| Value | Name | Description |
163
163
| --------- | - | --------- |
164
-
| 0x1 | Enabled | Computers can try to update the TopLevelDomain zones. If you enable the `UpdateTopLevelDomainZones` setting, computers send dynamic updates to any zone that is authoritative for the resource records that the computer must update, except for the root zone.|
164
+
| 0x1 | Enabled | Computers can try to update the TopLevelDomain zones. If you enable the `UpdateTopLevelDomainZones` setting, computers send dynamic updates to any zone that's authoritative for the resource records that the computer must update, except for the root zone. |
165
165
| 0x0 | Disabled | Computers can't try to update the TopLevelDomain zones. If you disable this setting, computers don't send dynamic updates to the root zone or to the top-level domain zones that are authoritative for the resource records that the computer must update. If you don't configure this setting, the policy isn't applied to any computers, and computers use their local configuration. |
0 commit comments