rsync -qa [RSYNC SERVER NAME HERE]::surbl/multi.surbl.org.rbldnsd ..\rbldnsd* The destination location must be "<INSTALL-PATH>\rbldnsd" in order for the next step to work. (The rsync server name will be provided in your data feed instructions.)
@echo off If not exist rsync.locked (goto :rsync) else (goto :exit) :rsync rename rsync.unlocked rsync.locked rsync -qa [RSYNC SERVER NAME HERE]::surbl/multi.surbl.org.rbldnsd ..\rbldnsd rename rsync.locked rsync.unlocked :exit exit
For example, for ClearSwift Mailsweeper:
Hence, there are two ways to point the software to query our SURBL cache: set up the new mirror on the existing recursive DNS server, or set up the new mirror on a local server and also set up the same server to act as a DNS forwarder.
On the existing recursive nameserver that the mail filter uses, create a new forward zone multi.surbl.org to forward all queries to the IP of your SURBL cache. The DNS servers will act as a forwarder and help to forward all SURBL queries to the SURBL cache.
During the installation of wrbldnsd, specify rbldnsd to run on another port e.g. "127.0.0.1/54". Install BIND for Windows. The latest BIND version 9.6.0 cannot run on Windows 2000 Server; the minimum version is WinXP Pro or Windows 2003 Server. Configure BIND for Windows to forward recursive requests (for all other zones) to your provider's DNS servers. Define the following zone in your named.conf file to forward requests to the local SURBL cache.
zone "multi.surbl.org" IN {
type forward;
forward first;
forwarders {
127.0.0.1 port 54;
};
};
(Note that BIND zone forwarding is the
same
technique used with Unix.)
Lastly on the Mailsweeper servers, set the first DNS server entry to the IP of this machine which BIND is listening on. Set the second and any additional IPs to the provider's DNS servers. This creates a failover redundancy. Should the local server go down, the queries go to your provider's DNS instead. Alternatively, set up additional local mirrors and add them as the second IP, etc.