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 ?
It very well could. If this is a production environment, having a second DNS server (and a second domain controller) would be a best practice, anyway.
If you wanted to give it a try, you could just add the DNS role to one of your other machines as a test before you take the plunge and build a whole new server.
If you're able to fix the problem with a second DNS server, can you report back? I'd love to know if it fixes the problem.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Virtualization] >> General >> DNS Issue on Hyper V DC 
DNS Issue on Hyper V DC - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread