Delayed ESXi Host Name Resolution in vCenter Server
Article ID: 420226
Updated On:
Products
Issue/Introduction
If name resolution on a DNS (Domain Name System) server is taking too long, the vCenter Server's vpxd.log may output warning logs similar to the following, indicating that "address resolution took too long".
This issue typically occurs when vCenter Server attempts to connect to ESXi hosts using their FQDN (Fully Qualified Domain Name) and can be an indicator of overall communication instability within the environment.
YYYY-MM-DDTmm:hh:ss.XXX+09:00 warning vpxd[XXXXX] [Originator@XXXX sub=IO.Connection opID=WorkQueue-XXXXXXXX] Address resolution took too long; <resolver p:0xXXXXXXXXXXXXXXXX, 'host3.domainX.local:443', next:(null)>, async: true, duration: 30028msec
YYYY-MM-DDTmm:hh:ss.XXX+09:00 warning vpxd[XXXXX] [Originator@XXXX sub=IO.Connection opID=WorkQueue-XXXXXXXX] Address resolution took too long; <resolver p:0xXXXXXXXXXXXXXXXX, 'host1.domainX.local:443', next:(null)>, async: true, duration: 30036msec
YYYY-MM-DDTmm:hh:ss.XXX+09:00 warning vpxd[XXXXX] [Originator@XXXX sub=IO.Connection opID=WorkQueue-XXXXXXXX] Address resolution took too long; <resolver p:0xXXXXXXXXXXXXXXXX, 'host2.domainX.local:443', next:(null)>, async: true, duration: 30037msec
YYYY-MM-DDTmm:hh:ss.XXX+09:00 warning vpxd[XXXXX] [Originator@XXXX sub=IO.Connection opID=WorkQueue-XXXXXXXX] Address resolution took too long; <resolver p:0xXXXXXXXXXXXXXXXX, 'host5.domainX.local:443', next:(null)>, async: true, duration: 30037msec
YYYY-MM-DDTmm:hh:ss.XXX+09:00 warning vpxd[XXXXX] [Originator@XXXX sub=IO.Connection opID=WorkQueue-XXXXXXXX] Address resolution took too long; <resolver p:0xXXXXXXXXXXXXXXXX, 'host4.domainX.local:443', next:(null)>, async: true, duration: 30037msec
YYYY-MM-DDTmm:hh:ss.XXX+09:00 warning vpxd[XXXXX] [Originator@XXXX sub=IO.Connection opID=WorkQueue-XXXXXXXX] Address resolution took too long; <resolver p:0xXXXXXXXXXXXXXXXX, 'host6.domainX.local:443', next:(null)>, async: true, duration: 30038msec
Environment
vCenter Server 8.0
Cause
The primary cause for these logs being continuously generated is likely the impact of degraded DNS server responsiveness.
vCenter Server performs name resolution to establish and maintain communication with its managed ESXi hosts.
If name resolution is prolonged due to DNS server load or latency, vCenter Server will experience a timeout, resulting in the warning logs mentioned above.
Resolution
Since the root cause lies with DNS server responsiveness, collaborate with your network administrators to investigate and improve the communication path between the DNS environment and vCenter Server.
- Check DNS Server Status:
- Verify that the DNS server itself is not experiencing high load (CPU/Memory/Disk I/O).
- Confirm that the DNS service is running normally and without response delays.
- Check Network Path:
- Use tools like ping and traceroute to check for network latency between vCenter Server and the DNS server.
- Ensure that DNS queries are not being blocked or restricted by firewalls or routers along the network path.
Additional Information
Japanese : https://knowledge.broadcom.com/external/article/418728
Feedback
