<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Take a moment to think before switching to the Google public DNS</title>
	<atom:link href="http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/</link>
	<description>Life, Technology, Music, and Soccer; not necessarily in that order</description>
	<lastBuildDate>Thu, 15 Apr 2010 17:35:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Precious</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-730</link>
		<dc:creator>David Precious</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-730</guid>
		<description>&lt;blockquote&gt;for example they may be able to estimate time spent on each site based on the time between requests to their DNS from your IP address&lt;/blockquote&gt;

I&#039;m not entirely sure that they could derive much of use from that;  with various browser addons and AJAXy pages making many automated requests and DNS lookups on behalf of the user, you cannot differentiate between &quot;the user must have finished on the last site they requested, and has moved on to another domain&quot; and &quot;the user is still reading (or doing something else), but their browser/other software is making requests (updating pages, AJAXy updates (Facebook live feed, Twitter, etc), checking for new software versions, etc...).</description>
		<content:encoded><![CDATA[<blockquote><p>for example they may be able to estimate time spent on each site based on the time between requests to their DNS from your IP address</p></blockquote>
<p>I&#8217;m not entirely sure that they could derive much of use from that;  with various browser addons and AJAXy pages making many automated requests and DNS lookups on behalf of the user, you cannot differentiate between &#8220;the user must have finished on the last site they requested, and has moved on to another domain&#8221; and &#8220;the user is still reading (or doing something else), but their browser/other software is making requests (updating pages, AJAXy updates (Facebook live feed, Twitter, etc), checking for new software versions, etc&#8230;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Precious</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-729</link>
		<dc:creator>David Precious</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-729</guid>
		<description>I share the worry that it&#039;s yet another data source for Google to obtain data from, although I don&#039;t think the data will be significantly more useful than other more in-depth user behaviour data they already collect.

I was curious about the speed though, and decided to knock up a quick script to compare Google&#039;s DNS servers to OpenDNS and to my ISP&#039;s resolvers (Virgin Media).  OpenDNS was faster than Google in my tests, and my ISP was significantly faster than both - &lt;a href=&quot;http://blog.preshweb.co.uk/2009/12/opendns-vs-google-speed-comparison/&quot; rel=&quot;nofollow&quot;&gt;see the results&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I share the worry that it&#8217;s yet another data source for Google to obtain data from, although I don&#8217;t think the data will be significantly more useful than other more in-depth user behaviour data they already collect.</p>
<p>I was curious about the speed though, and decided to knock up a quick script to compare Google&#8217;s DNS servers to OpenDNS and to my ISP&#8217;s resolvers (Virgin Media).  OpenDNS was faster than Google in my tests, and my ISP was significantly faster than both &#8211; <a href="http://blog.preshweb.co.uk/2009/12/opendns-vs-google-speed-comparison/" rel="nofollow">see the results</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Take a moment to think before switching to the Google public DNS &#124; JoshCampoverde.com -- Topsy.com</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-728</link>
		<dc:creator>Tweets that mention Take a moment to think before switching to the Google public DNS &#124; JoshCampoverde.com -- Topsy.com</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-728</guid>
		<description>[...] This post was mentioned on Twitter by robwatts 忍者, Ryan Nelson. Ryan Nelson said: Think about this before you begin to use Google DNS: http://bit.ly/6Xni20 [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by robwatts 忍者, Ryan Nelson. Ryan Nelson said: Think about this before you begin to use Google DNS: <a href="http://bit.ly/6Xni20" rel="nofollow">http://bit.ly/6Xni20</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: campo</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-727</link>
		<dc:creator>campo</dc:creator>
		<pubDate>Thu, 03 Dec 2009 19:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-727</guid>
		<description>Oz, it&#039;s possible they can gain use of out derivative statistics (for example they may be able to estimate time spent on each site based on the time between requests to their DNS from your IP address).  That&#039;s the first thing that comes to mind to me and seems like a reasonable possibility.  It would also have use in marketing/advertising areas.  Google can probably create a very widely used DNS and with a very large population using it they may be able to make fairly accurate estimates into things like the traffic to any given site in the world, etc.  Large amounts of basic information could lead to statistical analysis that provides valuable information.</description>
		<content:encoded><![CDATA[<p>Oz, it&#8217;s possible they can gain use of out derivative statistics (for example they may be able to estimate time spent on each site based on the time between requests to their DNS from your IP address).  That&#8217;s the first thing that comes to mind to me and seems like a reasonable possibility.  It would also have use in marketing/advertising areas.  Google can probably create a very widely used DNS and with a very large population using it they may be able to make fairly accurate estimates into things like the traffic to any given site in the world, etc.  Large amounts of basic information could lead to statistical analysis that provides valuable information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: campo</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-726</link>
		<dc:creator>campo</dc:creator>
		<pubDate>Thu, 03 Dec 2009 18:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-726</guid>
		<description>Andrew, Thanks for the link to the privacy policy for the Public DNS.  I&#039;ll have to take a read through it later.

My first thoughts from the quote you posted is &quot;does not permanently store&quot; PII:  

How long does that mean it&#039;s stored for?
Does it really *need* to be stored?
How can we be sure it is eventually deleted?</description>
		<content:encoded><![CDATA[<p>Andrew, Thanks for the link to the privacy policy for the Public DNS.  I&#8217;ll have to take a read through it later.</p>
<p>My first thoughts from the quote you posted is &#8220;does not permanently store&#8221; PII:  </p>
<p>How long does that mean it&#8217;s stored for?<br />
Does it really *need* to be stored?<br />
How can we be sure it is eventually deleted?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oz</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-725</link>
		<dc:creator>Oz</dc:creator>
		<pubDate>Thu, 03 Dec 2009 18:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-725</guid>
		<description>Well, through a DNS query they only have the IP address of the host making the request, and it is only done once and then cached by your machine for a period of time, so only the first hit is seen by google.  So it can build a picture of sites an IP address may visit over time, but that&#039;s about it.

What I fail to see is why would using googles DNS be any better than using your ISPs caching DNS server?  I suppose if your ISP is really bad their DNS servers may be dog slow.</description>
		<content:encoded><![CDATA[<p>Well, through a DNS query they only have the IP address of the host making the request, and it is only done once and then cached by your machine for a period of time, so only the first hit is seen by google.  So it can build a picture of sites an IP address may visit over time, but that&#8217;s about it.</p>
<p>What I fail to see is why would using googles DNS be any better than using your ISPs caching DNS server?  I suppose if your ISP is really bad their DNS servers may be dog slow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-724</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Thu, 03 Dec 2009 18:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-724</guid>
		<description>wow, it took me like 10 minutes to find this and read it: http://code.google.com/speed/public-dns/privacy.html</description>
		<content:encoded><![CDATA[<p>wow, it took me like 10 minutes to find this and read it: <a href="http://code.google.com/speed/public-dns/privacy.html" rel="nofollow">http://code.google.com/speed/public-dns/privacy.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Stott</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-723</link>
		<dc:creator>Andrew Stott</dc:creator>
		<pubDate>Thu, 03 Dec 2009 18:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-723</guid>
		<description>Good points, Josh.   

Privacy (or lack therof) was my first thought when I saw the announcement, too.   Looks like Google is, for now, taking the right approach in at least addressing the privacy and logging concerns.   They have a page up (http://code.google.com/speed/public-dns/privacy.html) that discusses what info they&#039;re collecting and storing.   

&quot;We built Google Public DNS to make the web faster and to retain as little information about usage as we could, while still being able to detect and fix problems. Google Public DNS does not permanently store personally identifiable information.&quot;

Hopefully they&#039;ll stick to this!   :)

andrew</description>
		<content:encoded><![CDATA[<p>Good points, Josh.   </p>
<p>Privacy (or lack therof) was my first thought when I saw the announcement, too.   Looks like Google is, for now, taking the right approach in at least addressing the privacy and logging concerns.   They have a page up (<a href="http://code.google.com/speed/public-dns/privacy.html" rel="nofollow">http://code.google.com/speed/public-dns/privacy.html</a>) that discusses what info they&#8217;re collecting and storing.   </p>
<p>&#8220;We built Google Public DNS to make the web faster and to retain as little information about usage as we could, while still being able to detect and fix problems. Google Public DNS does not permanently store personally identifiable information.&#8221;</p>
<p>Hopefully they&#8217;ll stick to this!   <img src='http://www.joshcampoverde.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AmpLiF1eR</title>
		<link>http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/comment-page-1/#comment-722</link>
		<dc:creator>AmpLiF1eR</dc:creator>
		<pubDate>Thu, 03 Dec 2009 18:46:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.joshcampoverde.com/2009/12/03/take-a-moment-to-think-before-switching-to-the-google-public-dns/#comment-722</guid>
		<description>exactly.... I was thinking the same thing when I saw that specific post some minutes ago and saw your article... good point!</description>
		<content:encoded><![CDATA[<p>exactly&#8230;. I was thinking the same thing when I saw that specific post some minutes ago and saw your article&#8230; good point!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
