Slow dns resolution

My network is made of up a Windows 2012r2 server running Hyper-v
The server has 32 gig of ram and dual nic cards in teamed together.
The server is not part of the active directory and is running dns.

The hosted OS is SBS 2011 16 gig of ram has been allocated to it.
The SBS is the AD and the dns is a split zoned dns.
x.local
x1.com

in the dns I have A host record for www.x1.com and a blank A host recrord (same as parent).
I am able to suft to https://www.x1.com from both OS.
From the host server when I try to access https://www.x1.com/admin it works fast and fine but,
when I try to access the same site from the hosted os it times out. This happens on desktops which are part of the AD.

The DNS on the hosted OS is getting 4013 warning.  This is the only AD on the network.

Please advise
LVL 1
HalCHubAsked:
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.

A KarelinCommented:
try this
0
HalCHubAuthor Commented:
Could this be the reason why the host OS can get to www.x1.com/admin but the guest and desktops can not ?

What happens is the browser times out.
0
A KarelinCommented:
Is www.x1.com resolved from both OS, hyper-v host and VM, and does nslookup have the same result? But  browsers have time out for the site page. Can you try to open another site page? Make ipconfig /flushdns and try again. Can that site have acl for "admin" or redirect?
0

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
HalCHubAuthor Commented:
I fixed it...

I removed the dns records for x1.com from the guest server (AD) and added a forwarder to the host (no ad). The dns records for x1.com where already in the hosts dns.
0
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
Microsoft Virtual Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.