Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is probably a noob question but I have a SMB network with AD domain corp.local and external hosting with a DNS domain

As a result if I add web services on an internal machine (like we can't resolve it internally.

I tried adding a domain to my DNS servers with no entries in it (expect the SOA created automatically). My understanding was that my server should attempt to resolve within the forward lookup zone and when it cannot just forward the request to the outside world.

But that doesn't happen if I add a primary zone to the server then I can't resolve any addresses.

If it had worked I'd then have started to add cool-app x.y.z.b etc to the local lookup zone so that those resources on the LAN can be resolved when you're in the office.

My guess is I'm making a silly mistake or that I'm trying to do something the wrong way and I thought the hivemind was the best way to try to find out...

share|improve this question
up vote 5 down vote accepted

Create a new forward lookup zone called Inside that zone, create an A record with a blank host name and specify the IP address you want it to resolve to.

I do this all the time and it works perfectly.

share|improve this answer
Would that work for things like OWA? – Paul D'Ambra Aug 26 '10 at 12:49
I checked and that works beautifully. Is their a way of pointing to internal resources by name so that if I change the IP I only have to do it in one place? – Paul D'Ambra Aug 26 '10 at 12:57
It absolutely works for OWA. Also, you can try to create a C record instead of an A record. I've never done this but don't see why it won't work. – Jason Berg Aug 26 '10 at 13:03
I just got here from a google search looking do to this exact thing for OWA, and your advice worked. If I could click up on you ten times I would :) – Bill Weiss Oct 20 '10 at 17:35

If your internal DNS has a primary zone for, and it's empty, then any queries to that zone will be returned as "non-existent" because the server thinks it knows all about that zone (and the request doesn't exist in what it knows).

If your internal DNS has no zone that matches, it knows nothing; if it's configured to forward or recurse the query, it will look to the outside world (assuming it's connected somehow) and find the entry (if one exists in the external DNS server).

If you want, you can maintain your own zone internally, which has different entries than the external DNS server; but it's probably not advisable as your employees would be easily confused by the different DNS entries when they're inside vs outside the office. You can however, duplicate the external entries, and add additional internal entries. Just keep the primary zone you have now; duplicate all the external entries ( for example), and add your internal-only entries (such as

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.