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

Pim van Pelt pim@ipng.nl
Thu, 25 Jul 2002 07:36:49 +0200


John,

At RIPE42 (the last meeting) it was proposed to start delegating in
ip6.arpa (and keeping ip6.int for backwards compatibility) for each new
request made after the 1st of July. The .int variant is supposed to be
deprecated by RFC3152, but still widely used in the field for both 3ffe
and 2001 networks.

I remember having checked up on some of my own 2001 allocations a couple
of months ago, and was quite sure that there was no .arpa delegation for
me. Some weeks ago it mysteriously appeared. It's somewhere on my
wishlist to create both delegations (ip6.int and ip6.arpa) by generating
the one from the other, like Kim said.

Debian also had a 'messup' a year ago when they suddonly decided to only
resolve in .arpa, rendering Debian boxes without a reversed resolver for
a while. They reverted to .int resolving due to complaints from the
field ( ;-) ).

I think it is time to start resolving .arpa zonefiles. I'd advise you to
simply keep both and use something along the lines of what Kim has
proposed (the Makefile).

houdoe
Pim

On Wed, Jul 24, 2002 at 09:56:32PM -0400, John Fraizer wrote:
| 
| On Wed, 24 Jul 2002, Kimmo Suominen wrote:
| 
| > | From:    John Fraizer <tvo@EnterZone.Net>
| > | Date:    Wed, 24 Jul 2002 21:19:24 -0400
| > |
| > | OK.
| > |
| > |  (1) What is nibble format?
| > 
| > $ORIGIN 2.0.0.0.c.0.0.b.0.0.9.2.e.f.f.3.ip6.arpa.
| > 8.1.5.7.c.1.e.f.f.f.2.e.4.0.2.0 IN PTR beowulf.gw.com.
| > 
| > Regards,
| > + Kim
| 
| OK.  That's how I've been doing things thus far.  Now, I find a new
| problem.
| 
| It doesn't appear that ARIN has delegated ip6.arpa for 2001:4f0::/35 to
| me.
| 
| ; <<>> DiG 9.1.0 <<>> @arrowroot.arin.net soa
| 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.f.4.0.1.0.0.2.ip6.arpa
| ;; global options:  printcmd
| ;; Got answer:
| ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46690
| ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
| 
| ;; QUESTION SECTION:
| ;1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.f.4.0.1.0.0.2.ip6.arpa. IN
| SOA
| 
| ;; AUTHORITY SECTION:
| 4.0.1.0.0.2.ip6.arpa.   10800   IN      SOA
| arrowroot.arin.net. bind.arin.net. 2002041212 10800 3600 1209600 10800
| 
| ;; Query time: 100 msec
| ;; SERVER: 198.133.199.110#53(arrowroot.arin.net)
| ;; WHEN: Wed Jul 24 21:45:16 2002
| ;; MSG SIZE  rcvd: 149
| 
| 
| 
| > 4.0.1.0.0.2.ip6.arpa
| Server:         arrowroot.arin.net
| Address:        198.133.199.110#53
| 
| 4.0.1.0.0.2.ip6.arpa
|         origin = arrowroot.arin.net.
|         mail addr = bind.arin.net.
|         serial = 2002041212
|         refresh = 10800
|         retry = 3600
|         expire = 1209600
|         minimum = 10800
| 
| > 0.f.4.0.1.0.0.2.ip6.arpa
| Server:         arrowroot.arin.net
| Address:        198.133.199.110#53
| 
| ** server can't find 0.f.4.0.1.0.0.2.ip6.arpa.: NXDOMAIN
| 
| 
| Isn't THAT special.  It doesn't look like the ip6.arpa zone has been
| updated at ARIN since April 12, 2002.
| 
| 
| [whois.arin.net]
| EnterZone, Inc (ENTERZONE-V6)
|    6227 Headley Road
|    Gahanna, OH 43230
|    US
| 
|    Netname: ENTERZONE-V6
|    Netnumber: 2001:04F0:0000:0000:0000:0000:0000:0000/35
| 
|    Maintainer: V6ZN
| 
|    Coordinator:
|      Fraizer, John (JF1998-ARIN)  John.Fraizer@ENTERZONE.NET
|      +1 614 554-4356
| 
|    Domain System inverse mapping provided by:
|    NS1.ENTERZONE.NET
|    NS2.ENTERZONE.NET
| 
|    Record last updated on 18-Jul-2002.
| 
| It would be nice if the ip6.arpa records were REALLY delegated to my
| nameservers.
| 
| 
| ---
| John Fraizer              | High-Security Datacenter Services |
| EnterZone, Inc            | Dedicated circuits 64k - 155M OC3 |
| http://www.enterzone.net/ | Virtual, Dedicated, Colocation    |
| 
| 
| _______________________________________________
| 6bone mailing list
| 6bone@mailman.isi.edu
| http://mailman.isi.edu/mailman/listinfo/6bone

-- 
---------- - -    - - -+- - -    - - ----------
Pim van Pelt                 Email: pim@ipng.nl
http://www.ipng.nl/             IPv6 Deployment
-----------------------------------------------