nslookup of the hostname of the ESXi in the command prompt of the windows jump server and it returns an incorrect IP address or returning two IP addresses where one of them is a incorrect/duplicate IPnslookup <Hostname of ESXi>Working IP Address : ##.###.##.##.###Non-working IP Address : ##.###.##.##.###
In vCenter server: /var/log/vmware/vpxd/vpxd.log
YYYY-MM-DDThh:mm:ss:uuu warning vpxd[63037] [Originator@6876 sub=MoHost opID=HostSync-host-37931-7f75b4b7] host [vim.HostSystem:host-37931,] connection state changed to NO_RESPONSE
YYYY-MM-DDThh:mm:ss:uuu warning vpxd[64705] [Originator@6876 sub=MoHost opID=HostSync-host-37931-73b9cd07] host [vim.HostSystem:host-37931,] connection state changed to NO_RESPONSE
YYYY-MM-DDThh:mm:ss:uuu warning vpxd[64784] [Originator@6876 sub=IO.Connection opID=HB-host-37931@1686-52d66fc6-SWI-4b70ddca] Failed to connect; <io_obj p:0x00007f4dd49726c8, h:152, <TCP '##.###.##.##.### : (port)'>, <TCP '##.###.##.##.### : (port)'>>, e: 110(Connection timed out), duration: 31436msec
The issue arises when vCenter Server receives multiple A and PTR records for a specific ESXi host.
While attempting to connect to one of these records, vCenter Server encounters an unreachable IP address.
To resolve the issue delete the incorrect PTR records in the DNS server.