> > http://v6fix.net/docs/ip6.int show that a number of current
> > resolvers are still falling back to IP6.INT. Until these
> > resolvers are corrected to be arpa (nibble) only the load
> > on the IP6.INT servers will only increase.
>
> presuming IANA leaves that delegation in place...
> if they pull it, the load goes to the INT servers...
> me, i'd need a COMPELLING reason to pull the delegations.
> i've not heard one yet... but its not my call. :)
>
> --bill
Ask Sun why they still fallback to IP6.INT.
Ask the glibc developers why they still fallback to IP6.INT.
I suspect the answers will be: "there is still information
under IP6.INT that is not available under IP6.ARPA,
in-particular local information and we can't break local
reverse lookups for our customers."
To be able to close down IP6.INT you have to get all the
vendors to stop querying IP6.INT or remove the data available
under IP6.INT globally.
Deploying empty IP6.INT zones in recurive nameservers would
allow local IP6.INT to still succeed without creating load
on the global servers. However I would only recommend this
course if we can't convince Sun and glibc to fix there
resolvers.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
