FNS defines policies for naming objects in the federated namespace (see fns_policies(5)). At the enterprise level, FNS policies specify naming for organizations, hosts, users, sites, and services. The enterprise-level naming
service provides contexts to allow other objects to be named relative to these objects.
The organizational unit namespace provides a hierarchical namespace for naming subunits of an enterprise. An organizational unit maps to an NIS+ domain. Organizational
unit names can be either fully qualified NIS+ domain names or relatively NIS+ domain names. If a terminal dot is present in the name, it
is treated as a fully qualified name. Otherwise, the name is resolved relative to the root NIS+ domain.
Users in the NIS+ namespace are found in the passwd.org_dir table of an NIS+ domain. Users in an FNS organizational unit correspond to the users in the passwd.org_dir table of the corresponding NIS+ domain. FNS
provides a context for each user in the passwd.org_dir table.
Hosts in the NIS+ namespace are found in the hosts.org_dir table of an NIS+ domain. Hosts in an FNS organizational unit correspond to the hosts in the hosts.org_dir table of the corresponding NIS+ domain. FNS
provides a context for each host in the hosts.org_dir table.
In NIS+, users and hosts have a notion of a home domain. It is the primary NIS+ domain that maintains information
associated with them. A user or host's home domain can be determined directly using its NIS+ principal name, which is composed of the atomic user (login) name or the atomic
host name, and the name of the NIS+ home domain. For example, user jsmith with home domain wiz.com has an NIS+ principal name, jsmith.wiz.com.
A user's NIS+ home domain corresponds to the user's FNS organizational unit and determines the binding for myens
A host's NIS+ home domain corresponds to the host's FNS organizational unit and determines the binding for thisens, thisorgunit, user, and host.