Domain Controller limited connection / No internet

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 =
Default gateway is

DNS forwarders have been set-up to

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?
Rob LeaverSr. Network & Server EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The DNS Forwarders have to be setup to point to authoritative DNS servers not the gateway IP.
Rob LeaverSr. Network & Server EngineerAuthor Commented:
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.
What happens if you run tracert

How is the Virtual Switch configured for the DC?
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

How do you have your network adapter setup in the virtual machine settings?  Is it in bridged mode?
Rob LeaverSr. Network & Server EngineerAuthor Commented:
The hose is joined to the domain

- Its using a virtual switch however it doesn't seem to  be communicating

When i do a tracert it just halts straight away at which is the vm

It's an issue with the virtual switch, but i can't figure out what
Cliff GaliherCommented:
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.
Is it an external virtual switch?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
If we're seeing a problem with tracert to an IP address, it's not a DNS/forwarding issue.

Please describe how you have the virtual switch configured as that is likely the issue.
Rob LeaverSr. Network & Server EngineerAuthor Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.