Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt

[Paul Vixie <[e-mail]>]

> From: Nicholas Weaver <[e-mail]>
> Date: Thu, 28 Jan 2010 11:13:29 -0800
> 
> > I have to wonder whether the simpler solution to fix this is
> > not just to deploy more resolvers closer to the edge.
> 
> Actually, that IS the fix:  Use the ISP's recursive resolver.
> 
> This is necessary if you want to use something OTHER than the ISP's
> recursive resolver to work well on today's Internet.

i love how somebody else (CDN providers) violate all existing assumptions
(by creating requestor-specific DNS replies) which then makes the Internet
work "less well" for lots of people... who are then constrained from doing
what were previously reasonable things (like using distant recursive servers).

> Do you want third-party DNS providers to not suck for youtube, akamai,
> Google, and a good fraction of the net people use every day?  If so, you
> need this.

if youtube and akamai and google want to suck, let them suck.  they weren't
the first movers and they won't be the last and redrawing the protocol to
support their flawed technical model is not in the global system's interest.

this incoherency should be dealt with more harshly, perhaps by minimizing
TTL to 5 minutes, and sharing a single DNS cache across global providers.

any CDN who relies on what i call "stupid DNS tricks" to deliver their
advantage should upgrade to something at the WWW layer, and leave DNS alone.

especially with DNSSEC coming.