Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of
 prvs=01593d4155=johnl@iecc.com designates 64.57.183.53 as permitted sender)
Date: 4 Jul 2011 19:26:13 -0000
Message-ID: <20110704192613.56994.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: users@spamassassin.apache.org
Cc: dfs@roaringpenguin.com
Subject: Re: TTL and DNSBLs (was Re: SpamTips.org: Why run your own DNS
 server?)
In-Reply-To: <20110704092419.36e1936d@hydrogen.roaringpenguin.com>
Organization: 
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit

>My experiments on real mail servers show that DNS caching is quite
>ineffective for DNSBLs (at least for typical ones like Spamhaus that
>use a short TTL on the order of 15-30 minutes.)

That's consistent with what I've seen, although you probably won't be
surprised to hear that I have higher hopes for my range published
DNSxLs than David does, partly because I expect them to be used for
whitelist which tend to cache better for technical reasons.

But if you're looking for a DNS cache, I highly recommend unbound.
I used to use dnscache but got tired of its limitations (due entirely
to it being unchanged since 1998.)  My copy of unbound runs about
27M real RAM, 44M virtual, which is pretty modest on my 12G server.

R's,
John