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 a question regardin this Zone file from "

$ORIGIN     ; designates the start of this zone file in the namespace
$TTL 1h                  ; default expiration time of all resource records without their own TTL value  IN  SOA (
              2007120710 ; serial number of this zone file
              1d         ; slave refresh (1 day)
              2h         ; slave retry time in case of a problem (2 hours)
              4w         ; slave expiration time (4 weeks)
              1h         ; maximum caching time in case of failed lookups (1 hour)
              )  NS    ns                    ; is a nameserver for  NS    ns.somewhere.example. ; ns.somewhere.example is a backup nameserver for  MX    10  ; is the mailserver for
@             MX    20 ; equivalent to above line, "@" represents zone origin
@             MX    50 mail3              ; equivalent to above line, but using a relative host name  A             ; IPv4 address for
              AAAA  2001:db8:10::1        ; IPv6 address for
ns            A             ; IPv4 address for
              AAAA  2001:db8:10::2        ; IPv6 address for
www           CNAME          ; is an alias for
wwwtest       CNAME www                   ; is another alias for
mail          A             ; IPv4 address for,
                                          ;  any MX record host must be an address record
                                          ; as explained in RFC 2181 (section 10.3)
mail2         A             ; IPv4 address for
mail3         A             ; IPv4 address for

Why is these lines necessary?:  NS    ns                    ; is a nameserver for
ns            A             ; IPv4 address for

We already know that the is the default name server, right? Then why should we specify its IP-address? Isn't this zone file in the name server, I mean if we are looking at it why do we want the ip-address of the server that has the file we are already looking at?

share|improve this question
up vote 0 down vote accepted

The information presented by the authoritative name server must be consistent with information presented elsewhere.

In this case, a resolver has used a glue record to find this name server. The delegation and name information found here must match the delegation from the TLD (the NS record in the example), and the host information found here must match what was provided as extra information by the TLD, the glue record (the A record in the example).

share|improve this answer
Let's say is the only name server for this Zone. Does that mean that the only place we can find this zone file is in that name server? If yes, do we still need the A record for it? – user951732 Sep 20 '11 at 19:42
Yes, when you only have one NS record, you're telling clients that this is the only place to find the zone's data. And yes, you would still need an A record; a DNS server must present consistent data. Yes, they know your IP if they're talking to it, but DNS caches heavily; it's important that your server confirm that it is where a client was told that it was. – Shane Madden Sep 20 '11 at 19:55
Thank you very much, very helpful information. Cheers – user951732 Sep 20 '11 at 20:03

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.