<?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: Is Your Domain Parking Service Vulnerable to DNS Cache Poisoning?</title>
	<atom:link href="http://domainnamewire.com/2008/08/08/is-your-domain-parking-service-vulnerable-to-dns-cache-poisoning/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2008/08/08/is-your-domain-parking-service-vulnerable-to-dns-cache-poisoning/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Sat, 21 Nov 2009 13:25:12 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Goldstone</title>
		<link>http://domainnamewire.com/2008/08/08/is-your-domain-parking-service-vulnerable-to-dns-cache-poisoning/comment-page-1/#comment-206719</link>
		<dc:creator>Paul Goldstone</dc:creator>
		<pubDate>Sun, 10 Aug 2008 07:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=1926#comment-206719</guid>
		<description>Andrew, thanks for bringing this to the attention of your readers.  Most name server providers have received multiple notifications on this issue, and I can confirm that Domainit.com is not susceptible to the vulnerability.</description>
		<content:encoded><![CDATA[<p>Andrew, thanks for bringing this to the attention of your readers.  Most name server providers have received multiple notifications on this issue, and I can confirm that Domainit.com is not susceptible to the vulnerability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Frazier</title>
		<link>http://domainnamewire.com/2008/08/08/is-your-domain-parking-service-vulnerable-to-dns-cache-poisoning/comment-page-1/#comment-205891</link>
		<dc:creator>Malcolm Frazier</dc:creator>
		<pubDate>Fri, 08 Aug 2008 23:38:57 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=1926#comment-205891</guid>
		<description>Good Afternoon - As of eleven o’clock this morning TrafficZ’s name servers are no-longer allowing recursive lookups. Although we did have recursion enabled; our DNS software (BIND) was patched for this type of vulnerability making it near impossible to successfully execute this type of attack.

In the future if it is necessary for TrafficZ to run BIND as a caching resolver we will implement dnssec as a definitive solution for this issue.

Thank you.</description>
		<content:encoded><![CDATA[<p>Good Afternoon &#8211; As of eleven o’clock this morning TrafficZ’s name servers are no-longer allowing recursive lookups. Although we did have recursion enabled; our DNS software (BIND) was patched for this type of vulnerability making it near impossible to successfully execute this type of attack.</p>
<p>In the future if it is necessary for TrafficZ to run BIND as a caching resolver we will implement dnssec as a definitive solution for this issue.</p>
<p>Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Rowe</title>
		<link>http://domainnamewire.com/2008/08/08/is-your-domain-parking-service-vulnerable-to-dns-cache-poisoning/comment-page-1/#comment-205643</link>
		<dc:creator>Craig Rowe</dc:creator>
		<pubDate>Fri, 08 Aug 2008 15:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=1926#comment-205643</guid>
		<description>Andrew - We&#039;re fixed on our end at WhyPark and have recursive lookups turned off.  We use a managed service for our DNS and they fixed it immediately after I alerted them to your post.  We appreciate the heads up...although an email to me directly would have done the trick as well :)</description>
		<content:encoded><![CDATA[<p>Andrew &#8211; We&#8217;re fixed on our end at WhyPark and have recursive lookups turned off.  We use a managed service for our DNS and they fixed it immediately after I alerted them to your post.  We appreciate the heads up&#8230;although an email to me directly would have done the trick as well <img src='http://domainnamewire.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
