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

Because the entries are stored in the directory based on the client’s configuration, theclient must be configured to use the LDAP naming services.For better performance, load the databases in this order:1. passwd database followed by shadow database2. networks database followed by netmasks database3. bootparams database followed by ethers databaseNote that when adding automounter entries, the database name is in the form ofauto_* (for example, auto_home).If you have /etc files from different hosts to add to the LDAP server, you can eithermerge all of them into the same /etc file and then use ldapaddent on one host toadd the files, or perform ldapaddent on the different hosts one by one, with theexpectation that each host is already configured as a LDAP client.If your naming service data is already in an NIS server, and you want to move thedata to the LDAP server for LDAP naming services, use the ypcat (or niscat)command to dump the NIS map into files. Then, run ldapaddent against these filesto add the data to the LDAP server.Note – ldapaddent can only be run on an LDAP client.The following procedure assumes that the tables are to be extracted from a yp client.▼How to Populate a Server With host Entries Usingldapaddent1. Make sure that Sun Java System Directory Server was set up using idsconfig.2. On a client machine, become superuser or assume an equivalent role.Roles contain authorizations and privileged commands. For more informationabout roles, see “Using Role-Based Access Control (Tasks)” in System AdministrationGuide: Security Services.3. Make the machine an LDAP client.# ldapclient init -a profileName=new -a domainName=west.example.com \192.168.0.14. Populate the server with data.# ldapaddent -D “cn=directory manager” -f /etc/hosts hostsYou will be prompted for a password.In this example, ldapaddent will use the authentication method that has beenconfigured in the profile “new”. Selecting “simple” will cause the password to beChapter 10 • Planning Requirements for LDAP Naming Services (Tasks) 159