<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.3">
</HEAD>
<BODY>
On Thu, 2009-12-03 at 18:37 -0500, Joe Abley wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 2009-12-03, at 18:14, Noel Butler wrote:
> On Thu, 2009-12-03 at 13:45 -0600, Jorge Amodio wrote:
>> No harm Bob, thanks for your private response.
>>
>> > At the very least I'm certain they are gathering statistics about what
>> > you're looking at.
>>
>> As I mentioned in NANOG-L, if a substantial number of folks use their
>> resolvers that will be a lot of juicy statistics that can be monetized in
>> some way and I'm sure google has the brain power to find the way.
>>
>>
>
> fight fire with fire, anycast their IP's to your own DNS resolvers :)
I'm not sure exactly what fire you're trying to fight, there.
What next, null-route Yahoo! because you don't want your users checking their mail there? Intercept and modify coffeegeek.com traffic because you don't appreciate the low rating they gave your favourite Gaggia?
</PRE>
</BLOCKQUOTE>
<BR>
huge difference, there's no comparison. google do nothing for nothing, there will be an agenda, what could that be, well they are after all a search engine who love to gather stats on everybody and everything, for their own purposes, not because they are good netizens.<BR>
<BR>
Using my home DSL, a DNS lookup from the U.S takes 190-216ms, locally, it takes 9-11ms, to what get the same thing, minus stats collected on you, minus googles decided search redirection it will likely give you for web browsing.<BR>
<BR>
I can do without the irritation of any of my users blaming us for sites taking forever to start to load, in every case I've come across at any time in this past decade, its always been because X is using Y's DNS.<BR>
<BR>
</BODY>
</HTML>