Nis maps not updating
The ypset command can point a client at a particular server; however, at the first hint of trouble, the client attempts to locate a new server by broadcasting.Unless a server on the client's network responds, this sequence of events can cause the client to hang.NIS commands still begin with the letters yp, so it's hard to forget the original name.NIS was widely adopted among Unix vendors and is supported by every Linux distribution.
Providing more than one server helps relieve the load on the master and helps keep clients working even when some servers become unavailable.In the traditional NIS implementation, you must place at least one NIS server on every physical network.Clients use IP broadcasting to locate servers, and broadcast packets are not forwarded by routers and gateways.Whenever a file is changed on the master server, the corresponding NIS map must be pushed out to the slaves so that all servers provide the same data.Clients do not distinguish between the master server and the slaves.
A server and its clients constitute an NIS "domain." Data files are preprocessed into database files by the Berkeley DB hashing library to improve the efficiency of lookups.