<div>
The DNS Forwarders have to be setup to point to authoritative DNS servers not the gateway IP.
</div>


<div>
Okay - first that isn't much help because I can't seem to get any connection to the internet to provide a authoritative dns server.
</div>


<div>
What happens if you run tracert 4.2.2.2?<br />
<br />
How is the Virtual Switch configured for the DC?
</div>


<div>
How do you have your network adapter setup in the virtual machine settings? &nbsp;Is it in bridged mode?
</div>


<div>
The hose is joined to the domain <br />
<br />
- Its using a virtual switch however it doesn't seem to &nbsp;be communicating <br />
<br />
When i do a tracert it just halts straight away at 192.168.89.10 which is the vm<br />
<br />
It's an issue with the virtual switch, but i can't figure out what
</div>


<div>
Ipconfig /all from the host, the DC guest, and a guest that works please? Also, try configuring the DC to not use forwarders. Allow it to use root hints. And the NIC should only list the DC itself (or other DC's) for DNS Servers.
</div>


<div>
If we're seeing a problem with tracert to an IP address, it's not a DNS/forwarding issue.<br />
<br />
Please describe how you have the virtual switch configured as that is likely the issue.
</div>


<div>
It was the external switch. After a couple hours of troubleshooting I found that the interface of the physical switch was mapped to the wrong external switch. There is 2 phyiscal NICS on the server and for some reason it was receiving DHCP on one of the ports which i believe was causing a problem - . After I mapped the correct external switch to the correct phyiscal NIC and disabled the other NIC i was able to get access.
</div>


<div>
<div class="content wysiwyg-content">
I have a Hyper-V host that is hosting 2 virtual machines. <br />
<br />
One of the virtual machines is the domain controller, running DHCP and DNS<br />
<br />
DC Static = 192.168.89.10<br />
Default gateway is 192.168.89.1<br />
<br />
DNS forwarders have been set-up to 192.168.89.1<br />
<br />
The host has internet - and all the computers connected to the network have internet access - however the domain controller can't resolve IP addresses but can ping the internal network. <br />
<br />
I have the DNS set on the VM NIC to loop back and the DG to 89.1 <br />
<br />
Am i forgetting something or have i mis configured something?
</div>
</div>


I have a Hyper-V host that is hosting 2 virtual machines. 

One of the virtual machines is the domain controller, running DHCP and DNS

DC Static = 192.168.89.10
Default gateway is 192.168.89.1

DNS forwarders have been set-up to 192.168.89.1

The host has internet - and all the computers connected to the network have internet access - however the domain controller can't resolve IP addresses but can ping the internal network. 

I have the DNS set on the VM NIC to loop back and the DG to 89.1 

Am i forgetting something or have i mis configured something?

Domain Controller limited connection / No internet

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.

Microsoft Virtual Server

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.