OK, the questions looked similar so that is why I asked. Nonetheless I wouldn’t recommend your described setup.
First: Although the backup DC contains a replica of OpenLDAP and its own DNS, it does still depend on some servces provided by the master DC. At a cold boot you may end up in a loop where the master DC VM cannot be launched because the VMM services require contacting the master etc.
Also, if you lose your master DC, you can only promote the backup to a master DC. This would result in your master becoming tied to a physical machine. Similar to @Moritz_Bunkus in the other thread I’d really not recommend having a UCS DC physically tied to a hardware.
It could potentially be done, but I’d really recommend using a basic hypervisor of your choice that is independent from UCS instead if you don’t have the possibility to host it on different hardware. It will be easier and safer for upgrades and if things break, rolling back all VMs is easier than rolling back the host that is also hosting its local copy of the OpenLDAP DB etc.
Also looking at other products like oVirt / Red Hat Virtualization for example they explicitely do not recommend hosting your DNS infrastructure on the virtualization hosts that it also relies on DNS at runtime itself. Similar things apply to Active Directory and failover clustering etc.