NFS Services Administrator's Guide

Configuring and Administering NIS
Configuring and Administering an NIS Client
Chapter 4 189
To Bind an NIS Client to a Server on a Different
Subnet
Hewlett-Packard recommends that you configure a server on each subnet
where you have NIS clients; however, if you cannot do that, follow these
steps to force an NIS client to bind to a server on a different subnet:
1. Log in as root to the NIS client.
2. Add the -ypset option to the YPBIND_OPTIONS variable in the
/etc/rc.config.d/namesvrs file, as follows:
YPBIND_OPTIONS=”-ypset”
3. In the /etc/rc.config.d/namesvrs file, set the YPSET_ADDR
variable to the IP address of an NIS server, as in the following
example:
YPSET_ADDR=”15.13.115.168”
4. Issue the following commands to restart the NIS client:
/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start
If the server you specify in the ypset command is unavailable when your
client boots up, your client will broadcast a request for a server to its
local network. If no server exists on the local network, the client will
hang.
For more information, type man 1M ypset or man 1M ypbind.
NOTE To configure the local host as an NFS client and enable the client to bind
to a specific server, you must use the -c option of the ypinit command.
Invoking the -c option of the ypinit command prompts the user to
provide a list of servers in the order of preference, to which the client
must bind to. To use the -c option, you must install patch PHNE_24910
or later. If you do not want to use this mode of specifying the list of
servers to bind to, you could use the broadcast method and bind to the
server in that subnet, that responds to the message or use the ypset
variable in the namesvrs file to specify the name of the NIS server on a
different subnet, to bind to.
To bind an NIS client to any of the specified NIS servers on a different
subnet, do the following: