Changes in version 22.214.171.124 (September 1, 2008)
Using DNS servers for REVDNS and RBL lookups
A major issue was discovered with using the default Windows DNS server ( 0.0.0.0 ) or using a Microsoft DNS server as the lookup server for reverse DNS lookups and DNSBL lookups. Using either of these will cause lookups to be pretty much unreliable. We recommend you use a high speed caching DNS service. The Alligate control panel has been modified to disallow 0.0.0.0 and we have provided wizard buttons to easily configure Alligate to use OpenDNS or UltraDNS. Both are free DNS services and have been tested and work very well.
A bug was fixed in the Alligate control panel that could cause problems when deleting the last entry in a routing table.
There is a new feature in Alligate that allows you to automatically add blocked senders to a temporary blacklist. They can be added for a user definable number of minutes. when subsequent connections they can be refused immediately or tarpitted for a user defined number of seconds. You can also specify a CIDR range to blacklist temporarily so that spammers using multiple addresses from the same netblock can be acted upon.
This is not yet enabled in the Alligate Control Panel. While it is technically working fine, we are still evaluating it's overall effectiveness.
Alligate users that would like to use this can do so by making a few registry changes.
By default, the following entry is 0. This defines the number of minutes to temporarily blacklist a blocked sender. A setting of 0 basically disables this function.
The following setting defines the CIDR range to apply temporary blacklisting to. A value of 29 is the default and recommended.
The following setting sets the additional tarpit times for a temporarily blacklisted sender. If this value is 0 (zero), then the sender will be blocked. If this value us greater than 0, then the blacklisted sender will not be blocked, but tarpit seconds will be added equal to the value specified.