I installed BIND 9.3.2-r4 with the following USE flags: USE="dlz doc idn ipv6 ldap ssl -berkdb -mysql -odbc -postgres (-selinux) -threads" Then a setup a the config. It works fine with normal zone files... I switched one zone to LDAP: zone "unix.sea" IN { type master; database "ldap ldap://127.0.0.1/ou=hosts,dc=unix,dc=sea 86400"; }; When I start the BIND daemon I get the followong error: Nov 19 13:40:47 triggerfish named[4092]: starting BIND 9.3.2-P1 -u named -n 1 Nov 19 13:40:47 triggerfish named[4092]: loading configuration from '/etc/bind/named.conf' Nov 19 13:40:47 triggerfish named[4092]: listening on IPv4 interface eth0, 192.168.1.10#53 Nov 19 13:40:47 triggerfish named[4092]: listening on IPv4 interface lo, 127.0.0.1#53 Nov 19 13:40:47 triggerfish named[4092]: command channel listening on 127.0.0.1#953 Nov 19 13:40:47 triggerfish named[4092]: command channel listening on ::1#953 Nov 19 13:40:47 triggerfish named[4092]: zone 127.in-addr.arpa/IN: loaded serial 2006062502 Nov 19 13:40:47 triggerfish named[4092]: zone 1.168.192.in-addr.arpa/IN: loaded serial 2006062504 Nov 19 13:40:47 triggerfish named[4092]: zone localhost/IN: loaded serial 2006062502 Nov 19 13:40:47 triggerfish named[4092]: unsupported database type 'ldap' Nov 19 13:40:47 triggerfish named[4092]: zone unix.sea/IN: loading zone: creating database: not found Nov 19 13:40:47 triggerfish named[4092]: running Is it possible that the LDAP patch does not work as expected?
your configuration is slightly wrong. please, refer to dlz's documentation page: http://bind-dlz.sourceforge.net/ldap_driver.html