Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
May the source be with you, but remember the KISS principle ;-)
Skepticism and critical thinking is not panacea, but can help to understand the world better

NIS Namespace and NIS domains



Contents Next

NIS is a very old service and unlike DNS NIS namespace does not support a domain hierarchy. Each NIS domain should contain one NIS master server, zero or more  slave servers (optional) and one or more clients.  In a way NIS master server is similar to WEB server: like is the case with WEB servers there can be many NIS domains in the organization each with its own master (and possibly slaves) serving particular subset of clients.  The client binds to the server with special command, somewhat similar to providing URL to the browser. NIS master distributes maps the pages of information similar to HTML pages. Similar to web pages NIS maps constitute the part of domain namespace. 

To set up an NIS domain, you need to know the IP address of the NIS master as well as the domain name. Usually NIS domain name is constructed from the appropriate DNS name for the organization as a whole or a particular part of the organization (in big companies). It does not need to be register in a special authority. The maximum length of NIS domain name is 256 characters. Unlike DNS NIS domains is case sensitive. For example:

is not equal to:

If you have more than one NIS domain established, you need to know which clients are handled by which NIS master in order to properly bind clients to masters. Bindling is client-side operation: you need to log into each client machine and use the command:

# domainname domain

Here domain is the domain name of the master server that you plan to use for a particular client, a kind of home page for browser.

Note that different clients can use different domains and different NIS server (on Solaris 10 you probably can run several of them on one physical server, each in its own zone, like you can run several Web servers in the same way). For example:


Normally only root can use the domainname command, unless you created a special role for this purpose. Because the command is effective only until the machine is rebooted, it needs to be put into one of the startup RC scripts.

Domain is only a part of NIS namespace, the second and more important part is NIS maps, the concept similar to web pages that we will discuss in the next part of the tutorial.


Contents Next


The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright 1996-2018 by Dr. Nikolai Bezroukov. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case is down you can use the at


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019