The Solaris 10 version of the System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) includes updates to DNS BIND and pam_ldap. It also incorporates some minor changes and additions to other content, as well as corrections to several documentation errors. The DNS, NIS, and LDAP services are now managed by the Service Management Facility. Administrative actions on these services, such as enabling, disabling, or restarting, can be performed by using the svcadm command. The service's status can be queried by using the svcs command. For an overview of SMF, refer to Chapter 16, Managing Services (Overview), in System Administration Guide: Basic Administration. Also refer to the svcadm1M and svcs1 man pages for more details.Information specific to each service described in this book can be found in the following sections.DNS and the Service Management Facility NIS and the Service Management Facility LDAP and the Service Management Facility NIS-to-LDAP Tools and the Service Management Facility NIS+ to LDAP Tools and the Service Management Facility For information about NIS+ and the Service Management Facility, see System Administration Guide: Naming and Directory Services (NIS+). BIND 8.4.2 ships in the Solaris 10 release. This version of BIND provides a complete DNS client-server solution for IPv6 networks on Solaris software. There are no changes to the DNS BIND procedures in this guide.BIND 9 is also supported in the Solaris 10 release and installs in the /usr/sfw directory. A migration document is available in the /usr/sfw/doc/bind directory. The information and procedures in Part II, DNS Setup and Administration apply to BIND 9, except as indicated in the migration document. The Solaris 10 OS release introduced several changes to pam_ldap, identified in the following list. See the pam_ldap5 man page for more information.The previously supported use_first_pass and try_first_pass options are obsolete as of the Solaris 10 software release. These options are no longer needed, may safely be removed from pam.conf, and are silently ignored. They may be removed in a future release. Password prompting must be provided for by stacking pam_authtok_get before pam_ldap in the authentication and password module stacks, and by including pam_passwd_auth in the passwd service auth stack. The previously supported password update function is replaced in this release by the previously recommended use of pam_authtok_store with the server_policy option. The pam_ldap account management feature strengthens the overall security of the LDAP Naming Service. Specifically, the account management feature does the following.Allows for tracking password aging and expiration Prevents users from choosing trivial or previously used passwords Warns users if their passwords are about to expire Locks out users after repeated login failures Prevents users, other than the authorized system administrator, from deactivating initialized accounts It is not possible to provide a clean automated update for the changes listed above. Therefore, an upgrade to a Solaris 10 or later release will not automatically update the existing pam.conf file to reflect the pam_ldap changes. If the existing pam.conf file contains a pam_ldap configuration, you will be notified after the upgrade via the CLEANUP file. You will need to examine the pam.conf file and modify it, as needed.See pam_passwd_auth5, pam_authtok_get5, pam_authtok_store5, and pam.conf4 man pages for more information. application-levelSeveral documentation errors have been corrected in this release.