INSTALL.ldap revision adf16bbdb65f8c0845d7c7a8ebc0836ec07bbfee
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannThis is the INSTALL file for 0.4. See
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrewshttp://www.venaas.no/ldap/bind-sdb/ for updates or other information.
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark AndrewsYou need the source for BIND 9.1.0 or newer (for zone transfers you
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannwill need at least 9.1.1rc3 due to a bug). Basically you need to follow
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannthe instructions in doc/misc/sdb, if my instructions doesn't make sense,
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannplease have a look at that as well.
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannCopy ldapdb.c to bin/named and ldapdb.h to bin/named/include in the
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark AndrewsNext alter bin/named/Makefile.in. Add ldapdb.@O@ to DBDRIVER_OBJS and
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrewsldapdb.c to DBDRIVER_SRCS. You also need to add something like
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrews-I/usr/local/include to DBDRIVER_INCLUDES and
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrews-L/usr/local/lib -lldap -llber -lresolv to DBDRIVER_LIBS
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrewsdepending on what LDAP library you have and where you installed it.
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark AndrewsFinally you need to edit bin/named/main.c. Below where it says
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mann"#include "xxdb.h"", add the line "#include <ldapdb.h>". Below where
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannit says "xxdb_init();" add the line "ldapdb_init();", and finally
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannbelow where it says "xxdb_clear();", add "ldapdb_clear();".
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannNow you should hopefully be able to build it.
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark AndrewsBefore you do any configuring of LDAP stuff, please try to configure
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrewsand start bind as usual to see if things work.
00fb0253c9df8a4686115745ae91d501f62c7451Mark AndrewsTo do anything useful, you need to store a zone in some LDAP server.
00fb0253c9df8a4686115745ae91d501f62c7451Mark AndrewsFrom this release on, you must use a schema called dNSZone. Note that
00fb0253c9df8a4686115745ae91d501f62c7451Mark Andrewsit relies on some attribute definitions in the Cosine schema, so that
00fb0253c9df8a4686115745ae91d501f62c7451Mark Andrewsmust be included as well. The Cosine schema probably comes with your
00fb0253c9df8a4686115745ae91d501f62c7451Mark AndrewsLDAP server. You can find dNSZone and further details on how to store
00fb0253c9df8a4686115745ae91d501f62c7451Mark Andrewsthe data in your LDAP server at
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannFor an example, have a look at my venaas.com zone. Try a subtree search
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannfor objectClass=* at
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrewsldap ldap://129.241.20.67/dc=venaas,dc=com,o=DNS,dc=venaas,dc=no
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannTo use it with BIND, I've added the following to named.conf:
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mann type master;
2c089bf6d24936de631a57b4958ba6b8b5e3b23dMark Andrews database "ldap ldap://129.241.20.67/dc=venaas,dc=com,o=DNS,dc=venaas,dc=no 172800";
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannWhen doing lookups BIND will do a sub-tree search below the base in the
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannURL. The number 172800 is the TTL which will be used for all entries that
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott Mannhaven't got the dNSTTL attribute.
be59d1eb72baa92baa74766a0a1ff4283e4e6ba5Scott MannStig Venaas <venaas@uninett.no> 2001-04-12