On Nov 7, 2016, at 11:54 AM, Jesus Cea <[email protected]> wrote:

The problem is NFS4_DOMAIN. If not defined, it is generated from the DNS
(reverse DNS mapping of the IP). The IP in the global zone is a public
IP with reverse mapping. The IP of the internal zone (in the etherstub)
is in the private range and has no reverse DNS. The result was a
NFS4_DOMAIN mismatch.

If you run your own (cacheing) DNS servers, it is trivial to make them authoritative for 1.168.192.in-addr.arpa or whatever and make the domain names match.  Problem solved.

-r


Reply via email to