Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Zone for Internal and External DNS

Posted on 2007-11-24
Medium Priority
Last Modified: 2008-05-31
I have a DNS question which I just kind of need a 'Yes, that is right' or 'No that is OK' answer to.  I am having some weird issues with my firewal using SMTP relay forwarding email to my SPAM firewall.  It appears to be DNS related.  Emails almost seem confused as to where to be sent to. This is a network I have come into that, from what I am told, has had a lot of issues.  I have found that there is two external DNS servers and two active-directory integrated internal DNS servers.  The two external DNS servers host the zone for our external servers and services.  I then checked our internal to check its setup and configuration only to discover that the same zone hosted on our external DNS is also hosted on our internal DNS, along with the local zone.  I have a pretty good grasp of DNS and In the past, I have always setup my internal DNS servers to point to my external DNS servers that hosted the zone for anything public.  Am I wrong in thinking the zone on my internal DNS that is also hosted on my external should not be there?
Question by:jabar5623
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2

Expert Comment

ID: 20344697
There is nothing wrong with this setup, as long as the internal and external are the same DNS (i.e  replicas) and not 2 seperatly maintained databases. As long as the external faceing DNS's are not forwarding requests, this meets the accepted standard.


Expert Comment

ID: 20344784
You are thinking right - Get rid of those external zones on your internal DNS - they should not be there.

Author Comment

ID: 20347188
The internal and external are seperately maintained, i.e. they are not sending Dynamic updates to one another.  The issue I am seeing is that my SPAM firewall and any of my pc's on my network cannot resolve  This can be resolved outside of the organization because my external DNS will resolve those requests but since this zone resides internally, my internal DNS will not answer the request because it sees it is has the zone but no record for  At least this is my assumption.  If I delete this zone on the internal DNS, it will have to forward the request to my external where the request can then be resolved, correct?
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.


Expert Comment

ID: 20347447

This is any easy fix.. there are too possibilities

1 your internal DNS name and external DNS names are same. e.g. your AD domain is and your internet zone is
If so you need to create a host record pointing to mail.yourdomain .com on your DNS (and all other servers hosted outside your network)

2.your internal DNS name and external DNS names are different e.g your AD domain is xyz.local and your external zone is - in that you will have to create a zone on your internal DNS and add appropriate entries for www, mail etc.
it will NOT be possible to have dynaic updates in either scenario - anytime you change provider or ip address of any server out on the network you will HAVE to manually update IP address for that record in your internal dns.


Author Comment

ID: 20347612
There is already a zone called on my internal and external DNS.  My internal DNS also has xyz.local. The issue I am seeing is that because the internal DNS zone does not have any resource records for, it only responds with 'non-existent domain' when is queried. Our external does have the records under but internal DNS does not forward the request since it has the zone So I could add the record to my internal DNS under the zone or I could delete the domain from my internal DNS so that it will forward requests for to my external DNS where those DNS resource records exist and can be resolved, correct?

Accepted Solution

jigans earned 300 total points
ID: 20347659
Since your internal DNS is xyz.local theoritically you should be able to delete

but from experience -  I would recommend instead of relying on outside DNS to perform resolution - just create an A record on your internal DNS for each entry which belongs to  I have seen strange results - occuring at firewall if you have external interface - referenced to public DNS - your internal machines will still get strange results if you rely on external DNS.

Again it will only happen if your external interface(S) has a Public DNS record - but if you have everything hosted outside your company then it will not be a problem

If you have all services hosted outside then delete zone - if you don't then you will need A entries for
mail & whatever else lives on internet IP addresses.


Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Active Directory security has been a hot topic of late, and for good reason. With 90% of the world’s organization using this system to manage access to all parts of their IT infrastructure, knowing how to protect against threats and keep vulnerabil…
Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
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 …
Suggested Courses

715 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