NIS slave server doesn't bind to itself

After configuring a system as a NIS slave server with ypinit -s, the system "binds" to the master NIS server instead of its own NIS slave server.

# ypwhich
NIS_master_server

To make the NIS client bind to itself:

1. Edit /var/yp/binding/`domainname`/ypservers and replace the hostname of the NIS master with your hostname.

2. Stop NIS services with /usr/lib/netsvc/yp/ypstop

3. Start NIS services with /usr/lib/netsvc/yp/ypstart

4. Confirm the binding with ypwhich

# ypwhich
NIS_slave_server

From the ypserv(1M) man page:

The file /var/yp/binding/domainname/ypservers is used to list the NIS server hosts that ypbind will bind to.

Back to brandonhutchinson.com.

NIS slave server doesn't bind to itself

Last modified: 06/09/2003