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

EXAMPLE 2–4 LDAP Switch File Template(Continued)netgroup:automount:aliases:ldapfiles ldapfiles ldap# for efficient getservbyname() avoid ldapservices: files ldapsendmailvars: filesThe nsswitch.conf FileThe default nsswitch.conf file that is installed with the Solaris software isdetermined by which naming service you select during the installation process. Eachline identifies a particular type of network information, such as host, password, andgroup, along with the information source, such as NIS+ tables, NIS maps, the DNShosts table, or local /etc. When you chose a naming service, the switch template filefor that service is copied to create the new nsswitch.conf file. For example, if youchoose NIS+, the nsswitch.nisplus file is copied to create a new nsswitch.conffile.An nsswitch.conf file is automatically loaded into every machine’s /etc directoryby the Solaris 9 release software, along with the following alternate (template)versions.■■■■/etc/nsswitch.nisplus/etc/nsswitch.nis/etc/nsswitch.files/etc/nsswitch.ldapThese alternate template files contain the default switch configurations used by theNIS+ and NIS services, local files, and LDAP. No default file is provided for DNS, butyou can edit any of these files to use DNS. When the Solaris software is first installedon a machine, the installer selects the machine’s default naming service. Duringinstallation, the corresponding template file is copied to /etc/nsswitch.conf. Forexample, for a machine client using NIS+, the installation process copiesnsswitch.nisplus to nsswitch.conf.If your network is connected to the Internet and users must access Internet hosts usingDNS, you must enable DNS forwarding.Unless you have an unusual namespace, the default template file as copied tonsswitch.conf should be sufficient for normal operation.40 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005