smackthat
Enthusiast
Enthusiast

ESX cannot resolve the DNS name of VMware vCenter Update Manager patch store...

Just upgraded from 3.5U6 to 4.1 and now have this error: "ESX cannot resolve the DNS name of VMware vCenter Update Manager patch store. Ensure that the Update Manager server name can be resolved from ESX hosts"

Supposedly resolved in 4.0 U1 but I'm clearly past that.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101476...

I cant find any arcticles/KBs for v4.1 and I tried the fix for 4U1 and it doesnt work.

Any ideas?

0 Kudos
3 Replies

It really can't resolve? Have you tried to ping vCenter from ESX using short name and fqdn? Do vCenter server have more than 1 IP?

Marcelo Soares

VMWare Certified Professional 310/410

Virtualization Tech Master

Globant Argentina

Consider awarding points for "helpful" and/or "correct" answers.

Marcelo Soares
0 Kudos

I concurr regarding pinging the VUM by bothe hostname and IP from the Service Console. If The Service Console is not resolving DNS, check /etc/resolv.conf and if all else fails, you could add the VUM hostname to each ESX Server /etc/hosts file.

-J

+The Invisible Admin+ If you find me useful, follow my blog: http://johnborhek.com/
0 Kudos

You could also do a "nslookup" on the IP of the vum to ensure it is resolving correctly. After the update you do have DNS showing up in the Configuration Tab for the host? Can you esx host also ping talk to the DNS servers? just a few more things... performing the ping to IP will rule out DNS though but you will still need it working right Smiley Wink






Cheers,

Chad King

VCP-410 | Server+

Twitter: http://twitter.com/cwjking

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

Cheers, Chad King VCP4 Twitter: http://twitter.com/cwjking | virtualnoob.wordpress.com If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos