<DIV>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. <BR><BR>For example:</DIV>
<DIV> </DIV>
<DIV>If I have the following two entries in my zone file (fake IPs):</DIV>
<DIV> </DIV>
<DIV>1.2.3.0/24:127.0.0.3</DIV>
<DIV>1.2.3.5:127.0.0.2</DIV>
<DIV> </DIV>
<DIV>If I do an nslookup on 5.3.2.1.zonename.com, I get 127.0.0.2 <STRONG>only</STRONG> as the response (this is the desired effect, the single IP is overriding the netblock)</DIV>
<DIV> </DIV>
<DIV>But, if I have the following two entries in my zone file:</DIV>
<DIV>1.2.3.0-1.2.3.255:127.0.0.3</DIV>
<DIV>1.2.3.5:127.0.0.2</DIV>
<DIV> </DIV>
<DIV>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).</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>Is there anyway to force a single IP to overide a range?</DIV>
<DIV> </DIV>
<DIV>Thanks for any input on this issue...</DIV>
<DIV> </DIV>
<DIV>Scott </DIV><p>
<hr size=1>Do you Yahoo!?<br>
The <a href="http://my.yahoo.com">all-new My Yahoo!</a> � Get yours free!