[rbldnsd] Netblocks vs. Ranges - different behavior

[Scott Knight]

I've noticed some differing behavior regarding the use of netblocks vs. ranges in RBLDNSD.  Particularly when combined with another single IP that is included in that netblock range. 

For example:
 
If I have the following two entries in my zone file (fake IPs):
 
1.2.3.0/24:127.0.0.3
1.2.3.5:127.0.0.2
 
If I do an nslookup on 5.3.2.1.zonename.com, I get 127.0.0.2 only as the response (this is the desired effect, the single IP is overriding the netblock)
 
But, if I have the following two entries in my zone file:
1.2.3.0-1.2.3.255:127.0.0.3
1.2.3.5:127.0.0.2
 
An nslookup on 5.3.2.1.zonename.com here returns 2 results, 127.0.0.3 and 127.0.0.2 (and order seems to matter... if the single IP was listed first, then 127.0.0.2 would be returned before 127.0.0.3).
 
For cases like the above, it doesn't matter much because I can just use netblocks instead of ranges, but for smaller ranges that don't necessarily map to a netblock, I run into this issue.
 
Is there anyway to force a single IP to overide a range?
 
Thanks for any input on this issue...
 
Scott 

			
---------------------------------
Do you Yahoo!?
 The all-new My Yahoo! – Get yours free!    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.corpit.ru/pipermail/rbldnsd/attachments/20041119/30a01f6f/attachment.html