Which nis server

About this task. Keep the following in mind before performing the binding procedure: Using the NIS broadcast feature can incur security risks. Otherwise, the binding with the host name fails. Example The following command lists two servers and uses the default broadcast multicast for IPv6 option: options nis.

Continue to the dialog for the database configuration. The default settings are usually adequate. Leave this dialog with Next. Check which maps should be available and click Next to continue. Determine which hosts are allowed to query the NIS server. You can add, edit, or delete hosts by clicking the appropriate button.

Specify from which networks requests can be sent to the NIS server. Normally, this is your internal network. In this case, there should be the following two entries:. The first entry enables connections from your own host, which is the NIS server. The second one allows all hosts to send requests to the server. To configure a NIS master server for your network, proceed as follows:.

YaST installs the required packages. It speeds up the transfer of maps to the slaves. Select Allow Changes to Passwords to allow users in your network both local users and those managed through the NIS server to change their passwords on the NIS server with the command yppasswd. Leave this dialog with Next or click Other Global Settings to make additional settings.

In addition, passwords can be merged here. Click OK to confirm your settings and return to the previous screen. If no slave servers exist, this configuration step is skipped.

Continue to the dialog for the database configuration. The default settings are usually adequate. Leave this dialog with Next. The machine designated as master server contains the set of maps that the system administrator creates and updates as necessary.

Each NIS domain must have one, and only one, master server, which can propagate NIS updates with the least performance degradation. You can designate additional NIS servers in the domain as slave servers.

A slave server has a complete copy of the master set of NIS maps. Whenever the master server maps are updated, the updates are propagated among the slave servers. Normally, the system administrator designates one master server for all NIS maps. However, because each individual NIS map has the machine name of the master server encoded within it, you could designate different servers to act as master and slave servers for different maps.

To minimize confusion, designate a single server as the master for all the maps you create within a single domain. The examples in this chapter assume that one server is the master for all maps in the domain. NIS clients run processes that request data from maps on the servers. Clients do not make a distinction between master and slave servers, since all NIS servers should have the same information.

Each domain has a domain name and each machine sharing the common set of maps belongs to that domain. Any machine can belong to a given domain, as long as there is a server for that domain's maps in the same network. NIS service is provided by five daemons as shown in Table 7—1. This means that users who have a shell that begins with an r. If you have a shell that begins with r but is not intended to be restricted as such, refer to Chapter 10, NIS Troubleshooting for the workaround.

NIS service is supported by nine utilities as shown in Table 7—2. The information in NIS maps is stored in ndbm format. NIS slave servers also maintain duplicates of the master server's maps. NIS client machines can obtain namespace information from either master or slave servers.

NIS maps are essentially two-column tables. One column is the key and the other column is information related to the key. NIS finds information for a client by searching through the keys. Some information is stored in several maps because each map uses a different key. For example, the names and addresses of machines are stored in two maps: hosts.

When a server has a machine's name and needs to find its address, it looks in the hosts. When it has the address and needs to find the name, it looks in the hosts. Running make in that directory causes makedbm to create or modify the default NIS maps from the input files.

Always create maps on the master server, as maps created on a slave will not automatically be pushed to the master server. A default set of NIS maps are provided in the Solaris operating environment. You might want to use all these maps or only some of them. NIS can also use whatever maps you create or add when you install other software products. For example, the maps that belong to the domain test. Table 7—3 describes the default NIS maps, information they contain, and whether the software consults the corresponding administrative files when NIS is running.

Same as ethers. Used for UNIX-style authentication. Contains machine name and mail address including domain name. If there is a netid file available it is consulted in addition to the data available through the other files. Contains names of networks known to your system and their IP addresses, with the address as key. New ipnodes maps ipnodes. The maps store both IPv4 and IPv6 addresses.

See the ipnodes 4 man page. For example, when you add a new machine to a network running NIS, you only have to update the input file in the master server and run make.