Obtain the NIS+ root reference for your NIS+ hierarchy.
Create an X.500 entry that supports XFN reference attributes.
For example, the following command creates a new X.500 entry called c=us/o=doc with the object classes top, organization, and XFN-supplement (1.2.840.113536.25). The XFN-supplement object class allows the c=us/o=doc entry to store reference information for a subordinate naming system.
# fnattr -a .../c=us/o=doc object-class \ top organization XFN-supplement
If the X.500 entry already existed and was not defined with the XFN-supplement object class, it must be removed and re-created with the additional object class. Otherwise, it will not be able to hold reference information about the subordinate naming system.
Add the reference information about the subordinate system to the entry.
After creating the X.500 entry, you can then add information about the subordinate system by binding the appropriate root reference to the named entry.
For example, if your subordinate naming system is NIS+, and the NIS+ server you want to use is nismaster, your would enter:
# fnbind -r .../c=us/o=doc/ onc_fn_enterprise onc_fn_nisplus_root \ "doc.com. nismaster
If your subordinate naming system is NIS, and the NIS server you want to use is ypmaster, your would enter:
# fnbind -r .../c=us/o=doc/ onc_fn_enterprise onc_fn_nis_root \ "doc.com/ ypmaster"
These examples bind the reference for the NIS+ or NIS hierarchy with the root domain name doc.com., to the next naming system pointer (NNSP) of the X.500 entry c=us/o=doc, thus linking the X.500 namespace with the doc.com. namespace.
The address format used is that of the root reference described in "Obtaining the Root Reference". Note the use of the trailing slash in the name argument to fnbind, .../c=us/o=doc/, to signify that the reference is being bound to the NNSP of the entry, rather than to the entry itself.
For further information on X.500 entries and XFN references, see "X.500 Attribute Syntax for XFN References".