DNSBL ending phase

We’re about to finish the long work of WP-DNSBL v2.0.0 which is a WordPress based plugin that will from this new release support and run with TorneAPIv3. APIv3 has much better documentation of how to use the DNSBL API (here). From this release, the API can also be configured via TorneAUTH v4, which will be located on https://auth.tornevall.net very soon, where API keys can be created automatically. All this together is planned to be a huge facelift (so the forum will hopefully also be updated in the same time and work as an extra support for the portal visitors).

Finishing this plugin has been very welcome by both me and other visitors, that during a long period have had a lot of problems with delisting themselves from the blacklist. For the moment, much of this is handled manually when the standard dnsbl site does not coorporate with us.

Changes

  • One big update for the new interface is that visitors can do CIDR-lookups (to see their entire network from a blacklist perspective).
  • Another update is that it should be more user friendly. Instead of impossible interfaces, there will be a raw, plain POST-form, with captcha support so system admins can run their delisting requests from another computers (where console is not supported)
  • The delisting and blacklist views are handled from a wordpress plugin, which means it might not be necessary to use the regular dnsbl server for delistings. By requesting special permissions, other servers might be able to communicate with the remote API too
  • The API is documented with more details than APIv2 was. This also means that own implementations of the DNSBL is made easier
  • Since we’re using a plugin for this, protecting admins from being banned from their own site is extra important
  • All bugs from DNSBLWP v1.x is hopefully fixed and removed

A complete CHANGELOG of what’s been fixed will be released soon. If you can’t wait for a status update you can take a look here. If you feel that something is missing, feel free to join the project and add requests!

When all this is done, there will be a whole new view for what could come next…

 

We’re working on it…

Currently there’s a few steps left before we can release the new portal system (as shown via the test site at https://www.tornevall.net) and the new portal configurator (Test site located at https://auth.tornevall.com). The old platform for handling DNS Blacklists became deprecated as the development of NetCURL (https://www.netcurl.org) have been highly upgraded to fit other (ecommerce) needs. The behaviour of netcurl is backward compatible, but the DNS blacklist and portal software really needed a facelift anyway.

I’ve been looking for a platform that I can handle easier than the self built, and got stuck into a million of alternatives. However, the forum platform is still there, since there are too many posts and history behind. So those parts can’t be replaced (yet). Besides, if everything goes well, there might be no need of doing so.

So what’s left before a release? Actually, TorneAPI (3.0) is ready to go live and the applications built in the API is also very dynamic. As I proceed more things will be added to it and currently, the big focus is the DNS Blacklist, FraudBL and NETFILTER.

opm.tornevall.org with DNSBL status

For three years ago (june 2013) we decided to remove the substructure opm.tornevall.org, from the DNSBL. Statistics, however, shows that opm are still in use. And in fact traffic seems to increase, from those resolvers. They are therefore reinstated, even if there will be double entries of each blacklisted host.

Our honeypot have also begun to catch e-mail on a new level. Messages containing traces of phishing and fraud will be flagged differently from the regular lookups. This refactoring and migrating to the new system are not finished yet, so bit-flags are not considered yet. However, our new domain for phishing – FraudBL – may be useful here.

And do not forget: As long as the migration is not finished, we will continue remove your blacklisted hosts manually, with as high SLA as possible. In that case, we still use the support address dnsbl@tornevall.org

To be continued…