I have a physical box that has about 12 HyperV servers running on it, one of which is the Primary DC. Whenever a power cycle is done on the physical server (due to updates) the DNS does not come back up for about 30 minutes, any ideas ?
While the DNS is down the DHCP is also down, its a big issue that I am hoping is a simple fix.
It has some pointers on what might cause slow DNS startup. I'd hesitate before I'd point at this being a Hyper-V problem as the virtualization layer is pretty transparent. I'd lean more toward this being some other configuration issue.
How is a member of the Domain with no real configuration set to it, just a Enterprise 2008 Server with Hyper-V running as a service. The DC is a virtual server located on this box and is the only DNS server we have. The DC also runs the DHCP scope.
Would a additional DNS server resolve this issue ?