Oracle Documentation
Solaris 10 System Administrator Collection, System Administration Guide: Network Services Accessing Network File Systems Topics
NFS version 4
RFC 3530, Network File System (NFS) version 4 Protocol
The NFS Version 4 Protocol, a white paper by Pawlowski, Brian, Spencer Shepler, Carl Beame, Brent Callaghan, Michael Eisler, David Novick, David Robinson, and Robert Thurlow.
From Opensolaris.org this page explains the nfsmapid Daemon and how the domain is set or how NFSMAPID_DOMAIN is used.
Blogs:
Mark Shellenbaum's Weblog describes ZFS ACLs.
Lisa Week's Weblog describes NFSv4 ACLs and ZFS ACLs.
Sam Falkner's Weblog describes A DTrace Provider for NFS.
Sam Falkner's Weblog describes ACLs Everywhere.
Eric Kustarz's Weblog has a dscript to get active NFS clients/nfstop.
Dave's Blog, Notes on configuring NFS on Solaris 10
arfore dot com, Patch Solaris 10 over NFS
Other
Solaris 10, Update 4, 8/07 and newer releases:
The sysidtool command includes an enhanced sysidnfs4 program. The sysidnfs4 program now runs during the installation process to determine whether an NFSv4 domain has been configured for the network.
During an interactive installation, the user is provided with the default NFSv4 domain name that is automatically derived from the OS. The user can accept this default. Or, the user can specify a different NFSv4 domain.
For more information, see the sysidtool(1M) and the sysidnfs4(1M) man pages.
As part of a Solaris JumpStartTM installation, a new keyword is available in the sysidcfg file. The user can now assign a value for the NFSv4 domain by using the new keyword, nfs4_domain.
For more information about this new keyword, see the sysidcfg(4) man page. This man page also provides an example of how to use the new nfs4_domain keyword.
NFS version 4 Default Domain Name
There is only one keyword for specifying the NFSv4 default domain name:
nfs4_domain=dynamic, value
where value must be a fully qualified domain name, as per RFC1033 and RFC1035 recommendations. The reserved value dynamic suppresses the front-end installation prompt. At the same time, use of dynamic enables the NFSv4 domain to be derived dynamically, at run time, based on naming service configuration.
For example:
nfs4_domain=example.com
...hard codes the value used by the nfsmapid(1M) daemon to be example.com. In contrast, the following example shows how to set the nfs4_domain variable to the reserved keyword dynamic:
nfs4_domain=dynamic
The preceding example enables the nfsmapid(1M) daemon to derive the domain from the system's configured naming services, as prescribed in the System Administration Guide: Network Services.