A complete block?

[Kevin Darcy]

Randall Badilla wrote:

> On Fri, 1 Jun 2001, Kevin Darcy wrote:
> > > $INCLUDE /var/named/Interno/1.168.192.in-addr.arpa
> > > $INCLUDE /var/named/Interno/X.168.192.in-addr.arpa
> > > $INCLUDE /var/named/Interno/.
> > > $INCLUDE /var/named/Interno/.
> >
> > What is "$INCLUDE /var/named/Interno/." intended to accomplish? Looks like
> > you're trying to $INCLUDE a Unix directory into your zone file. Not a file
> > *in* that directory, mind you, but the directory *itself*. That's not going
> > to work. A Unix directory is basically binary data and named isn't going to
> > be able to parse it sanely as a resource record.
>
> Ok. the $INCLUDE /var/named/Interno/. was to say "ident"
> $INCLUDE /var/named/Interno/.....in-addr.arpa, etc.

> > Why don't you just put all of the PTR records directly into the
> > 168.192.in-addr.arpa zone file? I'm not sure what the point is of all those
> > $INCLUDEs...
>
> Well, I ask because I didn't know how to do it!

Just add the PTR records to the zonefile, e.g.

@               IN      SOA     xxxxxxxxx. root.xxxxxxxxx.
(
                        2001051706      ; Serial Number
                        10800           ; Refresh
                        7200            ; Retry
                        604800          ; Expire
                        86400           ; ttl
                )

                        IN      NS      xxxxxxx.
;
2.1   in    ptr    host1.example.com.
3.2   in    ptr    host2.example.com.

This would create a reverse record for 192.168.1.2 pointing to host1.example.com
and a reverse record for 192.168.2.3 pointing to host2.example.com. The name of
a reverse record is the address with the octets reversed (e.g. 192.168.1.2
-> 2.1.168.192) with "in-addr.arpa" appended to the end, i.e. the full name of
192.168.1.2's reverse record is 2.1.168.192.in-addr.arpa. Since the zone origin
is 168.192.in-addr.arpa, you only need to supply the first two octets of the
PTR name, e.g. "2.1". Understand now? No need for $INCLUDEs.

If the zone file gets too big, or if you want to distribute maintenance of the
address space to other organizations/nameservers, then you may want to consider
delegating subzones from it. But let's not get into that right now...


- Kevin