NIS intelligently parses the setup files. Although this makes NIS administration easier, it does make the behavior of NIS more sensitive to changes in the setup and configuration files.
Use the procedures in this section when modifying any of the following.
Adding or deleting /etc/resolv.conf to allow or deny DNS forwarding
You do not have to stop and start NIS when changing NIS maps or the map source files.
Keep the following in mind.
Deleting a map or source file from an NIS master server does not automatically result in corresponding deletions from slave servers. You must delete maps and source files from slave servers by hand.
New maps do not automatically get pushed to existing slave servers. You must run ypxfr from the slaves.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Chapter 9, Using Role-Based Access Control (Tasks), in System Administration Guide: Security Services.
Stop the NIS server.
# svcadm disable network/nis/server
Make the necessary changes to your files.
Start the NIS server.
# svcadm enable network/nis/server