On Tue, 10 Jun 2014, Axb wrote:
On 06/10/2014 12:17 AM, Philip Prindeville wrote:
nope... wiht robldnsd you set your BL zone to use the ip4trie
dataset
which as perhttp://www.corpit.ru/mjt/rbldnsd/rbldnsd.8.html
ip4trie Dataset Set of IP4 CIDR ranges with corresponding (A,
TXT) values. This dataset is similar to ip4set, but uses a
different internal representation. It accepts CIDR ranges only
(not a.b.c.d−e.f.g.h), and allows for the specification of A/TXT
values on a per CIDR range basis. (If multiple CIDR ranges match
a query, the value for longest matching prefix is returned.)
Exclusions are supported too.
Okay, and what would 65.181.64.0/18 look like as a BIND RR? I wasn’t
able to infer this from the documentation you pointed at.
no idea... I don't use Bind.
rbldnsd (the "industry standard") is way more efficient and lightweight
designed especially for "dnsbl" usage.
BIND always breaks its reverse maps on class /C octet boundaries so to
represent 65.181.64.0/18 you'd have to utilize 64 class /C zones.
Having run a RBL with BIND and then moved to rbldnsd, I agree completely
with Axb. rbldnsd -is- the way to go. If you need the power and configurability
of BIND, then put it in front of rbldnsd, but use rbldnsd for the actual zone
data.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
