Re: I-D ACTION:draft-iab-dns-choices-00.txt

[Mark Andrews <Mark_Andrews@isc.org>]

> > 	I'm seeing the same thing w/ the IP6.INT -> IP6.ARPA
> > 	transition.  It is taking a long time because people left
> > 	the IP6.INT crutch in place.  We really should not be
> > 	shipping resolvers that use IP6.INT.  Stop making the old
> > 	lookups and the new records will appear.
> > 
> > Mark Andrews, ISC
> 
> 	actually, when the queries stop (e.g. the old resolvers
> 	are upgraded) the servers will be turned off. the new 
> 	delegations (and by extention RR types) need to be visable
> 	first.  
> 
> --bill

	The problem is that new resolvers try IP6.ARPA then if they
	don't get a answer they try IP6.INT.  You will never see
	the IP6.INT queries drop off as there will always be a
	significant number of addresses that have neither a IP6.ARPA
	or IP6.INT PTR record.  The only way out of this is for OS
	vendors to be brave enough to stop using IP6.INT as a crutch
	or for someone to be brave enough to put in "IP6.INT DNAME
	IP6.ARPA".  Once that is done you can say to the OS vendors
	that it is now pointless to try IP6.INT if you don't get a
	IP6.ARPA response and the later can't exist.

	Look like KAME has bitten the bullet.  Hopefully the rest will
	follow.  The following is from FreeBSD.
	Note: I havn't checked any of the others.

	MFC: now e.f.f.3.ip6.arpa is delegated, we no longer need to
	query ip6.int

	Mark

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>