I have a laptop configured in the following manner:
- Laptop is Server 2008 R2 member server running Hyper-V connected to the internet via a Wireless adapter
- One virtual machine is a Server Core 2008 R2 configured to run as a Domain Controller and DNS server; it has a single virtual NIC that is internal to the machine
- The host laptop is a member of that domain
- Several virtual machines running Windows XP to test various web browser versions; each machine is set up with two virtual NICs: one to the isolated domain, and one to a bridged internet connection per the following site.
Everything works well except that from time to time on boot-up I cannot get DNS to resolve (i.e., host comes up, domain controller comes up, I can ping IP address to virtual domain controller from host, but I can not ping the domain via domain name).
I have tried the following:
- Disable and re-enable network adapters, bridges, etc
- Various commands including "ipconfig /flushdns"
- Combinations of 1 & 2
- Enter the domain name in the hosts file (which does not work because of the increased security of Win2k8 R2 forcing domain resolution into dns)
- Restart dnscache service after reboot.
Solution #5 has been reasonably successful; however, it has started failing as well. Often a single reboot followed by restarting the dnscache service again will get my dns resolution working again (i.e., I can ping my domain name).
Any help would be much appreciated; a solution would cut ~15 minutes from my daily startup routine.