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

Say I've operating and on which I want to host the zone file for

When I go to my registrar and purchase , I will tell my registrar that my nameservers are and

My question then is, why do I then also need to specify those nameservers in the zone file for ? Haven't I already told the .com nameservers where to lookup information on , making the NS records redundant?

Clearly I'm missing some crucial fact...

share|improve this question
up vote 9 down vote accepted

NS Records inside the zone are authoritative, the ones received from the registrar (the ones delegating the domain) are not, so if a server receives any difference from those records, the authoritatives win. Also, servers listed in the NS record will receive a NOTIFY in case of zone changes (so the slaves can check for updates and so on). One last thing, the RFCs 1034 and 1035 say that they must exist, so they must exist!

share|improve this answer
I wanted to post an answer exactly like that. But it came first. – Gopoi Apr 4 '11 at 1:46
Are there legitimate use cases for having the NS records not match the registrar's delegation? – Nathan O'Sullivan Apr 4 '11 at 1:49
@nathan Well you can have many NS records on your file, but some registrars will limit the number of name servers you can add on their interfaces. Now about having completely different records on the registrar and the zone file no I can't think on any right now. – coredump Apr 4 '11 at 2:12

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.