Reach external servers with URL under intranet domain

When setting up our windows domain controller we choose a domain mycompany.com for the domain controller's domain. The problem is we have servers OUTSIDE of our intranet that use e.g. server1.mycompany.com as URL. If we configure our Windows clients to use our domain controller as the DNS server, we cannot reach those servers. Even configuring our internet gateway router as the primary DNS server (and the DC as the seondary) we sometimes cannot reach them - probably ur domain controller somehow gets in the way.

What do we need to seamlessly use external and internal servers under the mcompany.com domain?
NilsITAsked:
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.

cdfsCommented:
Add an appropiate A-Record to your internal DNS. If your clients are using your domain-controller as primary DNS, configure it there, if they are using your gateway-router as primary DNS, configure it there.
0
NilsITAuthor Commented:
Dear cdfs, I am not sure I understand your solution:

The external servers are hosted at a hosting company, not within our network. They can be accessed from anywhere using the URL EXCEPT from within our intranet because the internal domaincontroller/DNS server thinks he is responsible for all URLS below mycompany.com. Using the IP we can access them from our intranet without any problem.

I would like to configure the domain controller/DNS server in a way that he answers those requests under the mycompany.com domain for which no server registered with the domain controller (i.e. because it is situated at the hosting company, not in our offices) by referring to the external DNS (of our internet access provider).
0
cdfsCommented:
At your internal DNS-server you'll have to configure A-records for the external servers.
Example:
external servers IP: 123.123.123.123

A-Record on your internal DNS: 123.123.123.123 in A external.mycompany.com

As your internal clients will use the internal DNS first, they will get for external.mycompany.com the appropiate external IP. As you said, reaching the external server by IP is no problem for you, so your actual problem is proper DNS-resolution. You have to configure it on your internal DNS.
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
NilsITAuthor Commented:
Works.
I was hoping to have a generic, less laborious solution (such as a switch for "go to public DNS if you, DNS server, don't know a URL in your domain) but the proposed solution does work well.
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
Active Directory

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.