Cannot connect to host errors after upgrading ESX(i) hosts (4042703)

A new/rebuilt host is successfully added to vRanger, but no backups can be taken from it. Any number of "can't read {pathname}" error statements can be present in the job log.

Upon inspection of the "My Inventory" screen, the hostname of the ESX(i) host appears as "{hostname}." . This trailing "." is the cause of the issue, as it impedes proper name resolution by vRanger when it is attempting to connect to the host. This trailing "." appears because the host itself has had its "Domain" field (on the vSphere client's "Configuration" page for the host, under the "DNS and Routing" item) removed, and it is blank.

This field cannot be left blank; it must either have a valid DNS zone name entered, or it can be set to a "dummy" DNS zone name, provided some sort of resolution mechanism is provided to resolve the host to that FQDN/IP. So, either a "dummy" DNS zone with the name/ip of the host(s) must be setup, hosts files placed on the ESX(i) hosts/vRanger machine, or an actual "A" and "PTR" records winthin an actual DNS zone must be created. Once this is done, the hostname shows-up correctly in vRanger (i.e. FQDN), and backups/restores progress normally.