Temporary failure in name resolution during check compliance of baselines or using update manager
search cancel

Temporary failure in name resolution during check compliance of baselines or using update manager

book

Article ID: 372878

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Cannot ping vCenter server from ESXi using hostname of vCenter.

Connection timed out; no servers could be reached when trying to nslookup vCenter server

2024-07-23T15:14:52Z esxupdate: 191545: esxupdate: ERROR:     raise Errors.MetadataDownloadError(metaUrl, None, str(e))
2024-07-23T15:14:52Z esxupdate: 191545: esxupdate: ERROR: vmware.esximage.Errors.MetadataDownloadError: ('http://<VC_hostname>:9084/vum/repository/hostupdate/CIS/CIS-ESXi-7.0-Addon-cumulative_metadata.zip', None, "('http://<VC_Hostname:9084/vum/repository/hostupdate/CIS/CIS-ESXi-7.0-Addon-cumulative_metadata.zip', '/tmp/tmp6xbmj_av', '<urlopen error [Errno -3] Temporary failure in name resolution>')")
2024-07-23T15:14:52Z esxupdate: 191545: esxupdate: DEBUG: <<<

When trying any port connections to vc from esxi, gets similar error:

[root@esxi:~] nc -z <vc_Hostname> 443
nc: getaddrinfo: Temporary failure in name resolution

However, using IP address, we can ping and test port connections.

DNS configurations looks fine on DNS server.

Environment

  • vSphere ESXi 7.0
  • vSphere ESXi 8.0

Cause

DNS client firewall rule is whitelisted or disabled causing name resolution failures.

ESXi is not able to download metadata because of an issue with the DNS firewall rule.

Resolution

To resolve this issue, select the problematic Host > Configure > System > Firewall > Edit > Then, make sure "Allow connections from any IP address" is selected.

 

Additional Information

Powered by Wolken Software