For a description of Single Label Domains, see the Single Label Domains topic in the Microsoft DNS Namespace Planning Solution Center.
Single Label Domains
Disjoint NamespacesFor a description of Disjoint Namespaces, see the Disjoint Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
Discontiguous NamespacesFor a description of Discontiguous Namespaces, also known as a non-contiguous namespaces, see the Discontiguous Namespaces topic in the Microsoft DNS Namespace Planning Solution Center.
Exchange ServerIn response to customer feedback, the Exchange team has updated its testing matrix and has determined that Exchange Server 2010 will be supported on SLDs, Disjoint Namespaces, and Discontiguous Namespaces. This page contains a brief description of each of these scenarios and special considerations. If you intend to install Exchange 2010 into one of these environments, read the Exchange Team Blog's documentation about the applicable subject.
Note For information about disjoint namespace scenarios in Microsoft Exchange Server 2013, visit the following TechNet website:
In adding support for these types of topologies, there is an underlying requirement for DNS to be correctly installed and configured. Before users continue with any deployment that is defined here, clients and servers must be able to reliably resolve DNS queries for a given resource in the appropriate namespace.
Single Label DomainsAlthough Exchange 2010 is supported with SLDs, the Exchange product team's view is that SLDs are not a recommended configuration and may not be supported by future Exchange versions. Other Microsoft or third-party applications that you want to run in your environment may not be supported on an SLD. This could have an adverse effect on your environment. Although we will allow the installation of Exchange 2010 in an SLD, we strongly recommend that you take steps to move your organization out of this configuration.
Disjoint NamespacesIn Microsoft Exchange 2010, there are three supported scenarios for deploying Exchange in a domain that has a disjoint namespace. The supported scenarios are as follows:
- Scenario 1: The primary DNS suffix of the domain controller is not the same as the DNS domain name. Computers that are members of the domain can be either disjoint or not disjoint.
- Scenario 2: A member computer in an Active Directory domain is disjoint even though the domain controller is not disjoint.
- Scenario 3: The NetBIOS domain name of the domain controller is not the same as the subdomain of the DNS domain name of that domain controller.
- In Exchange 2010, you may have to configure the DNS suffix search list to include multiple DNS suffixes if you have a disjoint namespace. For more information, see the Configure the DNS Suffix Search List for a Disjoint Namespace TechNet article.
- Msds-allowedDNSSuffixes must be configured within the Active Directory environment for all namespaces that are used within the forest. For information about how to configure this, see the The computer's primary DNS suffix does not match the FQDN of the domain where it resides TechNet article.
Discontiguous (noncontiguous) namespacesFor discontiguous namespaces, DNS must be configured so that Exchange servers can resolve all domain names in the environment. It is also a requirement that msds-allowedDNSSuffixes are configured within the Active Directory environment for all namespaces that are used within the forest.
For information about how to configure this, see the Understanding DNS Client Settings. TechNet article.
Affected Exchange products include the following:
- Exchange Server 2013
For more information about Exchange 2013 system requirements, see the Exchange 2013 System Requirements TechNet article.
- Exchange Server 2010
For more information about Exchange 2010 system requirements, see the Exchange 2010 System Requirements TechNet article.
- Exchange Server 2007
Microsoft has changed the Setup prerequisite rule for SLDs from an Error to a Warning. This change lets the Service Pack 1 installation continue in SLD environments.
For known issues and recommendations about Exchange 2007 together with SLD, see the Exchange Team's Blog Documentation.
- Exchange Server 2003
- Exchange 2000 Server