[rbldnsd] Option -d (Bind dump) and wildcards: a small problem

[Amos Jeffries]

----- Original Message ----- 
From: "Michael Tokarev" <mjt at tls.msk.ru>
To: <rbldnsd at corpit.ru>
Sent: Tuesday, November 02, 2004 1:58 PM
Subject: Re: [rbldnsd] Option -d (Bind dump) and wildcards: a small problem


> Michael Tokarev wrote Sun, 10 Oct 2004 17:29:14 +0400:
>> furio ercolessi wrote:
>>
>>  > Small problem with -d dumps.
>>  >
>>  > Let us consider the following (real) case, from SBL.
>>  > SBL contains the following records related with 222.65.0.0/16:
>>  >
>>  > 222.65.0.0/16 http://www.spamhaus.org/SBL/sbl.lasso?query=SBL19307
>>  > 222.65.20.170/32 http://www.spamhaus.org/SBL/sbl.lasso?query=SBL19565
>>  >
>> []
>>
>>  > 170.20.65.222   A       127.0.0.2
>>  > *.65.222        A       127.0.0.2
>>
>> Oh well.  This isn't a *small* prob, it's a large problem
>> (in the context of -d option anyway).  I'll think about this
>> more - the whole stuff is getting to be quite ugly... :(
>
> Well, this is really getting very ugly.  I tried to sort this prob
> out several times already, but can't figure out how.
>

Okay,
   I have been working on this a bit more.

I can see what you mean by ugly.
It should now fill in the 'holes' so every IP that should be listed has at least 
one relevant RR and exclusions are dealt with cleanly.

The only potential problem I can see is if there is a /16 exclusion and a few 
/32 listed inside it.
The /32 will appear as listed, the /16 itself and all implicit /24 below get 
ignored nicely.

Code for the replacement ds_ip4set_dump function is at
http://eyezone.mine.nu/source/rbldnsd/rbldnsd_ip4set_dump.c
for checkup testing and approval.
I have debugged it as far as logic and compiling against 0.993.1 (29 Jul 2004).

AYJ