Hi Teodor, I wrote Sam about this topic time ago. Here is his reply:
==============Actually, a number of RBLs use CNAMEs to aggregate records. A lot of ISPs use them for their rDNS records too. Removing the CNAME check would cause some problems.
I'm much more interested, however, in figuring out _why_ the CNAME check is causing such a delay. If there are no CNAME records, performing the query shouldn't cause any delay at all. There must be something else going on.
-- Sam Clippinger ==============If your rbl lists do not require CNAME resolution, you can happily live with the following patch
which removes the CNAME query. Mirko At 19:08 21/05/2009 +0300, you wrote:
Hi, We are currently considering spamdyke for use in our network. One thing that caused most trouble so far is the way spamdyke does rbl queries and the way these queries interact with dnscache[1] and rbldns[2]. The issue we are having is caused by the way rbldns reacts to different types of DNS queries. According to it's documentation: "rbldns rejects inverse queries, non-Internet-class queries, truncated packets, packets that contain anything other than a single query, query types other than A, TXT, or *, and queries for domains outside $BASE."
spamdyke-rbl-no-cname.patch
Description: Binary data
_______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
