[dns-wg] Deprecation of ip6.int scheduled for 1 June 2006

On Wed, 15 Mar 2006 04:58:52 +0000, bmanning at vacation.karoshi.com said:

> On Tue, Mar 14, 2006 at 02:46:26PM -0800, Doug Barton wrote:
>> Andrei Robachevsky wrote:
>> > Dear Colleagues
>> > 
>> > In August 2005, the IETF published RFC 4159: 'Deprecation of "ip6.int"',
>> > as a Best Current Practice document. The RFC noted that maintenance of
>> > "ip6.int" is no longer needed and called on the Regional Internet
>> > Registries (RIRs) to decide when to stop providing support for the
>> > domain. The RIRs have jointly agreed to do this on 1 June 2006.
>> 
>> ... and there was much rejoicing. :)
>> 
>> Doug

> 	now if the IETF & the RIRs could just get rid of all that 
> 	deployed resolver code that looks for ip6.int by fiat.

As others said in this thread, this is probably not a big issue.  A
bigger issue is the fact that 0.1.0.0.2.ip6.int has been broken for a
long time.  I asked you several times to fix this :-)

Why does it matter?  For example, the resolver on Solaris (at least
Solaris 9 and newer) first looks in ip6.arpa.  When it doesn't find a
PTR there, it looks in ip6.int.  All delegations for 0.1.0.0.2.ip6.int
are lame and a BIND9 cache will produce timeouts for every single
query in this domain.  So, when you do reverse lookups for anything in
2001::/20 that doesn't have a mapping in ip6.arpa, you'll run into
this timeout and there's not much you can do about it except for ugly
hacks on your cache.  Incidentally, this happens for one of our IPv6
upstreams, which makes traceroute a real pain.

Thanks to opensolaris.org I have found an undocumented option for
resolv.conf (well, at least it's not in the man page). If you add

options v6revmode:single

then PTR queries will be restricted to ip6.arpa.

Removing ip6.int is fine, keeping broken zones is not.

--
Alex