3.1.1.3.1.2.2 NC Naming

The DN of a domain NC is derived from the DNS name of the domain using the transformation algorithm of [RFC2247] section 3. The object at the root of each domain NC is a domainDNS object, in accord with section 5.2 of that RFC. The rDNAttID for the domainDNS class is dc, in accord with section 4 of the RFC. While the same attribute OID is used for the dc attribute in Active Directory as in section 4 of the RFC, the syntax of the attribute in Active Directory is String(Unicode) rather than the specified String(IA5). The dcObject auxiliary class, specified in section 5.1 of the RFC, is not present in Active Directory.

When operating as AD DS, the DN for the config NC is the RDN "CN=Configuration", followed by the DN of the domain NC of the forest root domain. When operating as AD LDS, the DN for the config NC is the RDN "CN=Configuration, CN={guid}", where guid is a GUID in dashed-string form ([RFC4122] section 3). For example,

CN=Configuration, CN={FD783EE9-0216-4B83-8A2A-60E45AECCB81}

is a possible DN of the config NC when operating as AD LDS.

The DN for the schema NC is the RDN "CN=Schema" followed by the DN of the config NC.

When operating as AD DS, an application NC is named in the same way as a domain NC; the root of each AD DS application NC is a domainDNS object. When operating as AD LDS, the DN of an application NC consists of one or more RDNs.

Show: