[rbldnsd] how to make public (DNS)RBL?

[Chris.]

On Fri, 15 May 2009 02:07:00 -0400 (EDT), Jon Lewis wrote...

> On Fri, 15 May 2009, Chris. wrote:
> 
>> Not sure I completely follow you here. As to the "quarter of the IPv4
>> space" Did you imagine that more than 3 quarters of the IPv4 space is
>> in use by legitimate mail services? Where will all the dynamic IP
>> space come from for all the ISP/providers?
> 
> Certainly not...but as IPv4 is about 4 billion addresses, minus parts
> that can't be used, and not all of it is allocated, and not all that's
> allocated is in use, 1 billion may be more like half the currently
> used space.  That's a lot of IPs, but legitimate mail servers probably
> are a tiny fraction of the "in use" IPv4 space.

A good analysis on your part I believe.

> 
> This has gone way off-topic for the rbldnsd list, but I think you do
> have some of us interested in exactly what your list does / what its
> listing criteria are?

I answered that (to some degree) in your last posting.

To my original porting - getting back "on topic";
I was originally attempting to gain some insight from those whom might
already have "hands on" experience running a /public/ RBL. That is;
finding some of the potential "pitfalls" that they experienced. So that
I could compare them with those I've already experienced. There by
heading them off at the pass, so to speak. With that said, I had one
simple question regarding IP usage. I've been testing the RBL using 2
internet routable addresses - 1 for the .COM, and 1 for the .NET domains.
The .NET host/domain handled the RBL spam sources, that is;
for example:
I'm not using the BIND, but am working with/developing a DNS that /speaks/
BIND. So pretty much config/usage is compatible. That said,
the .COM manages a 'BIND like" DNS and fields the queries to the .NET.
As I said before, they both were using internet routable IP's, and the
.NET also spoke rbldnsd on the loopback (127.0.0.1-256) I only needed
6 IP's out of the loopback.
Now, I'd like to simply use one internet routable IP, and let the .COM
use/manage it. So now, as I haven't utilized my anti-spam system in quite
this environment. I was hoping to get some suggestions for what might be
the most resilient use of IP space under this environment. Does this
make any sense? I hope my question is understandable. I'm just a bit
leary "going live" with an environment I haven't already tested. So
was hoping to get some suggestions before doing so. :)

About my earlier "negative" statement;
I guess what anticipated when I first raised the question was something
like: Look, if you REALLY want to pursue this, you MUST understand that
you are setting yourself, and your servers for ALOT of abuse - REALLY.
If knowing this, you still want to do this I would recommend... :)

Thank you very much for taking the time to respond.

--Chris
> 
> ----------------------------------------------------------------------
> Jon Lewis                   |  I route
> Senior Network Engineer     |  therefore you are
> Atlantic Net                |
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
> _______________________________________________
> rbldnsd mailing list
> rbldnsd at corpit.ru
> http://www.corpit.ru/mailman/listinfo/rbldnsd
_________________________________________________________________
    http://fastmail.ca/ - Fast Secure Web Email for Canadians