7:53 a.m.
No, Ganesha doesn't do a hostname to ip conversion at all. Instead,
when a client connects, it takes the IP address from the packet, and
does a reverse lookup on that to get the hostname. It then uses this
hostname to check the configured netgroups to see if it's allowed. The
IP to hostname is cached, so if a host changes it's *name* (but keeps
the same IP address) it will always be treated as the original hostname,
but changing the IP address should work, as the new address will show up
and be resolved to the original name.
Note that if this address had a different name before, and that address
was used by a client to connect to Ganesha, then the cache will have
that original IP to name mapping, and that will continue to be used.
Daniel
On 01/17/2019 04:29 AM, Suhrud Patankar wrote:
Hello All,
How does Ganesha handle the DNS-IP change for client?
I have given access permission to a client based on its DNS name.
There is a case when the client changes the IP address and updates the
DNS server.
However, I think Ganesha does the DNS lookup only at the time of the
config parsing.
The access permissions do not work for the client which has changed
its IP address.
What is the best way to handle this?
Thanks & Regards,
Suhrud
_______________________________________________
Devel mailing list -- devel(a)lists.nfs-ganesha.org
To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org