> John Klos <john@sixgirls.org> said:

>
>> And, of course, add all the reverse (PTR) records, as well...
>
>Well, let's not confuse the issue here. PTR records don't go into the
>regular zone file.

I don't believe I said or inferred that they did!  :>
Rather, that your example only showed name->IP bindings and 
not the reverse (which is often needed for things like IP
based authentication).

>If you want to set up reverse DNS, create entries like
>so in /etc/namedb/named.conf:
>
>zone "131.27.216.IN-ADDR.ARPA" in {
>        type master;
>        file "db.216.27.131";
>};
>
>Note that the IN-ADDR.ARPA's IP part is reversed; this is an entry for

And, note that (your convention for) naming the actual static
database file shows the IP address in "normal form" (though
the last octet is omitted in your particular case).  Some folks
like to use "db.131.27.216" or "rev.216.27.131" or ...  It seems
to be largely a matter of choice -- though appears to be a
religious issue in some circles...  I think it gets particularly
messy if you have several subnets with discontiguous IP addresses.

<shrug>  Since I have only a few networks to deal with, I prefer
nice, simple names...  Network1.MyDomain, Network2.MyDomain, etc.
for forward (A record) databases; rev.Network1.MyDomain, 
rev.Network2.MyDomain, etc. for their corresponding reverse
(PTR) databases.  (My networks are small enough that I can
put each into it's own little file -- one pair of files per zone)

>216.27.131.x, as reva is 216.27.131.50.

--don