[rbldnsd] Question regarding use of rbldnsd with MAPS RBL

[Mark Hennessy]

I have a file like that now that I built with a perl script I wrote.

It's formatted like this (no other lines looking different from these):
10.0.0.0/8     127.1.0.1
10.1.0.0/8     127.1.0.1
192.168.2.0/24  127.1.0.2
192.168.1.1/32 127.1.0.2
192.168.2.12/32        127.1.0.2
192.168.36/24  127.1.0.2

Whenever I try to do an nslookup against an IP that is listed (in this case
192.168.1.1), I get:
*** dnsserver can't find 192.168.1.1: Query refused

The logs record the refusal, so it's not a firewall rule.
1114201474 <my ip> 1.1.168.192.IN-ADDR.ARPA PTR IN: REFUSED/0/44

I'm using the ip4set rules.  What am I missing?

--
 Mark Hennessy

-----Original Message-----
From: rbldnsd-bounces at corpit.ru [mailto:rbldnsd-bounces at corpit.ru] On Behalf
Of furio ercolessi
Sent: Friday, April 22, 2005 4:58 PM
To: Small Daemon for DNSBLs
Subject: Re: [rbldnsd] Question regarding use of rbldnsd with MAPS RBL

On Fri, Apr 22, 2005 at 11:39:40PM +0400, Michael Tokarev wrote:
> Mark Hennessy wrote:
> >Does anyone have an example script for pulling down the zone for MAPS RBL 
> >for
> >use with rbldnsd?
> >I can't seem to find one anywhere and I have only just started trying to 
> >set
> >up rbldnsd.
> 
> I've never saw the zones myself.  

They are weird, because IPs in common between the subzones are handled
with a bitmask in the return code rather than with multiple entries
(like Osirusoft did, and now XBL does).

So if, say, RBL contains 100.100.0.0/16 and RSS contains 100.100.100.100/32,
the RBL+ file would contain something like (in Bind notation)

100.100.0.0/24     127.1.0.1
100.100.1.0/24     127.1.0.1
.....                ...
100.100.99.0/24    127.1.0.1
100.100.100.0/32   127.1.0.1
100.100.100.1/32   127.1.0.1
.....                ...
100.100.100.99/32  127.1.0.1
100.100.100.100/32 127.1.0.5
100.100.100.101/32 127.1.0.1
.....                ...
100.100.100.255/32 127.1.0.1
100.100.101.0/24   127.1.0.1
.....                ...
100.100.255.0/24   127.1.0.1

So, in this example, two records in the original zones become
511 records in the combined zone.
The result is that RBL+ splitting into the original subzones requires 
a considerable reaggregation work to obtain something sane and compact.
To be honest, I always thought that the RBL+ aggregation scheme
is not the smartest of ideas.

furio

_______________________________________________
rbldnsd mailing list
rbldnsd at corpit.ru
http://www.corpit.ru/mailman/listinfo/rbldnsd