You're right, I'm sure this is doable in some fashion.  However there's
a limit to how much I want to fool with a server's setup.  Note that I'm
using a VERY specialized RBL-only DNS daemon here (djbdns's rbldns) and
that it only provides RBL data.  Frankly this becomes less interesting
the more complex it becomes.  Really the use of a DNS based solution in
this case is problematic.  DNS based RBL really only makes sense when
you are going to leverage the caching nature of the DNS network.  That's
not occurring here and I mainly was trying to use the type of system
because packages for such daemons were readily available and it seemed
like support for interfacing with it was already available in SA.  Since
that's not the case maybe I should instead consider some other more
sensible approach for local host blacklisting.


Ken

On Tue, 2002-10-29 at 16:43, Steve Thomas wrote:
> What about making your local nameserver authoritative for the rbl domain
> you're using, and replacing your nameserver with 127.0.0.1 in resolv.conf? I
> use my own nameservers on every connection I use, including my dsl at home.
> That way, I maintain complete control over what I'm looking up, I can clear
> the cache when I want to instead of waiting for an outdated RR to expire,
> etc.
> 
> I'm sure there's a way you could do it - maybe I'll play with it tonight.
> I've been dealing with dns servers for a few years, but don't have much
> experience with the blacklist variety. Which blacklist are you using?
> 
> St-
> 
> 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to