We have a number of clients who are keen to go virtual when buying new servers, but are at the lower end of the scale when it comes to need. Basic setup for these guys is:
2 ESX hosts, 1 SAN, 1 Physical Server for AD, DNS, DHCP, etc.
The question I've been trying to answer is, how to not have to go to a second physical server. This has come about as vCentre wont run on an AD server. DNS is the main issue as an AD integrated DNS is the easiest to manage (for me anyway). What really needs to be in DNS to make vMotion work? Do we need just a forward lookup zone with the ESX host names to keep vCentre happy? Or does it need to know about the whole network? These networks, once set up, will typically not change. Can we just put entries into host files?
I
2 ESX hosts, 1 SAN, 1 Physical Server for AD, DNS, DHCP, etc.
The question I've been trying to answer is, how to not have to go to a second physical server. This has come about as vCentre wont run on an AD server. DNS is the main issue as an AD integrated DNS is the easiest to manage (for me anyway). What really needs to be in DNS to make vMotion work? Do we need just a forward lookup zone with the ESX host names to keep vCentre happy? Or does it need to know about the whole network? These networks, once set up, will typically not change. Can we just put entries into host files?
I