ypset is useful for binding a client node which is not on a broadcast net, or is on a broadcast net which is not running the NIS server host. It also is useful for debugging NIS client applications, for instance where the NIS map only exists at a single NIS server.
In cases where several hosts on the local net are supplying NIS services, it is possible for ypbind to rebind to another host even while you attempt to find out if the ypset operation succeeded. For example, you can enter:
#which can be confusing. This is a function of the NIS subsystem's attempt to load-balance among the available NIS servers, and occurs when host1 does not respond to ypbind because it is not running ypserv (or is overloaded), and host2, running ypserv, gets the binding.
server indicates the NIS server to bind to, and must be specified as a name. This will work only if the node has a current valid binding for the domain in question, and ypbind has been set to allow use of ypset. In most cases, server should be specified as an IP address.
ypset tries to bind ypbind over a datagram transport first. Datagram Transports are recommended for higher performance. The NIS library calls, yp_enum, yp_all, yp_next, and yp_first use circuit transports regardless of the ``main'' transport being used.
for an overview of the NIS service.