Now stop using dsbl.org blacklisting: it’s offline

It seems a lot of Blacklist filters still use the old DSBL DNS Blacklist, but it's been dead for few years already. Since March 2009, to be exact. However, something changed in the last 24 hours that actually made them go offline.

The result is that any system still using that blacklist sends out bounce messages such as this.

The following recipient(s) cannot be reached: xxx
Service unavailable; Client host [x.x.x.x] blocked using list.dsbl.org

If you still have legacy systems running that use the list.dsbl.org blacklist, you may want to remove any references to the DSBL in your configs and stop using that blacklist.

Looking for help?

Tired of fixing all these tech-problems yourself? We've got an excellent team at Nucleus, a top-class Belgian hosting provider, that can help you. Discover our Managed Hosting, where skilled engineers manage your servers and keep them up-to-date, so you can focus on your core business. We use a variety of Configuration Management Systems such as Puppet to make sure every config is reviewed, unit-tested and guaranteed to be working.

Want to get in touch? Find me as @mattiasgeniar on Twitter or via the contact-page on my blog.

Tagged with:
Posted in Devops, linux

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>