So with earlier versions of Slack i have been running a DNS server following the directions from this site:
http://www.unixwiz.net/techtips/bind9-chroot.html

So today i upgraded to Slack14 and copied over my config files and try to run it per the site (again been building it like this since 12) but no luck.

by cat'ing messages i get the following:

Oct 8 18:09:57 Slackbox named[4180]: starting BIND 9.9.1-P3
Oct 8 18:09:57 Slackbox named[4180]: built with '--prefix=/usr' '--libdir=/usr/lib' '--sysconfdir=/etc' '--localstatedir=/var' '--with-libtool' '--with-idn=/usr' '--mandir=/usr/man' '--enable-shared' '--disable-static' '--enable-threads' '--with-openssl=/usr' '--build=i486-slackware-linux' 'build_alias=i486-slackware-linux' 'CFLAGS=-O2 -march=i486 -mtune=i686'
Oct 8 18:09:57 Slackbox named[4180]: ----------------------------------------------------
Oct 8 18:09:57 Slackbox named[4180]: BIND 9 is maintained by Internet Systems Consortium,
Oct 8 18:09:57 Slackbox named[4180]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Oct 8 18:09:57 Slackbox named[4180]: corporation. Support and training for BIND 9 are
Oct 8 18:09:57 Slackbox named[4180]: available at https://www.isc.org/support
Oct 8 18:09:57 Slackbox named[4180]: ----------------------------------------------------
Oct 8 18:09:57 Slackbox named[4180]: adjusted limit on open files from 4096 to 1048576
Oct 8 18:09:57 Slackbox named[4180]: found 2 CPUs, using 2 worker threads
Oct 8 18:09:57 Slackbox named[4180]: using 2 UDP listeners per interface
Oct 8 18:09:57 Slackbox named[4180]: using up to 4096 sockets
Oct 8 18:09:57 Slackbox named[4180]: loading configuration from '/etc/named.conf'



but the port is closed, per nmap and tested with telnet and a ps-fCnamed shows no PID. anyone else running into this???? been at a loss all day

quick workaround for now:

mkdir -p /chroot/named/usr/lib/engines
cp -a /usr/lib/engines/libgost.so /chroot/named/usr/lib/engines

1 members found this post helpful.

fluke, you my man, you're the best!!!!! copied the file and all worked!

thank you for the help

Out of curiosity, that file is a part of the "openssl" package. Why not do something like:

Then you can still manage it with the pkgtool and its tools.