<?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: Google Public DNS Could Be Data Treasure Trove for Google</title>
	<atom:link href="http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Tue, 14 Feb 2012 04:15:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: willemijns</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-526079</link>
		<dc:creator>willemijns</dc:creator>
		<pubDate>Sat, 12 Dec 2009 16:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-526079</guid>
		<description>I agree with you SL, i submit to AV...</description>
		<content:encoded><![CDATA[<p>I agree with you SL, i submit to AV&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SL</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-526067</link>
		<dc:creator>SL</dc:creator>
		<pubDate>Sat, 12 Dec 2009 15:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-526067</guid>
		<description>Whoa...be careful folks!  The &quot;DNS changer&quot; link in the message above could easily be a trojan.

Google &quot;dns changer&quot; for more info.</description>
		<content:encoded><![CDATA[<p>Whoa&#8230;be careful folks!  The &#8220;DNS changer&#8221; link in the message above could easily be a trojan.</p>
<p>Google &#8220;dns changer&#8221; for more info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: velociraptor</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-525972</link>
		<dc:creator>velociraptor</dc:creator>
		<pubDate>Sat, 12 Dec 2009 09:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-525972</guid>
		<description>Link removed</description>
		<content:encoded><![CDATA[<p>Link removed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harsh Agrawal</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-521982</link>
		<dc:creator>Harsh Agrawal</dc:creator>
		<pubDate>Sat, 05 Dec 2009 09:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-521982</guid>
		<description>I tried Google Public DNS and its fast
My report shows almost 50% less latency but when I changed name server for one of domain
it took time to reflect that changes on my local PC and as soon as I changed it to Open DNS 
I can see name server change</description>
		<content:encoded><![CDATA[<p>I tried Google Public DNS and its fast<br />
My report shows almost 50% less latency but when I changed name server for one of domain<br />
it took time to reflect that changes on my local PC and as soon as I changed it to Open DNS<br />
I can see name server change</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vivek</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-521945</link>
		<dc:creator>vivek</dc:creator>
		<pubDate>Sat, 05 Dec 2009 08:21:43 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-521945</guid>
		<description>Great move by the giant,rather, as Mansour said &quot;PAcman of 21st century&quot;, but the ISP&#039;s can configure their routers to direct DNS requests to their own servers.
It wont be surprising if Google uses this whole lot of data in their search algorithms, in near future.</description>
		<content:encoded><![CDATA[<p>Great move by the giant,rather, as Mansour said &#8220;PAcman of 21st century&#8221;, but the ISP&#8217;s can configure their routers to direct DNS requests to their own servers.<br />
It wont be surprising if Google uses this whole lot of data in their search algorithms, in near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BF</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-521631</link>
		<dc:creator>BF</dc:creator>
		<pubDate>Fri, 04 Dec 2009 22:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-521631</guid>
		<description>I use chrome as my default browser, and rely on gmail for email. The connection of my gmail/google account to my browsing history is my primary reason for not using Google DNS, despite their claim the connection will never happen.</description>
		<content:encoded><![CDATA[<p>I use chrome as my default browser, and rely on gmail for email. The connection of my gmail/google account to my browsing history is my primary reason for not using Google DNS, despite their claim the connection will never happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SL</title>
		<link>http://domainnamewire.com/2009/12/03/google-public-dns-could-be-data-treasure-trove-for-google/comment-page-1/#comment-521616</link>
		<dc:creator>SL</dc:creator>
		<pubDate>Fri, 04 Dec 2009 21:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9544#comment-521616</guid>
		<description>Holy crap, notOpenGoogleDNS.  How could you possibly have missed the point of this topic so badly?

The issue is not about speed.  It&#039;s about tracking and ads served on non-resolvable queries.  Hence the choice to use other public, unfettered DNS servers instead of your ISP&#039;s tainted offerings.

Like anything else in life, yes, there will be a tradeoff.  In my case the IPs served up by dnsserverlist.org are *slightly* slower.  If there are problems then it takes about 30 seconds to pick another one.  BFD.

Btw, 1334 skillz with that dig query.</description>
		<content:encoded><![CDATA[<p>Holy crap, notOpenGoogleDNS.  How could you possibly have missed the point of this topic so badly?</p>
<p>The issue is not about speed.  It&#8217;s about tracking and ads served on non-resolvable queries.  Hence the choice to use other public, unfettered DNS servers instead of your ISP&#8217;s tainted offerings.</p>
<p>Like anything else in life, yes, there will be a tradeoff.  In my case the IPs served up by dnsserverlist.org are *slightly* slower.  If there are problems then it takes about 30 seconds to pick another one.  BFD.</p>
<p>Btw, 1334 skillz with that dig query.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

