Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

Is it possible to emulate my customer production environment inside my AD domain by just creating the same domain inside my primary DNS server ?

Can I created DNS zone (STUB) just for the sake of listing few database servers and application servers and then for the other DNS records eg. MX, NS and the other refer to the REAL MX record entry so that my Exchange Server email flow is unaffected to ?

because if I just create A record in my current domain for some of the servers, the FQDN is not exactly what I want.


share|improve this question
up vote 1 down vote accepted

A stub zone is not what you want. You'll want to create a standard forward lookup zone for the domain in question, if I'm understanding what you're trying to accomplish.

I'm currently doing something similar in order to troubleshoot a suspected DNS issue with an external email provider. I simply created a new standard forward lookup zone in my AD integrated DNS for the external domain and populated it with the relevant records for the external domain (A, MX, etc). This essentially makes my AD\DNS server authoratative (internally) for the external domain, eliminating the suspected problems with the external name servers.

share|improve this answer
thanks for the explanation mate, all is clear now :-) – Server System Specialist Jan 11 '11 at 11:23
Glad to help... – joeqwerty Jan 11 '11 at 11:31

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.