[rbldnsd] Problems with Exclusions.

[Dallas Engelken]

Greetings...

Is it possible to have a seperate exclusions file in a combined zone?   
The man says...

"Note that when aggre-gating several data files into one dataset, an 
exclusion entry in one file becomes exclusion entry in the whole  
dataset  (which  may  be  a  problem  when  aggregating
       dialups, where exclusions are common, with open relays/proxies, 
where exclusions are rare if at all used)."

So, it sounds like I should be able to do this...

   zone.local:combined:large.rbldnsd \
   zone.local:combined:excludes.rbldnsd \

With the goal here of quick false remediation.  Assuming large.rbldnsd 
is very large (~10m records) and takes 30+ seconds to reload, and there 
is a record in there such as

DOMAIN.TLD :2:blacklisted

I'd like to be able to stick in my excludes.rbldnsd

!DOMAIN.TLD

and rbldns would only reload that file, which would be very quick.   
However, this doesnt seem to work.   Nor does it work when I load the 
zone in this fashion.

   zone.local:combined:large.rbldnsd,excludes.rbldnsd \

If I put the !DOMAIN.TLD at the bottom of large.rbldnsd and wait for it 
to reload, i get NXDOMAIN results as expected.

The only way I can get it to work where my entries are in one file and 
exceptions are in another with with a non-"combined" zone type, like so

   zone.local:dnset:large.rbldnsd,excludes.rbldnsd \

Which doesnt help either because a change to excludes.rbldnsd causes a 
reload of both files in that set.

Splitting them out into seperate lines makes the exclusions fail as well.

  zone.local:dnset:large.rbldnsd \
  zone.local:dnset:excludes.rbldnsd \

Am I trying to do the impossible?

-- 
Dallas Engelken
dallase at uribl.com
http://uribl.com