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

I have these domains:

Sub domains "a" and "b" are under the same zone of in the GUI (albeit with an extra dot in the hostname field). The zone is separate from the zone that hosts a and b.

When I delegated a secondary/slave to "" I don't see any NS record or any records for


  • Should a secondary of zone (that has a and b) include NS records for c? (I can't resolve anything under c

  • What is the expected value of the NS for in this case before and after delegation?

  • Is this expected behavior for DNS in general? (for secondaries to not have NS records for some subdomains)

  • What are my options to make c resolve or redirect at the secondary?

I was able to get to resolve at the NS for if I created a stub zone (a Windows 2003 feature) for I had to do this for each stand alone secondary.

My intent is to get a better understanding of the problem, that is platform agnostic, and prevent this from happening again in the future.

share|improve this question

If is a delegated zone then there should be NS records for it in, as well as A records if the nameserver is in-baliwick. For example, in      IN  NS   IN  A

These records should be returned by both primary and secondary servers for Before delegating the zone there would be no NS records for it.

I don't know how to achieve this on Windows Server ;-)

share|improve this answer
What does in-baliwick mean? – LamonteCristo Aug 10 '12 at 2:51
@makerofthings7 That the hostname of the nameserver is within the domain which it is serving. This means that the parent zone needs to return an A record for the nameserver, otherwise the resolver can't find it. – mgorven Aug 10 '12 at 3:16 should have an entry for c that includes the 2 or more NS records. It also needs to know the address(es) of any nameservers within the subdomain. Querying a nameserver for should return the nameservers. Running nslookup in command mode with the following command should give you an idea what is happening.


dig if available is the tool of choice. A command like dig should return data required to locate the nameservers. This will include NS records, A, and optionally AAAA records.

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.