Many websites will say that vCenter 6x requires DNS lookup, but these steps and screenshots prove that you can install a new vCenter 6.7 with only an IP address and no DNS.
Start vCenter install from .iso file using Windows 10
vCenter install stage 1
8. Configure options for “set up appliance VM” — this gives the name for the VM on your host (and will affect naming of the datastore folders). Set the root password for the vCenter appliance here. Select deployment size – for most situations, the default of Tiny is fine unless you have more than 10 hosts. Select datastore – pick the datastore to create the VM into.
vCenter installation stage 2
Now to connect to your new vCenter VCSA without DNS..
Selfish plug time (sorry!)
Thanks for reading this article! I hope it helps you! If you have tips or feedback, please comment or send me an email so that others can benefit. I am a consultant in the Maryland/DC area in the USA. My specialties are Windows migrations (to 2016 and to Office 365 / Azure), VMware migrations, Netapp and SAN, and high availability / disaster recovery planning. If you would like help with your complex project, or would like a architectural review to improve your availability, please reach out! More information and contact can be found on the About page. – Amira Armond
11 thoughts on “How to install vCenter 6.7 (and 6.0 and 6.5) with no DNS, only IP address”
This looks very helpful. I may have to do this. I am attempting to have a working lab with vcsa 6.7 in my home.. I have a Unifi network, had set a domain, and then in the SSO setup , I DID use an fqdn..funny thing is it was working and now the dns is reporting as vcsa.xyz.com.xyz.com…I have no idea of how ro chang, as SSO only responds to vcx.xyz.com..Idea?
I tried a bogus ip for my DNS on a 6.7 u3 install and it denied me FYI for everyone. I am currently trying my router and ill know if it worked later today I imagine.
Let me know how that works for you. I am trying to set it up and use vrealize orchestrator but it keeps on giving me a lookup service error (even though I did all the steps on the KB ariticle)
When the 2nd type the Ip, system name. U can check system name is using ip or not. If not change to Ip then u can install it successfully
So using the IP Address as the FQDN instead of entering a full FQDN will let the VCSa work without a PTR record? This is the issue im having and will try again tonight when i get back to my homelab, and update with findings. This seems too easy to be true ( after messing with Bind9 for the last few days to no avail..)
Well, it worked when I tried it a few months ago. Let us know your experience!
6.7 U3 didn’t like ip address, or using hosts file with static entries. My solution was to use my Windows Server 2012 R2 virtual machine and enter the DNS entries.
You can edit the VCSA hosts file, so you don’t need a DNS Server on the local network. Here’s how: https://www.sysadmit.com/2020/08/vmware-instalar-vcsa-sin-dns.html
when install Vcenter 6.7 U1 , I have the error below, some can help me
2019-12-27T17:31:01.789Z – error: Could not get response for get request from url https://OPVTBGOSVCNT01.abj.gos.ftgroup:5480/: Error: getaddrinfo ENOTFOUND opvtbgosvcnt01.abj.gos.ftgroup opvtbgosvcnt01.abj.gos.ftgroup:5480
2019-12-27T17:31:01.789Z – error: VAMI is NOT accessilbe: https://OPVTBGOSVCNT01.abj.gos.ftgroup:5480/, err: Could not get response for get request from url https://OPVTBGOSVCNT01.abj.gos.ftgroup:5480/: Error: getaddrinfo ENOTFOUND opvtbgosvcnt01.abj.gos.ftgroup opvtbgosvcnt01.abj.gos.ftgroup:5480
how can I do the reverse
If I log into the vcenter UI I see the ipaddress but I’d rather see the FQDN .
Doing a ssh to the vcenter I see that the hostname is the FQDN .
Thanks for the blog, it helps.
I have query might be a simple one but I’m finding it difficult to execute. How to install vCenter 6.5 on a separate server rather than onto a Esxi host, if we install vCenter onto a Esxi host and if Esxi host happens to reboot or shutdown than entire vcenter will be down.
I tried installing it on another win server in demo env but it looks for certificate, but when i add esxi host ip or fqdn it works fine.
Can you please guide me through for the missing part or vCenter 6.5 onwards it only installed onto esxi host.
Have a nice time.