Integration Guide:
Bind 9
4.4 Install BIND Domain Name Server
Besides to have OpenSSL compiled from sources it is also mandatory to compile BIND from it’s source
files. This will enable BIND to use PKCS#11 enabled hardware for cryptographic operations. Since it
is determined during the configuration of BIND where the OpenSSL and PKCS#11 libraries are located,
you have to provide the location of the OpenSSL libraries created in chapter 4.3. Next configure and
install BIND.
4.4.1 Linux
1. Configure BIND on a 32 bit machine
# ./configure CC=”gcc -m32” -enable-threads \
--with-openssl=/opt/openssl-p11 \
--with-pkcs11=/usr/lib/cryptoserver/libcs2_pkcs11.so
If you are on a 64 bit machine configure BIND via
# ./configure CC=”gcc -m64” -enable-threads \
--with-openssl=/opt/openssl-p11 \
--with-pkcs11=/usr/lib/cryptoserver/libcs2_pkcs11.so
2. Set the environment variable
LD_LIBRARY_PATH
to the path of the PKCS#11 library
# export LD_LIBRARY_PATH=/usr/lib/cryptoserver
3. Build and install BIND
# make
# make install
4.4.2 Microsoft Windows
1. To set the path to the PKCS#11 library run the following script:
cd bind-9.7.0\win32utils
perl setpk11provider.pl /windows/system32/cs2_pkcs11.dll
After the installation of BIND it is still possible to specify the path manually.
Page 12
Summary of Contents for Bind 9
Page 1: ...Integration Guide Bind 9 Linux 3 19 Microsoft Windows Server 2008...
Page 17: ...Page 17...
Page 18: ...Integration Guide Bind 9 Page 18...
Page 19: ...Page 19...