<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
We've done some limited testing. It is as you'd expect. They have good
locality information for their deployment footprint. Places where they
don't have good/similar deployments have bad/not-so-bad results. It's
pretty good in the US. It's less good in Europe and even less good in
the Asia/AU region. <br>
<br>
That's not surprising as we don't deploy our networks lock step w/
google. Depending on where the client lives they will get marginally
faster to slower response times by using Google DNS. In some places
like Australia users would incur a pretty hefty hit since they're being
redirected from local servers to servers over 100ms away.<br>
<br>
Overall, I think a lot of the things they've done w/ the product are a
"good idea" (pre-fetching/caching/maintaining state independent of
query) but I think the locality loss probably doesn't compensate for
it... At least for internet presences with large deployments worldwide.
Averaging all Akamai users worldwide, for instance, would probably get
worse performance overall because google just doesn't know where all
the best Akamai nodes are. We had the same problem with Akamai trying
to GSLB internal Yahoo stuff. We can do a better job since we know our
network whereas they had to guess at it from what they could glean via
external probing from limited locations.<br>
<br>
It's not worse (and maybe better) than any other open dns service. I'm
not sure I'd try to make the claim it would speed up your web browsing
experience though. It may speed up your DNS lookup experience but it
can definitely slow down your web browsing experience.<br>
<br>
east<br>
<br>
Florian Weimer wrote:
<blockquote cite="mid:87iqcfewme.fsf@mid.deneb.enyo.de" type="cite">
<pre wrap="">* Patrick W. Gilmore:
</pre>
<blockquote type="cite">
<pre wrap="">Data exists. Maybe even someone here is using a CDN and can provide
data. Then we can make an informed decision. Until then, posturing
and name calling is ... silly. :)
</pre>
</blockquote>
<pre wrap=""><!---->
Debian uses DNS tricks to distribute mirror load. It proved to be
necessary because we can't be too picky about mirror offers, and the
network operators tend to be not very upfront about choke points. A
solution based on redirects would likely confuse unofficial mirrors.
(Our own client doesn't support them, but that could be fixed.)
_______________________________________________
dns-operations mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dns-operations@lists.dns-oarc.net">dns-operations@lists.dns-oarc.net</a>
<a class="moz-txt-link-freetext" href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations">https://lists.dns-oarc.net/mailman/listinfo/dns-operations</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>