How many NS records should be in the 0.0.127.in-addr.arpa zone?

Barry Margolin barmar at bbnplanet.com
Tue Sep 21 14:47:30 UTC 1999


In article <199909202236.SAA28022 at fw1-a.osis.gov>,
Joseph S D Yao  <jsdy at cospo.osis.gov> wrote:
>> > According to the DNS and BIND book the zone file for 0.0.127.in-addr.arpa
>> > should contain an NS record for each server in your domain (see the 3rd
>> > edition page 67).  First question - is this a correct assumption?
>> 
>> This doesn't seem correct.  I don't have my copy of DNS & BIND handy
>> so I can't check your reference.
>
>D&B does NOT say that.  It gives an example, in which there are two (2)
>NS records instead of 1.  It makes no statement why it does so, or
>whether you should use 1 or 2 or N, N > 2.

Here's my guess why people may have done it that way: you can use the same
file on all your servers.

Actually, it doesn't really matter *what* NS records you put in
0.0.127.in-addr.arpa.  NS records are only used by caching servers, but all
servers should be configured as authoritative for this zone.  You need to
have at least one NS record in there to keep BIND from complaining "No NS
records at zone top", but other than that it doesn't really care what they
are.

>I realized today why that might be.  Some systems start other network
>aware programs before 'named'!  ;-?  If they cannot reach their own
>local 'named', they might be able to reach the other one.

Since only named looks in zone files, how does listing multiple NS records
help that?

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list