<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: DNS getting lots of attention today</title>
	<atom:link href="http://techdulla.wordpress.com/2008/07/09/dns-getting-lots-of-attention-today/feed/" rel="self" type="application/rss+xml" />
	<link>http://techdulla.wordpress.com/2008/07/09/dns-getting-lots-of-attention-today/</link>
	<description>Ramblings of yet another IT guy</description>
	<lastBuildDate>Thu, 27 Aug 2009 17:46:44 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan</title>
		<link>http://techdulla.wordpress.com/2008/07/09/dns-getting-lots-of-attention-today/#comment-172</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 09 Jul 2008 17:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://techdulla.wordpress.com/?p=89#comment-172</guid>
		<description>Yes and No.  

The vulnerability could potentially have a serious impact on a large scale if it were exploited so I would agree that it is a major issue that needs to be addressed ASAP.  On the other hand, DNS was never an absolutely secure protocol to begin with so to think that this news means you need to storm into your CEO&#039;s office and tell him everything needs to get shut down mid-day so that you can install the patches would be overkill.

Update your name servers as soon as possible to mitigate the largest risk.  For everything else I would treat this vulnerability equal to any other vulnerability that impacts the majority if not all of your systems.  Follow your normal procedure for patch management and get these applied in a timely manner.  If you don&#039;t have a normal procedure....then now is a good time to put one together.  It doesn&#039;t have to be done today, but I wouldn&#039;t put it off too long without a really good reason.</description>
		<content:encoded><![CDATA[<p>Yes and No.  </p>
<p>The vulnerability could potentially have a serious impact on a large scale if it were exploited so I would agree that it is a major issue that needs to be addressed ASAP.  On the other hand, DNS was never an absolutely secure protocol to begin with so to think that this news means you need to storm into your CEO&#8217;s office and tell him everything needs to get shut down mid-day so that you can install the patches would be overkill.</p>
<p>Update your name servers as soon as possible to mitigate the largest risk.  For everything else I would treat this vulnerability equal to any other vulnerability that impacts the majority if not all of your systems.  Follow your normal procedure for patch management and get these applied in a timely manner.  If you don&#8217;t have a normal procedure&#8230;.then now is a good time to put one together.  It doesn&#8217;t have to be done today, but I wouldn&#8217;t put it off too long without a really good reason.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DMB411</title>
		<link>http://techdulla.wordpress.com/2008/07/09/dns-getting-lots-of-attention-today/#comment-171</link>
		<dc:creator>DMB411</dc:creator>
		<pubDate>Wed, 09 Jul 2008 15:24:05 +0000</pubDate>
		<guid isPermaLink="false">http://techdulla.wordpress.com/?p=89#comment-171</guid>
		<description>Glad to see you are writing more regularly again.  Thanks for writing about this and for the links.  So do you think this is as major an issue as everyone is making it out to be?</description>
		<content:encoded><![CDATA[<p>Glad to see you are writing more regularly again.  Thanks for writing about this and for the links.  So do you think this is as major an issue as everyone is making it out to be?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
