[6bone] ip6.int or ip6.arpa or BOTH?

[Kimmo Suominen]

I'm using $ORIGIN in the IPv6 reverse files to avoid excessively long
lines.  I also find it easier to move machines from one subnet to
another by moving an entire PTR entry to be under a different $ORIGIN
as opposed to having to edit the line too.  This is especially useful
when there are moves from one assigned block to another.

I wish I could do "popd" or some sort of "cd .." with $ORIGIN.  Or
just limit the scope, maybe something like

    {
	$ORIGIN xxx.
	foo IN PTR yyy.zzz.
    }

But that's probably off-topic here, already.

+ Kim


| From:    Garrett Wollman <wollman@lcs.mit.edu>
| Date:    Wed, 24 Jul 2002 22:03:09 -0400
|
| In article <mit.lcs.mail.6bone/20020725005333.DB36B7E04@beowulf.gw.com> you w
| rite:
|
| >I've been maintaining both ip6.arpa and ip6.int in nibble format, so
| >that at least all local nodes will be able to resolve names.  I only
| >edit files for ip6.arpa, and use a little Makefile to produce the
| >ip6.int files.
|
| There's really no need to go to all that work, since the records in
| the zones are all the same but for the origin.  We have:
|
| zone "2.1.0.0.a.1.2.1.2.0.0.2.ip6.int" {
|   type master;
|   file "primary/rev.ipv6.db";
| };
|
| zone "2.0.0.0.1.e.c.1.e.f.f.3.ip6.int" {
|   type master;
|   file "primary/rev.ipv6.db";
| };
|
| ..and everything works just peachy.  (Actually, not quite everything,
| because there's one address (prefix::1) which needs to map to
| different things in our 6to4 and 6bone spaces, but we'll fix that by
| giving both duties to one machine.)  The zone file uses only
| origin-relative addresses and does not contain a $ORIGIN directive.
|
| -GAWollman
|
| --
| Garrett A. Wollman   | [G]enes make enzymes, and enzymes control the rates of
| wollman@lcs.mit.edu  | chemical processes.  Genes do not make ``novelty-
| Opinions not those of| seeking'' or any other complex and overt behavior.
| MIT, LCS, CRS, or NSA|         - Stephen Jay Gould (1941-2002)
|