<?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: OpenDNS: A Followup</title>
	<atom:link href="http://www.sector930.com/blog/2009/05/13/opendns-a-followup/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sector930.com/blog/2009/05/13/opendns-a-followup/</link>
	<description>EVERYBODY WRITES, NOBODY QUITS.</description>
	<lastBuildDate>Fri, 13 Aug 2010 13:12:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: John</title>
		<link>http://www.sector930.com/blog/2009/05/13/opendns-a-followup/comment-page-1/#comment-1058</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 09 Sep 2009 16:33:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sector930.com/blog/?p=573#comment-1058</guid>
		<description>It is also worth nothing that you can opt out of the statics program now. Doing so will halt all logging of traffic that passes over your account, and adds that much needed layer of privacy.

I am a very private person, and I use OpenDNS on my home networks. When combined with a properly configured Windows security policy (to disable DNS/IP editing), it works very well to keep the kids off 4Chan and the like.

Just some more food for thought. Good articles though.</description>
		<content:encoded><![CDATA[<p>It is also worth nothing that you can opt out of the statics program now. Doing so will halt all logging of traffic that passes over your account, and adds that much needed layer of privacy.</p>
<p>I am a very private person, and I use OpenDNS on my home networks. When combined with a properly configured Windows security policy (to disable DNS/IP editing), it works very well to keep the kids off 4Chan and the like.</p>
<p>Just some more food for thought. Good articles though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Sniderman</title>
		<link>http://www.sector930.com/blog/2009/05/13/opendns-a-followup/comment-page-1/#comment-972</link>
		<dc:creator>Joe Sniderman</dc:creator>
		<pubDate>Tue, 30 Jun 2009 07:24:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.sector930.com/blog/?p=573#comment-972</guid>
		<description>Hi.
The real reason using the root nameservers won&#039;t work is that they are not set up to handle recursive queries.  When you send one of the root servers a domain, it responds by telling you where to look next, ie, who is authoritative for that tld, you then look there, and so on, down the line, till you get the nameserver(s) for the specific domain you are looking to resolve.  Therefore you cannot just send them a domain name and have them resolve it for you.  This is not a security feature per se, it is just how DNS itself works. 

Nothing stopping you from having your own nameserver pull info from the root servers however.  Run BIND or whatever on a spare box, make sure it has info for *all* of the root servers ( otherwise it will fail ) and let it do the work for you. That way you&#039;re not dependent on OpenDNS, your ISP, or Verizon to do your lookups for you.</description>
		<content:encoded><![CDATA[<p>Hi.<br />
The real reason using the root nameservers won&#8217;t work is that they are not set up to handle recursive queries.  When you send one of the root servers a domain, it responds by telling you where to look next, ie, who is authoritative for that tld, you then look there, and so on, down the line, till you get the nameserver(s) for the specific domain you are looking to resolve.  Therefore you cannot just send them a domain name and have them resolve it for you.  This is not a security feature per se, it is just how DNS itself works. </p>
<p>Nothing stopping you from having your own nameserver pull info from the root servers however.  Run BIND or whatever on a spare box, make sure it has info for *all* of the root servers ( otherwise it will fail ) and let it do the work for you. That way you&#8217;re not dependent on OpenDNS, your ISP, or Verizon to do your lookups for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bypassing OpenDNS at Sector 930</title>
		<link>http://www.sector930.com/blog/2009/05/13/opendns-a-followup/comment-page-1/#comment-934</link>
		<dc:creator>Bypassing OpenDNS at Sector 930</dc:creator>
		<pubDate>Thu, 28 May 2009 17:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.sector930.com/blog/?p=573#comment-934</guid>
		<description>[...] refer to a followup post: http://www.sector930.com/blog/2009/05/13/opendns-a-followup/      &#171; Fun Times with Religion Sector930 Is Now Global! [...]</description>
		<content:encoded><![CDATA[<p>[...] refer to a followup post: <a href="http://www.sector930.com/blog/2009/05/13/opendns-a-followup/" rel="nofollow">http://www.sector930.com/blog/2009/05/13/opendns-a-followup/</a>      &laquo; Fun Times with Religion Sector930 Is Now Global! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lenowe</title>
		<link>http://www.sector930.com/blog/2009/05/13/opendns-a-followup/comment-page-1/#comment-914</link>
		<dc:creator>Lenowe</dc:creator>
		<pubDate>Wed, 13 May 2009 17:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.sector930.com/blog/?p=573#comment-914</guid>
		<description>I think they&#039;re quite malicious. Just sayin.</description>
		<content:encoded><![CDATA[<p>I think they&#8217;re quite malicious. Just sayin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
