Hello,
I have a Vsphere 6.7 system that I'm attempting to update to the last patch level. I have disabled IPv6 as we've not migrated our management network yet.
I'm running into an issue with a timeout attempting to contact hostupdate.vmware,com. The root cause appears to be esxcli's attempt to contact hostupdate.vmware.com using it's IPv6 IP. An nslookup from the commandline on the Vsphere box returns:
[root@VspgereBox:~] nslookup hostupdate.vmware.com 8.8.8.8
Server: 8.8.8.8
Address 1: 8.8.8.8 google-public-dns-a.google.com
Name: hostupdate.vmware.com
Address 1: 2600:141b:13:793::2ef g2600-141b-0013-0793-0000-0000-0000-02ef.deploy.static.akamaitechnologies.com
Address 2: 2600:141b:13:795::2ef g2600-141b-0013-0795-0000-0000-0000-02ef.deploy.static.akamaitechnologies.com
Address 3: 96.6.22.67 a96-6-22-67.deploy.static.akamaitechnologies.com
Using the IPv4 name doesn't appear to work:
[root@VsphereBox:~] esxcli --debug software sources profile list --depot=http://a96-6-22-67.deploy.static.akamaitechnologies.com/software/VUM/PRODUCTION/ma
in/vmw-depot-index.xml
[MetadataDownloadError]
Could not download from depot at http://a96-6-22-67.deploy.static.akamaitechnologies.com/software/VUM/PRODUCTION/main/vmw-depot-index..., skipping (('http://a96-6-22-67.deploy.static.akamaitechnologies.com/software/VUM/PRODUCTION/main/vmw-depot-index...', '', 'HTTP Error 400: Bad Request'))
url = http://a96-6-22-67.deploy.static.akamaitechnologies.com/software/VUM/PRODUCTION/main/vmw-depot-index...
Please refer to the log file for more details.
This appears to be a known issue based on an earlier thread:
ESXi hosts generating IPv6 AAAA DNS records
Is there a workaround other than enabling IPv6?
Thanks
John
