vCenter Server Appliance 6.7 DNS

Recently, got to know from a customer who have a vCenter Server Appliance 6.7 that went down after a reboot. The services refused to come up.

Looking at the error generated, it looks something similar to this KB. However, this was the the similar Error RC code which returns 1 instead of 11.

So we went asked the customer what actually happens and the results was they change a new DNS server with new IP but did not update vCenter Server. This is a big impact!

Why is this so? If you have deploy a vCenter Server, the requirement for forward and reverse DNS is required as a prerequisites else the vCenter Server Installation wizard will not proceed further. So while the vCenter Sever is still running without been updated on the new DNS, services on the vCenter start to act abnormally.

A reboot will completely bring it down as nothing will start without DNS. The only service that will start is the vSphere Client service.

There are few ways to change your DNS which I am going to list them below:

1. Login to your Direct Console and update the DNS. This will be persistent and resolved the customer issue in our case.
2. SSH and update the DNS. This is not persistent and will not be saved when you reboot the vCenter Server. This method should be done with a VMware support as accessing the SSH to perform any task which results in breaking the vCenter Server can be result in a unsupported vCenter Server.

Lastly, what should be the proper procedure when you want to change DNS? Login into your VAMI and change the DNS first before making changes to your existing DNS.

Comments

Popular posts from this blog

Why VMware or Why Not after Broadcom?

VMware by Broadcom, A New Chapter Forward

VMware vExpert 2024 Application is Now Open!