<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Block the bad guys with OpenDNS!</title>
	<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/</link>
	<description>Making the Internet safer and faster</description>
	<pubDate>Wed, 19 Nov 2008 11:48:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: theo</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-50712</link>
		<author>theo</author>
		<pubDate>Fri, 22 Jun 2007 11:09:53 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-50712</guid>
		<description>Perhaps OpenDNS should consider a menu of blockable sites.  For example, the military regularly configures its firewalls to block outbound traffic to domains in hostile contries, under the assumption that any traffic bound to them is generated  by malware or trojans - or spies. One possible drawback - such malware may rely on IP addresses, and not require DNS lookup.

Great service, guys...keep it up.</description>
		<content:encoded><![CDATA[<p>Perhaps OpenDNS should consider a menu of blockable sites.  For example, the military regularly configures its firewalls to block outbound traffic to domains in hostile contries, under the assumption that any traffic bound to them is generated  by malware or trojans - or spies. One possible drawback - such malware may rely on IP addresses, and not require DNS lookup.</p>
<p>Great service, guys&#8230;keep it up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Roberts</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-45428</link>
		<author>John Roberts</author>
		<pubDate>Thu, 07 Jun 2007 20:04:04 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-45428</guid>
		<description>@Christoph, reasonable point. It's not intentional, but it's something we'll take a look at.</description>
		<content:encoded><![CDATA[<p>@Christoph, reasonable point. It&#8217;s not intentional, but it&#8217;s something we&#8217;ll take a look at.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christoph</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-44746</link>
		<author>Christoph</author>
		<pubDate>Wed, 06 Jun 2007 20:24:36 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-44746</guid>
		<description>So I blocked a couple advertising servers (doubleclick.net, atdmt.com, and advertising.com are the top offenders).

But something I noticed is that they still show up in the Top Domains Resolved list. Is this intentional? Perhaps a new list is needed called something like Top Domains Blocked. Otherwise the blocked domains just spam the normal Top Domains Resolved list.

(For me, ad.doubleclick.net, view.atdmt.com, and servedby.advertising.com still show up my Top Domains Resolved list)</description>
		<content:encoded><![CDATA[<p>So I blocked a couple advertising servers (doubleclick.net, atdmt.com, and advertising.com are the top offenders).</p>
<p>But something I noticed is that they still show up in the Top Domains Resolved list. Is this intentional? Perhaps a new list is needed called something like Top Domains Blocked. Otherwise the blocked domains just spam the normal Top Domains Resolved list.</p>
<p>(For me, ad.doubleclick.net, view.atdmt.com, and servedby.advertising.com still show up my Top Domains Resolved list)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Thein</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-43715</link>
		<author>Tim Thein</author>
		<pubDate>Tue, 05 Jun 2007 08:00:19 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-43715</guid>
		<description>It's a nice feature but using it created a few unexpected results.  Internet Explorer complains about security certificate errors when accessing a web page using secure http and the web page contains references to blocked domains.  For example, when I sign into BankOfAmerica.com to view my account, the web page has a few references to doubleclick.net which I blocked because that domain is a big source of web advertisements.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a nice feature but using it created a few unexpected results.  Internet Explorer complains about security certificate errors when accessing a web page using secure http and the web page contains references to blocked domains.  For example, when I sign into BankOfAmerica.com to view my account, the web page has a few references to doubleclick.net which I blocked because that domain is a big source of web advertisements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gnarlodious</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-39919</link>
		<author>Gnarlodious</author>
		<pubDate>Mon, 28 May 2007 10:25:05 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-39919</guid>
		<description>Great! You rock! Hope this feature expands to take over the internet!</description>
		<content:encoded><![CDATA[<p>Great! You rock! Hope this feature expands to take over the internet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claude Gelinas</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-39427</link>
		<author>Claude Gelinas</author>
		<pubDate>Sat, 26 May 2007 05:22:19 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-39427</guid>
		<description>If many users block a specific web site, will you take the hint and block it for everyone else, as a "preventive measure"?

Are everyone's entries truly private?</description>
		<content:encoded><![CDATA[<p>If many users block a specific web site, will you take the hint and block it for everyone else, as a &#8220;preventive measure&#8221;?</p>
<p>Are everyone&#8217;s entries truly private?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-38695</link>
		<author>Jack</author>
		<pubDate>Wed, 23 May 2007 14:20:20 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-38695</guid>
		<description>Great work guys, another fantasticly helpful feature!!</description>
		<content:encoded><![CDATA[<p>Great work guys, another fantasticly helpful feature!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Block the bad guys with OpenDNS! &#171; Bloggitation</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-37308</link>
		<author>Block the bad guys with OpenDNS! &#171; Bloggitation</author>
		<pubDate>Thu, 17 May 2007 15:42:21 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-37308</guid>
		<description>[...] read more &#124; digg story [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] read more | digg story [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ansi</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-37203</link>
		<author>Ansi</author>
		<pubDate>Wed, 16 May 2007 23:59:44 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-37203</guid>
		<description>howbt providing and option for admins to see a blocked website after typing in a password?

example. parents want to use myspace.com but not for their kids?</description>
		<content:encoded><![CDATA[<p>howbt providing and option for admins to see a blocked website after typing in a password?</p>
<p>example. parents want to use myspace.com but not for their kids?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-37060</link>
		<author>Andy</author>
		<pubDate>Tue, 15 May 2007 23:08:21 +0000</pubDate>
		<guid>http://blog.opendns.com/2007/05/13/opendns-domain-blocking/#comment-37060</guid>
		<description>how well does this protect against PROXYs?</description>
		<content:encoded><![CDATA[<p>how well does this protect against PROXYs?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
