CentOS 6.2 Build NIS service

NIS Server Overview

Server for NIS provides network Microsoft Windows and Network Information Service (NIS) networks by providing the ability to act as a master NIS server for one or more NIS domains for a windows-based Active Directory domain service (AD DS) domain controller The network is integrated together.

How Server for NIS works

Server for NIS stores both standard and non-standard NIS map data in AD DS. (standard mapping consists of aliases, Bootparams, ethers, hosts, group, Netgroup, NetID, netmasks, Networks, passwd, protocols, RPC, services, Pservers and Shadow; all other mappings are non-standard mappings. Therefore, Server for NIS creates a namespace for Windows domain and NIS domains that can be managed by a Windows administrator using a set of tools. Administrators can easily create, modify, and delete user accounts for both Windows domain and UNIX domains. Users who have accounts in both Windows and UNIX environments can be managed by AD DS that contains all the attributes required by their respective domains and namespaces.

Server for NIS can also be installed on other domain controllers that are located in the same domain as the primary NIS server, enabling these domain controllers to act as NIS subordinate servers (also known as secondary servers). In this case, NIS data in Active Directory is automatically replicated between Windows domain controllers running Server for NIS. In addition, unix-based computers can continue to act as subordinate servers in the NIS domain, and NIS servers use Yppush to propagate changes to NIS data to unix-based Server for NIS, just like a UNIX master NIS server.

Server for NIS installation process

After you install NIS server, migrate the NIS mappings from the unix-based Server for NIS to the computer running Server for NIS. You can use the Windows-based Migration Wizard provided with server for NIS, or you can use command-line utilities to complete the migration. After migrating the mappings for the NIS domain, the server for NIS can be deployed as the primary server for the NIS domain. You can migrate multiple NIS domains to the same windows-based AD DS domain controller. These fields can be merged with each other, or they can exist independently. You can migrate NIS map data in stages by migrating one NIS map at a time.

NIS servers can support multiple NIS domains at the same time. Mappings that belong to multiple domains can also reside in Active Directory. Requests from clients or other servers in the domain receive data from mappings in the same domain.

Server Management for NIS

You can use Windows based UNIX identity Management to manage NIS servers. You can use windows-based tools, such as Active Directory users and computers, to manage the passwd, group, and hosts mappings that have been migrated to AD DS. You can also use command-line tools Nismap and nisadmin to manage standard and non-standard mappings and administer NIS servers. You can use Windows management tools to monitor NIS servers, including significant events and errors that audit NIS server records with Event Viewer.

In addition to using the administrative tools provided by Windows, you can create additional management tools by using Active Directory Service Interface (ADSI) or Lightweight Directory Access Protocol (LDAP).

The NIS server implements the required NIS remote procedure calls for processing requests from unix-based NIS clients and windows-based NIS clients and other subordinate NIS servers. The server for NIS supports broadcast mode and normal binding mode.

NIS Required Packages

The main package for the Ypserv-2.19-22.el6.i686.rpm:nis service

YP-TOOLS-2.9-12.EL6.I686.RPM: Provides software packages for NIS client settings

YPBIND-1.20.4-29.EL6.I686.RPM: A package that provides query instruction functionality for NIS clients

RPCBIND-0.2.0-8.EL6.I686.RPM (The package name for the older version name is not Rpcbind is Portmap): Managing RPC connections, starting RPC-required packages

NIS Related Documents

/etc/ypserv.conf:nis The primary configuration file, you can standardize whether NIS clients have permissions to query NIS servers

/etc/hosts: Record host and IP address correspondence, if there is no DNS system, the Hosts file for NIS server requires host records for each NIS client.

/etc/netgroup: Setting a trusted host or network segment

/etc/yp/makefile: Configuration files related to database creation