After a longer-than-expected delay, ProBIND 1.0.3 has been released. It addresses the most serious bugs of the 1.0.2 release and includes some cleaned up code.

There has been a big effort underway by security researcher Dan Kaminsky on a very bad problem with many DNS server platforms. Basically, it's a poisoning attack, and a fairly bad one from what is being said. Mr. Kaminsky will publish full details after his presentation at the Black Hat conference. A list of affected systems are in CERT VU #800113.

Note that all versions of ISC BIND are affected, but only version 9 is patched. I guess version 8 is too difficult to fix. If you still have version 8 servers, put in place a plan to upgrade to version 9. Also note that this affects servers with recursion enabled, so if you are running authoritative servers, disable recursion on them - it's a good practice anyway.

Most vendors should have updated their packages with patched ones by now, so if you use the vendor-supplied BIND, you just need to make sure you are updated. If you are running from source, you should be running 9.3.5-P1, 9.4.2-P1, or 9.5.0-P1.

The official root nameserver file has changed as of February 4, 2008. Just recently, l.root-servers.net has moved off the old IP it was using (as of May 1) and to a new one.

It has come to my attention that ProBIND ships with an outdated version (the last version from 2004). Please make sure to replace any copies of root.hint in your ProBIND templates file with the latest edition from InterNIC.

The updated file will be present in the next release of ProBIND.

After all the trouble with SourceForge this weekend (their shell access was down, preventing me from being able to edit the website) and the other restrictions imposed, I've moved the site to space generously donated by PhD Computing, our sponsor.

To help with this, we now have our own project domain: probind.org! Please update any bookmarks or feeds you have set up.

It seems SourceForge doesn't allow web applications to send e-mail directly. This is currently breaking account activation messages for the forum. If you need your account activated, please contact me directly.

Sorry for the inconvenience, I'm currently looking at relaying mail to an outside server or possibly just moving hosting for the site to a less restrictive host.

As a holiday present to all those out there, a new version of ProBIND has been released.

It has been a busy road for me, juggling a bunch of other projects and this software alongside my day job, but I'm happy with the changes I made for this release. At the very least, ProBIND should be a bit cleaner on the errors and have a few more niceties.

I'll be posting more on the direction of this project as I get time to formulate a roadmap. In the meantime, enjoy.

Update: The file release system seems to be working properly now. Accordingly, I have posted the package on the project's download area. You are still welcome to checkout the tag in the repository.

NOTE: It seems the SourceForge release system is broken at the moment, so I can't put out a package. Those with subversion clients can check out the 1.0.2 tag. Getting the release is as easy as "svn export https://probind.svn.sourceforge.net/svnroot/probind/tags/1.0.2 probind-1.0.2". This post will be updated once a package can be released.

The repository for ProBIND is being migrated to Subversion, which is much nicer to work with. All the history is being kept.

This is the first step to cleaning things up for a new bugfix release. Those who are brave can checkout the HEAD revision on the trunk to see how things are going.

After a very long time without updates, work on the ProBIND project has been resumed.

The demo of ProBIND has been taken down until it can be put back in working condition again.