This plug-in is used to host a DNS blacklist (a.k.a. "DNSBL" / "RBL").
DNS blacklists are typically used with e-mail servers to filter spam and other unwanted e-mails.
Many e-mail servers can be configured to check if a sender's IP address is listed in a specified DNS blacklist, and based on this decide to reject or flag the incoming e-mail message.
Every time such an e-mail server receives an inbound e-mail message, it does a DNS lookup against one or more DNS blacklists by reversing the segments of the sender's IP address and adding the blacklist domain name.
For example if the sender's IP address is 220.127.116.11 and the blacklist domain name is "dnsbl.example.com", it will do a DNS lookup for "18.104.22.168.dnsbl.example.com".
If the DNS lookup returns an value (typically the dummy IP address 127.0.0.2), this means that the sender's IP address is on the blacklist, and the e-mail server can take appropriate action according to its configuration.
Many blacklists also contain text strings associated with each blacklist entry - typically describing why an IP address is listed and what to do to get de-listed.
E-mail servers can request this text through a DNS TXT-record lookup and log and/or include this in error messages etc.
For more details on this concept and its history, please see this Wikipedia article.
Theoretically a DNS blacklist can be hosted as a normal DNS zone with A-records and TXT-records.
However a DNS blacklist typically contains thousands and often millions of IP addresses, and the standard DNS zone file format and the normal way of storing DNS records in computer memory is just not efficient for this type of data.
This plug-in however is highly optimized for this, and can load a dataset for millions of IP addresses in a fraction of a second using minimal memory, and can query this data extremely efficiently.
You can create your own blacklists with the DNS Blacklist Editor tool.
If you receive a lot of e-mails and do a lot of DNS blacklist lookups against other blacklists (for example as an ISP), it may also be more efficient to periodically download the full blacklists and host them yourself with this plug-in.
In the plug-in instance dialog / Plug-In Settings tab you can specify the blacklist domain name, the compiled data file, select if the data file should automatically be re-loaded when updated, and the TTL value for responses:
The "Compiled data file" is highly optimized proprietary binary file type (".sdnsbl" file extension) which is only understood by this plug-in. This should NOT be confused with standard text based DNSBL/RBL files.
You compile this file type from a DNSBL/RBL text file using the DNS Blacklist Editor tool.
You can compile either from DNS Blacklist Editor's Tools menu, or from the command line (or as part of an automated script) by executing:
DNSBLEDIT.EXE <input-file> <output-file>
Note: You should always keep a copy of your blacklist data in the standard text based format (RBLDNSD format) for editing. Compiling to the plug-in data file format is a one way process. A compiled data file cannot be opened for editing.
When hosting a DNS blacklist with this plug-in, make sure to also configure a local DNS zone for the blacklist domain name or a parent name. Otherwise Simple DNS Plus will attempt to resolve any DNS request which does not have a match in the blacklist (according to recursion settings etc.).
This local zone also provides a place to configure other records for the blacklist domain name - such as SOA, NS, MX records, perhaps an A-records for a web-site about the blacklist, etc.
Where to get this plug-in
Download from: https://simpledns.com/outbox/plugins/v52/dnsbl-plugin.zip
Download the .zip file and then extract the included .dll file to the "PlugIns" directory under the directory where Simple DNS Plus is installed, re-start Simple DNS Plus.
For details on setting up an instance of the plug-in click here.
Note: The zip file includes both the plug-in file (BlackListPlugIn.dll) and the DNS Blacklist Editor tool (DNSBLEdit.exe).
The later is used to create and compile data files for the plug-in and does not need to be in the "plugins" directory.