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

Tip – The original NIS dbm files are not overwritten. You can recover these files,if needed.c. Start the NIS daemons to ensure that they use the new maps.# svcadm enable network/nis/server:default8. Verify that the LDAP entries are correct.If the entries are not correct, then the entries can not be found by LDAP namingservices clients.# ldapsearch -h server -s sub -b "ou=servdates, dc=..." \"objectclass=servDates"9. Verify the contents of the LDAP_ maps.The following sample output shows how to use makedm to verify the contents ofthe hosts.byaddr map.# makedbm -u LDAP_servdate.bynumberplato: 1/3/2001johnson: 2/4/2003,1/3/2001yeats: 4/4/2002poe: 3/3/2002,3/4/2000If the contents are as expected, the transition from NIS to LDAP was successful.Note that the original NIS dbm files are not overwritten, so you can always recoverthose files. See “Reverting to NIS” on page 248 for more information.Examples of Custom MapsThe following two examples show how you might customize maps. Use yourpreferred text editor to modify the /var/yp/NISLDAPmapping file as needed. Formore information about file attributes and syntax, see the NISLDAPmapping(4) manpage and the LDAP naming services information in Chapter 9.Example 1–Moving Host EntriesThis example shows how to move host entries from the default location to another(nonstandard) location in the DIT.Change the nisLDAPobjectDN attribute in the NISLDAPmapping file to the newbase LDAP distinguished name (DN). For this example, the internal structure of theLDAP objects is unchanged, so objectClass entries are unchanged.Change:Chapter 15 • Transitioning From NIS to LDAP (Overview/Tasks) 239