<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Shut them down&#x27; in forum &#x27;&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Shut-them-down-19612276</link>
<description></description>
<language>en</language>
<pubDate>Fri, 10 Feb 2012 15:58:15 EDT</pubDate>
<lastBuildDate>Fri, 10 Feb 2012 15:58:15 EDT</lastBuildDate>

<item>
<title>Re: Shut them down</title>
<link>http://www.dslreports.com/forum/Re-Shut-them-down-19612343</link>
<description><![CDATA[JamesPC posted : <div class="bquote"><small>said by <a href="/profile/200845" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=200845');">manhole</a>:</small><br><br>Can't ICANN shut them down by pulling their IP assignments?  Any DNS server that publicly returns false information should be shut down.<br> </div>ICANN, does not have the man power to regulate all the DNS servers. But you are right that misinformation can cripple the internet. This problem really lies with the major ISPs and backbone operators. Its up to there IT department to have strategy in place when something like that would happen. I work at a ISP in downtown Los Angeles and we get a denial of service attack (DOD) about every one to two weeks. This particular hack sounds tricky, maybe some time of software to check DNS entries multiple times during day?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Shut-them-down-19612343</guid>
<pubDate>Wed, 12 Dec 2007 18:36:35 EDT</pubDate>
</item>

<item>
<title>Shut them down</title>
<link>http://www.dslreports.com/forum/Shut-them-down-19612276</link>
<description><![CDATA[manhole posted : Can't ICANN shut them down by pulling their IP assignments?  Any DNS server that publicly returns false information should be shut down.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Shut-them-down-19612276</guid>
<pubDate>Wed, 12 Dec 2007 18:22:04 EDT</pubDate>
</item>

</channel>
</rss>

