adding a host to the dnsbl?

[scohen <sc...@scohen.mysticjj.com>]

I know the default way of configuring spamassassin to use a dnsbl is like
this:

header RCVD_IN_DSBL             eval:check_rbl_txt('dsbl',
'list.dsbl.org.')
describe RCVD_IN_DSBL           Received via a relay in list.dsbl.org
tflags RCVD_IN_DSBL             net

Now, I set up my own dnsbl and I was wondering if was possible to
supply the host to check with in addition to just the zone, so I don't have
to add a forward entry in dns or add a nameserver entry in resolv.conf

Basically, I want to have spamassassin do what I can do manually with dig:

dig @192.168.13.13 2.0.53.198.my-dnsbl.steve.net

Assumming I had a zone my-dnsbl.steve.net on the ip 192.168.13.13, this
would return a 127.0.0.2 response (assuming that 198.53.0.2 was in the
zone file).

Anyway is something like this possible with spamassassin?

thanks for your time,

Steve Cohen

Re: adding a host to the dnsbl?

[Jeff Chan <je...@surbl.org>]

On Friday, June 25, 2004, 7:27:31 AM, scohen scohen wrote:
> Now, I set up my own dnsbl and I was wondering if was possible to
> supply the host to check with in addition to just the zone, so I don't have
> to add a forward entry in dns or add a nameserver entry in resolv.conf

I believe the cleanest solution *is* to serve up the zone locally
with a forward or zone file entry in named.conf.  That let's all
the leveraged mechanisms apply in the way they are meant to.

Jeff C.
-- 
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/

Re: adding a host to the dnsbl?

[Matt Kettler <mk...@evi-inc.com>]

At 11:21 AM 6/25/2004, scohen wrote:
>I was just looking up NET::DNS on the web and I noticed the the
>NET::DNS::RESOLVER can be used to do something like this:
>
>  @nameservers = $res->nameservers;
>  $res->nameservers('192.168.1.1', '192.168.2.2', '192.168.3.3');
>
>
>Gets or sets the nameservers to be queried.
>
>
>Is there anyway to just set the nameserver to be queried?

you could hack the code in DNS.pm easily enough.. however, SA will use it 
for ALL of it's DNS queries.. MX records, dnsbls, PTR lookups, everything.

Re: adding a host to the dnsbl?

[scohen <sc...@scohen.mysticjj.com>]

On Fri, 25 Jun 2004, Matt Kettler wrote:

> At 10:27 AM 6/25/2004, scohen wrote:
> >I know the default way of configuring spamassassin to use a dnsbl is like
> >this:
> >
> >header RCVD_IN_DSBL             eval:check_rbl_txt('dsbl',
> >'list.dsbl.org.')
> >describe RCVD_IN_DSBL           Received via a relay in list.dsbl.org
> >tflags RCVD_IN_DSBL             net
> >
> >Now, I set up my own dnsbl and I was wondering if was possible to
> >supply the host to check with in addition to just the zone, so I don't have
> >to add a forward entry in dns or add a nameserver entry in resolv.conf
>
> Right now, no.. SA just uses Net::DNS in a fairly straightforward manner
> which just uses the local resolver.
>
> Net::DNS can be set with separate parameters when created via new, however
> this would require SA to instantiate a separate Net::DNS object just for
> that query. It could get a bit ugly in the code trying to keep track of
> multiple resolver objects each with separate settings.
>
I was just looking up NET::DNS on the web and I noticed the the
NET::DNS::RESOLVER can be used to do something like this:

 @nameservers = $res->nameservers;
 $res->nameservers('192.168.1.1', '192.168.2.2', '192.168.3.3');


Gets or sets the nameservers to be queried.


Is there anyway to just set the nameserver to be queried?

Thanks,

Steve Cohen

Re: adding a host to the dnsbl?

[Matt Kettler <mk...@evi-inc.com>]

At 10:27 AM 6/25/2004, scohen wrote:
>I know the default way of configuring spamassassin to use a dnsbl is like
>this:
>
>header RCVD_IN_DSBL             eval:check_rbl_txt('dsbl',
>'list.dsbl.org.')
>describe RCVD_IN_DSBL           Received via a relay in list.dsbl.org
>tflags RCVD_IN_DSBL             net
>
>Now, I set up my own dnsbl and I was wondering if was possible to
>supply the host to check with in addition to just the zone, so I don't have
>to add a forward entry in dns or add a nameserver entry in resolv.conf

Right now, no.. SA just uses Net::DNS in a fairly straightforward manner 
which just uses the local resolver.

Net::DNS can be set with separate parameters when created via new, however 
this would require SA to instantiate a separate Net::DNS object just for 
that query. It could get a bit ugly in the code trying to keep track of 
multiple resolver objects each with separate settings.