Restart a cluster, VC can't find ESX because DNS not started (hosted on a vm)

[zemotard]

Hi, I own a cluster with 2 AD servers running on 2 VM.

After having stop all the infrastructure, I need to restart esx.

But My vc doesn't recognize the ESX because AD and DNS are not started.

What's the best practise ?

Set esx name and IP in the lmhost file on the VC Server ?

Start manually both AD using the VIC on each ESX ?

Set a third DNS server ?

Thanks a lot

Bye

[vmroyale · Accepted solution]

Not sure if its best practice or not, but putting entries for the ESX hosts in the hosts file on that VC box sounds like the easiest way to solve this problem.

[derekn]

I experienced this same issue, we place the records in our local hosts file on the VC, then after getting annoyed with the slow load up times ended up placing a 3rd physical DNS server just for this. It increased the uptime drastically as VC is so DNS dependent. If you have the hardware and justification it is probably easier just doing a 3rd DNS server.

[zemotard]

Ok, thanks for your feedback.

[azn2kew]

That's why when you planning to virtualize Domain controllers and DNS on VM, make sure to seperate each DC and DNS servers on seperate clusters in case one cluster failed, the other cluster still functional and also best is to have 1 set of physical DC & DNS servers too. To maximize all DNS failured redundancy, place all ESX hosts IP in local VC server hosts files that way its all protected. If all DC & DNS are on VM, make sure to set up rules so that DRS not accidentally move all DC & DNS on the same cluster. You dont' want to place all eggs in one basket.

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Regards,

Stefan Nguyen

iGeek Systems Inc.

VMware, Citrix, Microsoft Consultant