Naming and Directory Services (DNS, NIS, and LDAP)

Also, if you use interface-specific aliases such as server-#, a long list of fullyqualified host names are returned. If you are using host names to share file systems orhave other such checks, you must account for the checks. For example, if you assumenon-FQDNs for local hosts and FQDNs only for remote DNS-resolved hosts, you mustaccount for the difference. If you set up LDAP with a different domain name fromDNS, the same host might end up with two different FQDNs, depending on thelookup source.Default Directory Information Tree (DIT)By default, Solaris LDAP clients access the information assuming that the DIT has agiven structure. For each domain supported by the LDAP server, there is a subtreewith an assumed structure. This default structure, however, can be overridden byspecifying Service Search Descriptors (SSDs). For a given domain, the default DIT willhave a base container that holds a number of well known containers that hold entriesfor a specific information type. See the following table for the names of these subtrees.(This information can be found in RFC 2307 and others.)TABLE 9–1 DIT Default LocationsDefault Containerou=Ethersou=Groupou=Hostsou=Aliasesou=Netgroupou=Networksou=Peopleou=printersou=Protocolsou=Rpcou=Servicesou=SolarisAuthAttrou=SolarisProfAttrInformation Typebootparams(4), ethers(4)group(4)hosts(4), ipnodes(4), publickey for hostsaliases(4)netgroup(4)networks(4), netmasks(4)passwd(1), shadow(4), user_attr(4),audit_user(4), publickey for usersprinters(4)protocols(4)rpc(4)services(4)auth_attr(4)prof_attr(4), exec_attr(4)Chapter 9 • LDAP Basic Components and Concepts (Overview) 133