Using dynamic client IP addressing

By default, the z/OS NFS server expects to communicate with clients based on a static client IP address. The server can also use the dynamic host configuration protocol (DHCP) to accept dynamic client IP address changes. To use dynamic client IP addressing, specify the dhcp server site attribute. The default attribute, nodhcp, tells the server to use the static IP algorithm.

To use dynamic IP addressing, the client must:

Have a constant host name that the NFS server can identify it by.
Dynamically update the authentication DNS (dynamic name server) with new IP addresses whenever they change.
Maintain the TTL (time to live) value that the authentication DNS server specifies to any caching DNS server, based on the frequency with which system IP addresses might change. The larger the TTL value, the greater the possibility that the caching DNS server will have obsolete information. If dynamic addressing is used, the TTL value should be small, ideally zero, but a small value defeats the benefit of caching, so a compromise must be set with the understanding that cached values can become obsolete during the TTL interval and report incorrect information to querying systems like the NFS server.

Regardless of the dhcp/nodhcp attribute value, the z/OS NFS server itself continues to have a static IP address.