<?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 Code Blog: A proposal to extend the DNS protocol</title>
	<atom:link href="http://danielmiessler.com/blog/google-code-blog-a-proposal-to-extend-the-dns-protocol/feed" rel="self" type="application/rss+xml" />
	<link>http://danielmiessler.com/blog/google-code-blog-a-proposal-to-extend-the-dns-protocol</link>
	<description>grep understanding</description>
	<lastBuildDate>Sun, 29 Jan 2012 20:44:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: aid</title>
		<link>http://danielmiessler.com/blog/google-code-blog-a-proposal-to-extend-the-dns-protocol/comment-page-1#comment-244687</link>
		<dc:creator>aid</dc:creator>
		<pubDate>Sat, 06 Feb 2010 14:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://danielmiessler.com/blog/google-code-blog-a-proposal-to-extend-the-dns-protocol#comment-244687</guid>
		<description>&lt;p&gt;Nope, sounds like a disaster for DNS caching.&lt;br&gt;&lt;br&gt;Nor is it necessary to solve the stated problem. Google have a world wide network - they can return a single A record to all users and then have their multiple server farms distributed around the world replying for that same address. This will properly terminate users based upon actual routing rather than where their IP addresses are registered.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nope, sounds like a disaster for DNS caching.<br /><br />Nor is it necessary to solve the stated problem. Google have a world wide network &#8211; they can return a single A record to all users and then have their multiple server farms distributed around the world replying for that same address. This will properly terminate users based upon actual routing rather than where their IP addresses are registered.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: aid</title>
		<link>http://danielmiessler.com/blog/google-code-blog-a-proposal-to-extend-the-dns-protocol/comment-page-1#comment-243893</link>
		<dc:creator>aid</dc:creator>
		<pubDate>Sat, 06 Feb 2010 09:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://danielmiessler.com/blog/google-code-blog-a-proposal-to-extend-the-dns-protocol#comment-243893</guid>
		<description>&lt;p&gt;Nope, sounds like a disaster for DNS caching.&lt;br&gt;&lt;br&gt;Nor is it necessary to solve the stated problem. Google have a world wide network - they can return a single A record to all users and then have their multiple server farms distributed around the world replying for that same address. This will properly terminate users based upon actual routing rather than where their IP addresses are registered.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nope, sounds like a disaster for DNS caching.<br /><br />Nor is it necessary to solve the stated problem. Google have a world wide network &#8211; they can return a single A record to all users and then have their multiple server farms distributed around the world replying for that same address. This will properly terminate users based upon actual routing rather than where their IP addresses are registered.</p>]]></content:encoded>
	</item>
</channel>
</rss>

