<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Blocking spam domain referrals with .htaccess</title>
	<link>http://www.hojohnlee.com/hacks/2006/01/12/blocking-spam-domain-referrals-with-htaccess/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 20:59:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Hacks and Gadgets by HJL &#187; Blog Archive &#187; Blizzard of comment and trackback spam</title>
		<link>http://www.hojohnlee.com/hacks/2006/01/12/blocking-spam-domain-referrals-with-htaccess/#comment-259</link>
		<pubDate>Sat, 20 May 2006 18:48:30 +0000</pubDate>
		<guid>http://www.hojohnlee.com/hacks/2006/01/12/blocking-spam-domain-referrals-with-htaccess/#comment-259</guid>
					<description>[...] This round of spam seems better implemented than previous ones. The incoming comments and trackbacks are distributed across the entire site, rather than on one or two posts, and are also coming in from a broad set of IP addresses and user agents, which makes it hard to use .htaccess rules for blocking it. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This round of spam seems better implemented than previous ones. The incoming comments and trackbacks are distributed across the entire site, rather than on one or two posts, and are also coming in from a broad set of IP addresses and user agents, which makes it hard to use .htaccess rules for blocking it. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: veridicus</title>
		<link>http://www.hojohnlee.com/hacks/2006/01/12/blocking-spam-domain-referrals-with-htaccess/#comment-18</link>
		<pubDate>Thu, 02 Mar 2006 20:07:27 +0000</pubDate>
		<guid>http://www.hojohnlee.com/hacks/2006/01/12/blocking-spam-domain-referrals-with-htaccess/#comment-18</guid>
					<description>Be aware blocking by domain name requires reverse DNS lookup to be on.  Otherwise apache only has the IP address to work with.  Based on your experience it appears Dreamhost has it turned on.  That's surprising because it eats CPU cycles and network traffic.  For efficiency most big hosts turn it off.

If a host has it turned off and you're using PHP to run your site you can do reverse DNS lookups through PHP code and handle all cases there.  Of course this also eats up CPU and network traffic, but for small enough sites it may be worth it.</description>
		<content:encoded><![CDATA[<p>Be aware blocking by domain name requires reverse DNS lookup to be on.  Otherwise apache only has the IP address to work with.  Based on your experience it appears Dreamhost has it turned on.  That&#8217;s surprising because it eats CPU cycles and network traffic.  For efficiency most big hosts turn it off.</p>
<p>If a host has it turned off and you&#8217;re using PHP to run your site you can do reverse DNS lookups through PHP code and handle all cases there.  Of course this also eats up CPU and network traffic, but for small enough sites it may be worth it.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
