Subject: Re: reverse lookup file
To: None <itojun@iijlab.net>
From: Andrew Brown <atatat@atatdot.net>
List: tech-net
Date: 01/27/2000 13:48:48
> current netbsd src/etc/namedb configuration is:
>
>"127" supplies 127.in-addr.arpa. (contains "1.0.0")
>"0000:0000:0000:0000:0000:0000:000" supplies
> 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.int.
> (contains "1")
>
> My preference is the following. I use this configuration in my home.
> I split IPv6 address in 64bit boundary since most of IPv6 addresses
> has prefix length of /64 (so the filename will align nicely with
> others).
>
>"127.0.0.rev" supplies 0.0.127.in-addr.arpa. (contains "1")
>"0000:0000:0000:0000.rev" supplies 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.int.
> (contains "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0")
>"0.0.0.rev" supplies 0.0.0.in-addr.arpa. (contains "1")
>
> any opinions?
my preference is usually to declare the zone and the file with respect
to where they fall in the global address space. thus, since 127.0.0.1
is under the class a space 127.0.0.0/8, i use a file called 127.rev
for the zone 127.in-addr.arpa.
likewise, the loopback address for ip16 falls under
2.4 Address Type Representation
The specific type of an IPv6 address is indicated by the leading bits
in the address. The variable-length field comprising these leading
bits is called the Format Prefix (FP). The initial allocation of
these prefixes is as follows:
Allocation Prefix Fraction of
(binary) Address Space
----------------------------------- -------- -------------
Reserved 0000 0000 1/256
...
so i'd be tempted to do
zone "0.0.ip6.int" { type master; file "0.0.ip6.int"; };
and the same with the 0.in-addr.arpa zone.
sure, it makes the zone files a little more ugly to look at, but
they're *supposed* to be relatively static anyway. :)
--
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org * "ah! i see you have the internet
twofsonet@graffiti.com (Andrew Brown) that goes *ping*!"
andrew@crossbar.com * "information is power -- share the wealth."