Hi, Setup: physical hardware: Dell T300 server, dual nic interface software: windows 2008 r2 server Configuration: the above hardware runs a virtual machine via hyper-v. This VM runs windows server 2008 R2 and exchange 2010; it is the only domain controller in a domain. One of the NICS on the pohysical hardware is designated as the virtual network adaptor. Problem: using DNS on the physical server appears to work fine, but using it on the virtual server does not. The symptom is a failure to find any external site on the first attempt. On the second attempt it works. I'm guessing that, byt the time of the 2nd attempt, it has got the details and cached them. This problem affects all clients as they all use this dns on the server The VM has the dns configured with the same forwarder as the physical system so that should not be an issue. I think it must be a timing issue of some sort but increasing the timeout to the forwarder does not make any difference. NSLOOKUP shows that it is trying to get an AAAA record as well as an A record (AAAA being the IPV6 equivalent of A) as the interface has IPV6 enabled (has to be there apparently or other things dont work). I would be grateful for any suggestions as this is seriously holding up deployment of a new server into production.