This is very basic for anyone to have a rresolvable name and IP before we install or upgrade vcenter
When you deploy the vCenter Server Appliance or Platform Services Controller appliance, similar to any network server, you can assign a fixed IP address and an FQDN that is resolvable by a DNS server so that clients can reliably access the service.
When you deploy the vCenter Server Appliance or Platform Services Controller appliance with a static IP address, you ensure that in case of system restart, the IP address of the appliance remains the same.
Before you deploy the vCenter Server Appliance or Platform Services Controller appliance with a static IP address, you must verify that this IP address has a valid internal domain name system (DNS) registration.
When you deploy the vCenter Server Appliance, the installation of the Web server component that supports the vSphere Web Client fails if the installer cannot look up the fully qualified domain name (FQDN) for the appliance from its IP address. Reverse lookup is implemented using PTR records.
If you plan to use an FQDN for the appliance system name, you must verify that the FQDN is resolvable by a DNS server.
Please mark this as "correct" or " Helpfull" if this answers your query.
No, I dont have any FQDN set up. I always connect by IP and always connect only from the same local subnet. And when you set FQDN for some server and DNS server goes down, then usually no any server starts shutting down its services. And why the IP address must change after restart? I dont have any local FQDN registered in my DNS server for vmware products. Never was, altough I used vCenter about 10y now, beginning from version 4. But now was the first time I see it shuts down its own services. It was never doed this before. I have he newest 6.7 vCenter, with all updates. No, vCenter had not such requirements. The only software, I remember, that wanted also reverse PTR was vSphere Data Protection. This is fact - 1) I dont have FQDN set in DNS 2) I still use vCenter successfully. So, how I can use it then when exist such requirements?.
If it works without DNS since version 4.1 as you say, then why this post? I don't understand you...
You shut down the DNS server and vCenter didn't work anymore. DNS is a prerequisite for deployment and installation. This is clearly stated in the documentation. So why should it be different later in operation? The fact that you have only configured your environment with IP addresses is another matter. This is possible and supported.
Basically it is quite simple:
Does everything work without DNS if you only have IP addresses configured and no FQDNs? If so, then vCenter does not need DNS.
However, if you have "strange" behavior or errors without DNS, assume that vCenter still needs DNS for some reason. So simple.
An Internet connection is not needed, but then some features like the Online Health Checks and the Update Manager are limited.
I dont talk about installation. My question is very simple - Do vCenter server usually shuts down its services when DNS server goes down? Yes or Not?
I dont have AD.