1. We'd like to welcome and thank our two new public name
server administrators and hosts:
Dave Burke and esat.net
Bjorn Jensen and info-connect.dk
Without the help of all of our public nameservers, SURBLs
would not be possible. Thanks Dave, Bjorn and all the
administrators and networks of our nameservers!
2. We've added some documents about using rbldnsd, rsync, dnscache
and BIND to locally cache SURBL (and any other RBL) zone files.
Bob Cottrell describes setting up rbldnsd and rsync on top
of an existing BIND server:
http://www.surbl.org/rbldnsd-howto.html
Rick Macdougall writes up how he set up rbldnsd to run on
the same name server as dnscache from djbdns:
http://www.surbl.org/dnscache-rbldnsd.html
I've written up how to use rsync with BIND to cache RBL
zone files, though rbldnsd is a better solution for many
reasons.
http://www.surbl.org/bind-rsync.html
In addition, NJABL has some helpful tips on setting up
rbldnsd and rsync to serve RBL zone files locally:
http://njabl.org/rsync.html
Kind thanks to Bob Cottrell and Rick Macdougall for preparing
and sharing their notes for everyone's benefit! Please let me
know if you have any comments on these. Any errors are probably
due to my transcriptions.
*****************************************************************
Anyone running a high-volume mail system (i.e., more than 250,000
inbound messages per day) is strongly encouraged to set up local
caching of their RBL zone files including SURBLs. The benefits
are improved mail performance, reduced network traffic, and
offloading of the public nameservers. rbldnsd and rsync is the
preferred way to do it, but BIND will also work (slower ;-).
Also if you are using a version of SpamCopURI prior to the
current 0.14, please upgrade it. Some earlier versions do not
support DNS caching, which can result in excessive DNS traffic.
http://sourceforge.net/projects/spamcopuri/
*****************************************************************
3. We have lowered the refresh times on ws.surbl.org and
be.surbl.org zone files to 20 minutes. This change should not
affect most SURBL users. Refresh times of 10 minutes remain
unchanged on sc.surbl.org. Retry times are programatically half
of the refresh times (i.e. 10 and 5 minutes respectively).
Jeff C.
--
Jeff Chan
mailto:[EMAIL PROTECTED]
http://www.surbl.org/
