Use DNS to resolve HOSTS file entries on another network

We are in the process of moving from a government active directory domain to a one of our own. Our domain, DNS, DHCP is a brand new install of Windows Server 2012 R2 at the 2012 R2 forest level. After moving to our own domain, we will still need to access county servers and resources.

The county domain is on a different network in which our SonicWALL is currently handling the routing to. There are a few application servers on the county network that our old DNS did not resolve so we have previously been creating manual entries on the hosts file on each domain client.

Now that we are managing our own DNS, I was wondering the best way to go about resolving this breakdown when trying to reach these particular county servers without touching the host file in the future.

Is this an issue on the county end only? Is there something I need to do to my own DNS server for my domain clients? Do I update the hosts file on the DNS server and it will then tell my DNS clients?
Ricky HelmerNetwork EngineerAsked:
Who is Participating?
it_saigeConnect With a Mentor DeveloperCommented:
I would use a Forward Lookup Zone configured as a Secondary Zone instead.  Ultimately, it is because your clients do not know where to redirect their DNS requests for the county network.  Your DNS server can do this for them.

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.

All Courses

From novice to tech pro — start learning today.