Documentation and debugging for NFSv4

[Greg Veldman]

On Tue, May 26, 2020 at 07:07:37PM +0100, Norman Gray wrote:
> > On FreeBSD this is specified with the -domain
> > arg to nfsuserd (which looks like it can also be put in rc.conf).
> > On Linux it's set with the Domain keyword in /etc/idmapd.conf.
> > Various implementations of the software attempt to calculate a
> > default domain if none is given, using different methods to do
> > so.  It's much safer to pick something yourself and explicitly
> > set it everywhere.
> 
> I'm currently trying to work out if there's a way of doing that that 
> doesn't involve making config edits to a lot of machines.  I think the 
> answer is 'no', and that this is going to be painful whichever decision 
> I make about the domain name.
> 
> Solaris appears 
> <https://docs.oracle.com/cd/E19120-01/open.solaris/819-1634/epubp/index.html> 
> to support a rather nice client-side search for a magic DNS TXT record.  
> Cute, but as far as I can see that's a Solaris-only thing.

Yes, you're probably going to have to touch all the machines
(or have your config management tool of choice do it for you).
But note that you should only need to change either the arg
to nfsuserd (which can be put in rc.conf) or the one line in
idmapd.conf.  This has nothing to do with the system's DNS
domain name, name resolution search order, etc.  There's no
real requirement (that I know of) to have it reflect anything
about your DNS.  You could just make it "foo" everywhere, and
as long as all the hosts agree it should work.

-- 
Greg Veldman