RBL cache {Scanned by HJMS}

[Furnish, Trever G]

If you wanted to do that, all you'd need to do is set up a caching-only dns
server on your local system.  If your system is redhat, I think they include
a package with the bind config meant specificly for that purpose.  I would
think most people already have another local server doing dns lookups for
them anyway, which is in effect a cache.  For example, my mailscanner uses
another local server as its dns server - that server is on the same ethernet
segment so there's very little difference compared to running my own cache
on the mailscanner.  The DNS server is caching all the lookups - because
that's just what DNS servers do.

If you're suggesting that you would like a long TTL on the records than the
TTL set by the RBL maintainers, that seems ill-informed to me - I would
think the individual RBL maintainer would have a better idea of how long his
records should be considered fresh than I would.

> -----Original Message-----
> From: Ugo Bellavance [mailto:ugob at CAMO-ROUTE.COM]
> Sent: Friday, September 12, 2003 3:34 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: RBL cache {Scanned by HJMS}
>
>
> Hi,
>
>         To my understanding, the RBLs are contacted at every
> batch.  Wouldn't it be easier on the resources to have a
> local cache of blacklisted servers, that would expire, say,
> after 4 hours, a system like caching DNS that may save some
> time and resources?
>