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

Setting Up NIS ClientsThe two methods for configuring a client machine to use NIS as its naming service areexplained below.Note – The Solaris operating system does not support a configuration in which a NISclient and a Native LDAP client co-exist on the same client machine.■ypinit. The recommended method for configuring a client machine to use NIS isto login to the machine as root and run ypinit -c.# ypinit -c■You will be asked to name NIS servers from which the client obtains namingservice information. You can list as many master or slave servers as you want. Theservers that you list can be located anywhere in the domain. It is a better practice tofirst list the servers closest (in network terms) to the machine, than those that areon more distant parts of the net.Broadcast method. An older method of configuring a client machine to use NIS to login to the machine as root, set the domain name with the domainname command,then run ypbind.ypstart will automatically invoke the NIS client in broadcast mode (ypbind-broadcast), if the /var/yp/binding/‘domainname‘/ypservers file doesnot exist.# domainname doc.com# mv /var/yp/binding/‘domainname‘/ypservers /var/yp/binding/‘domainname‘\/ypservers.bak# ypstartWhen you run ypbind, it searches the local subnet for an NIS server. If it finds asubnet, ypbind binds to it. This search is referred to as broadcasting. If there is noNIS server on the client’s local subnet, ypbind fails to bind and the client machineis not able to obtain namespace data from the NIS service.Chapter 5 • Setting Up and Configuring NIS Service 91