Red Hat Directory Server 8.0 Administrator's Guide

domain entry for the directory is probably named dc=ldap,dc=example,dc=com or simply
dc=example,dc=com.
The LDIF entry used to define a domain appears as follows:
dn: distinguished_name
objectClass: top
objectClass: domain
dc: domain_component_name
list_of_optional_attributes
...
The following is a sample domain entry in LDIF format:
dn: dc=example,dc=com
objectclass: top
objectclass: domain
dc: example
description: Fictional example company
Each element of the LDIF-formatted domain entry is defined in Table A.2, “LDIF Elements in
Domain Entries”.
LDIF Element Description
dn: distinguished_name Required. Specifies the distinguished name
for the entry.
objectClass: top Required. Specifies the top object class.
objectClass: domain Specifies the domain object class. This line
defines the entry as a domain or domain
component.
dc: domain_component Attribute that specifies the domain's name.
The server is typically configured during the
initial setup to have a suffix or naming context
in the form
dc=hostname,dc=domain,dc=toplevel. For
example, dc=ldap,dc=example,dc=com. The
domain entry should use the leftmost dc
value, such as dc: ldap. If the suffix were
dc=example,dc=com, the dc value is dc:
example. Do not create the entry for dn:
dc=com unless the server has been
configured to use that suffix.
list_of_attributes Specifies the list of optional attributes to
maintain for the entry.
Table A.2. LDIF Elements in Domain Entries
Specifying Organizational Unit Entries
543