An NIS system maintains and distributes a central directory of user and group information, hostnames, e-mail aliases and other text-based information in a network.<\/p>\n
Though not the core purpose, NIS can be used for centralized authentication too.<\/p>\n
Server packages:<\/p>\n
ypserve
\nypbind
\nmake<\/p>\n
Client package:<\/p>\n
ypbind<\/p>\n
Procedure to create an NIS authentication server:<\/p>\n
Logon to server host
\nCreate users and assign password
\nEdit \/etc\/sysconfig\/network and add the line “NISDOMAIN=llc”
\nStart the ypserv service
\nCreate a database for the master NIS servers
\n# \/usr\/lib\/yp\/ypinit -m
\nIf this is the only server press “Q”
\nA new folder \/var\/yp\/llc will be created.
\nEdit \/etc\/hosts with the following entry
\nwww.llc
\nIn the client run the tool authconfig.
\nEnable NIC and give the servers IP address.
\nLogout and try loging back<\/p>\n
Client host] # ypwhich : Shows the server to which the host is connected.<\/p>\n
Client host] # ypcat password : Displays the password database<\/p>\n
We might need to mount home directories from the server. Mounting it using autofs should be good.<\/p>\n
NIS slave<\/p>\n
It is good to run an NIS slave server in a network. By this, if the primary server goes down, the slave should be able to perform authentication. The slave replicated its database from the primary frequently.<\/p>\n
Procedure to configure an NIS slave:<\/p>\n
Append “NISDOMAIN=llc” in \/etc\/sysconfig\/network
\nStart the service ypserv
\nRun the command \/usr\/lib\/yp\/ypinit -S
\nThe database gets populated in \/var\/yp\/llc automatically<\/p>\n
If any change is done in an NIS server, the database should be recreated using
\n# make -c \/var\/yp<\/p>\n","protected":false},"excerpt":{"rendered":"