Solved

Reach external servers with URL under intranet domain

Posted on 2012-03-15
4
303 Views
Last Modified: 2012-03-20
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?
0
Comment
Question by:NilsIT
  • 2
  • 2
4 Comments
 
LVL 5

Expert Comment

by:cdfs
ID: 37724501
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
 

Author Comment

by:NilsIT
ID: 37724687
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
 
LVL 5

Accepted Solution

by:
cdfs earned 500 total points
ID: 37734255
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
 

Author Closing Comment

by:NilsIT
ID: 37741186
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

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

As network administrators; we know how hard it is to track user’s login/logout using security event log (BTW it is harder now in windows 2008 because user name is always “N/A” in the grid), and most of us either get 3rd party tools, or just make our…
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now