<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Worlds Colliding Violently &#187; bind</title>
	<atom:link href="http://www.mikepalumbo.com/tag/bind/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikepalumbo.com</link>
	<description>Programming, Drumming, Cooking, Cars, Mozilla, and the Trials &#38; Tribulations of a Geek from New Jersey.</description>
	<lastBuildDate>Wed, 25 Jan 2012 19:55:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Take That, VeriSign.</title>
		<link>http://www.mikepalumbo.com/2003/09/17/take-that-verisign/</link>
		<comments>http://www.mikepalumbo.com/2003/09/17/take-that-verisign/#comments</comments>
		<pubDate>Wed, 17 Sep 2003 17:25:09 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[General geek related entries.]]></category>
		<category><![CDATA[bind]]></category>

		<guid isPermaLink="false">http://www.mikepalumbo.com/?p=22</guid>
		<description><![CDATA[ICS stomps on VeriSign's domain redirect scheme.  [...]]]></description>
			<content:encoded><![CDATA[<p>As I noted in earlier entries, VeriSign put their domain finder service into effect on Monday.  Today, <a href="http://www.isc.org/products/BIND/">ICS &#038; BIND</a> completely invalidated VeriSign&#8217;s efforts.  And I smiled greatly.</p>
<p>Really, it&#8217;s a <a href="http://www.isc.org/products/BIND/delegation-only.html">very clever solution</a> to the problem.  By declaring .net and .com zones as delegation only, they essentially force only NXDOMAIN records to be returned in the case of something other than a NS record coming back (namely, an A record).</p>
<p>Of course, I&#8217;m wondering if VeriSign is going to escalate this.  They very well might, since money is involved, and they technically <strong>could</strong> get around this (and it would be pretty easy for them to do so as well).  Things would only get worse at that point, and then ICANN would potentially have to get involved&#8230;ugh.  Let&#8217;s see what happens from this point onward, but I applaud ICS for making such a wonderfully elegant solution to this problem.</p>
<p>As a final note, <a href="http://www.tinydns.org">djbdns</a> also has released a patch for this.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mikepalumbo.com/2003/09/17/take-that-verisign/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

