The Domain Name System (DNS) server returns more than one address defined for an FTP server's host name. Usage of the z/OS FTP client specifying that host name was expected to attempt to establish a connection to each of the listed addresses until one of them was successful. However, the client terminated after the first connection attempt failed.
Messages similar to the following are produced:
EZA1554I Connecting to: FTP.MYCORP.COM 10.11.12.13 port: 21.
EZA2590E recv error from getNextReply - EDC8130I Host cannot be reached. (errno2=0x74500442)
EZA1475I Connection with FTP.MYCORP.COM terminated
The z/OS FTP client will attempt a connection to another address in the list returned from DNS when there is no response from an address within the configured MYOPENTIME period (or overridden with the TIMEOUT option on the FTP command). However, if the remote address returns a "Connection refused" response (a RESET packet), the process will terminate without any further connection attempts.
Resolving The Problem
- Ensure that the list of IP addresses returned from the DNS server is correct for the host name supplied.
- Ensure that the FTP server software is functional whenever the TCP/IP stack on each of the listed hosts is up.
- Specify another host name that selects a desired subset of the IP addresses returned. Or specify an individual IP address instead of a host name.
- Repeated attempts to use the FTP client with the hostname specified will probably result in the DNS server returning the list of IP addresses in a different order. It is likely that one (or more) of the other addresses will work.
NOTE for z/OS 1.11 and above:
- Check the cache entry using a
NETSTAT RESCACHE DETAIL (HOSTNAME FTP.MYCORP.COMcommand. A retry after the reported Expired Time will retrieve a new list. Contact the administrator of the authoritative DNS server for that domain to see if a shorter Time To Live (TTL) can be configured (if appropriate). Note that the reported expiration will be reported as GMT (UCT) unless the TZ environment variable has been set for the user issuing the NETSTAT command.
- Clear the resolver cache using a
MODIFY RESOLVER,FLUSHcommand. However this will (temporarily) affect performance for all DNS queries on the system.
- Override the TCPIP.DATA input used for this FTP session to use an input that has the NOCACHE statement specified.
If resolver caching is enabled on the system (the default), retry attempts will get the same results until the cached entry expires. One of these options may be used:
Was this topic helpful?
15 June 2018