To prevent being asked to specify an NFSv4 domain name during installation, use the nfs4_domain keyword in the sysidcfg file. This keyword suppresses selection of a domain name during the installation process. Use the following syntax:
nfs4_domain=dynamic or custom_domain_name
This reserved keyword dynamically derives the NFSv4 domain name, based on naming services configuration. For example:
This example enables the domain name to be derived by the naming service.
The reserved keyword, dynamic, is not case sensitive.
By default, NFSv4 uses a domain name that is automatically derived from the system's naming services. This domain name is sufficient for most configurations. In a few cases, mount points that cross domain boundaries can cause files to appear to be owned by “nobody” because no common domain name exists. To prevent this situation, you can override the default domain name and select a custom domain name.
This value overrides the default domain name.
This value must be a valid custom domain name. A valid domain name is composed of a combination of alphanumeric characters, dots, underscores, and dashes only. The first character must be an alphabetical character. For example:
This example sets the value that is used by the nfsmapid daemon to be example.com. This selection overrides the default domain name.
In previous releases, scripts enabled users to avoid being prompted for the NFSv4 domain name during installation.
For JumpStart installations in the Solaris 10 OS, you could use the workaround JumpStart sample script, set_nfs4_domain, to suppress the NFSv4 prompt during installation. This script is no longer required. Use the sysidcfg keyword, nfs4_domain, instead.
In prior releases, the /etc/.NFS4inst_state.domain file was created by the sysidnfs4 program. This file would suppress the prompt for an NFSv4 domain name during installation. This file is no longer created. Use the sysidcfg keyword, nfs4_domain, instead.