[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: DNSOPS presentation
- To: Ed Jankiewicz <edward.jankiewicz@sri.com>
- Subject: Re: FYI: DNSOPS presentation
- From: Brian E Carpenter <brian.e.carpenter@gmail.com>
- Date: Sat, 03 Apr 2010 04:16:28 +1300
- Cc: IPv6 Operations <v6ops@ops.ietf.org>, 6man <ipv6@ietf.org>
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=LT1ckBXXP8QfKTxk9UQAoPQxnnse/iuTi3Mcs43QSGMc0jpcFus3atoKWpeP2tmziP 3yt+bFVtAWRB9rzhemUsDpZwxTHznHXsTVASogyJbW3K6vXCxdt8vyI5kznKpgXdIT3B Mv3x1GvTykeqHOsAzck/d/+61lIa9wW2gx3Z8=
- In-reply-to: <4BB127CE.7020703@sri.com>
- Organization: University of Auckland
- References: <4BB127CE.7020703@sri.com>
- User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
As every successful IPv6 user on Windows XP knows, the hack
would break all Windows XP IPv6 usage (since it can't resolve
DNS over IPv6 at all).
I prefer the current situation, where occasionally I have to
disable IPv6 manually due to being on an IPv6-broken network
where DNS serves up AAAA records and my regular tunnel is too
slow. This seems OK, since people using v6 on XP are normally doing
so as conscious early adopters.
I do think that Google's solution to this, i.e. being selective
about who gets the AAAA records in the first place, is much less
of hack with less harmful side effects.
Surely a better hack would be for recursive resolvers in IPv6-broken
networks not to serve up AAAA records at all? Tunnel users could
always find another resolver.
Regards
Brian