Slackware 12.0 shipped with the bind package version:
bind-9.4.1-i486-1.tgz

It was patched a couple of times, and most recently is patched to
version, bind-9.4.2_P2-i486-1_slack12.0.tgz

There is a misc. gotcha, which can crop up if the user is not paying
enough attention. It caught me when I decided to start running a
caching only name server on an existing Slack 12.0 box. I did not notice
that there had been a new version of the file, /etc/named.conf.new, as
part of a previous patch rollout. When I began building the box, I
started by editing /etc/named.conf to customize it to work with my setup.
I did not notice the new version. This gotcha is easily fixed- once the
problem is noticed- simply refer to the correct filename, named.root. See
below.


//
// a caching only nameserver config
//
zone "." IN {
type hint;
file "caching-example/named.root";
};


<
//
// a caching only nameserver config
//
zone "." IN {
type hint;
file "caching-example/named.ca";
};


p.s. Perhaps, this warning will save someone else some grief. The warning
messages when bind fails to start running refer to a "capability module"
not being loaded. That can be true, but may not be the cause for bind
failing to start. In this case named.ca will have been removed.

--
Douglas Mayne