<?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"
	>
<channel>
	<title>Comments on: NSA.gov Hosed?</title>
	<atom:link href="http://asert.arbornetworks.com/2008/05/nsagov-hosed/feed/" rel="self" type="application/rss+xml" />
	<link>http://asert.arbornetworks.com/2008/05/nsagov-hosed/</link>
	<description>A weblog dedicated to educating the community on security threats that matter</description>
	<pubDate>Mon, 06 Oct 2008 20:11:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Danny McPherson</title>
		<link>http://asert.arbornetworks.com/2008/05/nsagov-hosed/#comment-121906</link>
		<dc:creator>Danny McPherson</dc:creator>
		<pubDate>Thu, 22 May 2008 02:02:50 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=249#comment-121906</guid>
		<description>Most of the stuff (e.g., traceroute probes) to those IPs is filtered at the ingress of the NCSC network just after it leaves the ISP network.  Routing was fine to there, but there was no visibility or response after those hops.  Apparently it wasn't just a DNS process crash issue or the like, as the http server running on one of the boxes was also unreachable.  HTH, -danny</description>
		<content:encoded><![CDATA[<p>Most of the stuff (e.g., traceroute probes) to those IPs is filtered at the ingress of the NCSC network just after it leaves the ISP network.  Routing was fine to there, but there was no visibility or response after those hops.  Apparently it wasn&#8217;t just a DNS process crash issue or the like, as the http server running on one of the boxes was also unreachable.  HTH, -danny</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul D. Parisi</title>
		<link>http://asert.arbornetworks.com/2008/05/nsagov-hosed/#comment-121660</link>
		<dc:creator>Paul D. Parisi</dc:creator>
		<pubDate>Wed, 21 May 2008 17:38:56 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=249#comment-121660</guid>
		<description>Danny,

Did you happen to do any traceroutes to the NS IP's during the outage? If so were they reachable? So was it that the machines were unreachable or was the DNS zone broken?

Paul.</description>
		<content:encoded><![CDATA[<p>Danny,</p>
<p>Did you happen to do any traceroutes to the NS IP&#8217;s during the outage? If so were they reachable? So was it that the machines were unreachable or was the DNS zone broken?</p>
<p>Paul.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Update: DNS trouble knocks NSA off Internet &#124; InfoWorld &#124; News &#124; 2008-05-15 &#124; By Robert McMillan, IDG News Service</title>
		<link>http://asert.arbornetworks.com/2008/05/nsagov-hosed/#comment-118797</link>
		<dc:creator>Update: DNS trouble knocks NSA off Internet &#124; InfoWorld &#124; News &#124; 2008-05-15 &#124; By Robert McMillan, IDG News Service</dc:creator>
		<pubDate>Thu, 15 May 2008 23:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://asert.arbornetworks.com/?p=249#comment-118797</guid>
		<description>[...] Web site was unreachable because of a problem with the NSA's DNS&#160;servers, said Danny McPherson, chief research officer with Arbor Networks. [...]</description>
		<content:encoded><![CDATA[<p>[...] Web site was unreachable because of a problem with the NSA&#8217;s DNS&nbsp;servers, said Danny McPherson, chief research officer with Arbor Networks. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
