Precedence Rules
For nfsmapid to work properly, NFS Version 4 clients and servers
must have the same domain. To ensure matching NFS Version 4 domains,
nfsmapid follows these strict precedence rules:
-
The daemon first checks the SMF repository for a value that has been assigned to the
nfsmapid_domainparameter. If a value is found, the assigned value takes precedence over any other settings. The assigned value is appended to the outbound attribute strings and is compared against inbound attribute strings. For procedural information, see Setting Up the NFS Service.Note:
The use of theNFSMAPID_DOMAINsetting is not scalable and is not recommended for large deployments. -
If no value has been assigned to
nfsmapid_domain, then the daemon checks for a domain name from a DNS TXT RR.nfsmapidrelies on directives in the/etc/resolv.conffile that are used by the set of routines in theresolver. Theresolversearches through the configured DNS servers for the_nfsv4idmapdomainTXT RR. Note that the use of DNS TXT records is more scalable. For this reason, continued use of TXT records is much preferred over setting the parameter in the SMF repository. -
If no DNS TXT record is configured to provide a domain name, then the
nfsmapiddaemon uses the value specified by thedomainorsearchdirective in the/etc/resolv.conffile, with the directive specified last taking precedence.In the following example, both the
domainandsearchdirectives are used. Thenfsmapiddaemon uses the first domain listed after thesearchdirective, which isexample.com.domain company.example.com search example.com corp.example.com
-
If the
/etc/resolv.conffile does not exist,nfsmapidobtains the NFS Version 4 domain name by following the behavior of thedomainnamecommand. Specifically, if the/etc/defaultdomainfile exists,nfsmapiduses the contents of that file for the NFS Version 4 domain. If the/etc/defaultdomainfile does not exist,nfsmapiduses the domain name that is provided by the network's configured naming service. For more information, see thedomainname(8) man page.