1administration tools readme 2 3this assumes ldapdns was setup into /service/ldapdns using ldapdns-conf 4first note: 5these tools ONLY work with the vanilla ldapdns system. they're not 6suited for Active Directory or BIND. there are existing tools for that. 7 8i also assume that you've installed perl, and at least Net::LDAP. 9 10configuration: 11 121. create a directory off of home called ~/.ldapdns/ 13 * optional: more than one user can "share" a config by creating 14 /.ldapdns/ or (admintooldir)/.config/ but be warned; these 15 users will have access to your LDAP password. 16 17 * optional: this directory is also read from $ROOT; 18 you can use that too 19 20 this directory is called $ROOT for the remainder of this document 21 222. create two directories: 23 $ROOT/env 24 $ROOT/root 25 copy the files LDAP_BINDDN LDAP_HOST and LDAP_SUFFIX from 26 /service/ldapdns/env to $ROOT/env 27 28 copy the file "password" from /service/ldapdns/root into $ROOT/root 29 30 * optiona: make symlinks instead of directories; 31 ln -s /service/ldapdns/env $ROOT/env 32 ln -s /service/ldapdns/root $ROOT/root 33 343. if you don't use TLS/SSL (e.g. LDAPS) then comment out that code 35 at the top of config.pl and: 36 echo 1 > $ROOT/env/TRUSTED_NETWORK 37 384. if you're going to be using transfer_zone to transfer zones from 39 another nameserver into your directory, note that transfer_zone has 40 TWO MODES of operation: 41 1. a normal zone-transfer tool 42 2. a zone-migration tool 43 to invoke "type 2" set two envrionment variables prior to use: 44 IP the local IP of the nameserver 45 LOCAL_NS nameservers (names) handling PTR entries... 46 you may need to hack this a bit yourself... contact me if you have 47 any questions... 48 495. another possibility (thanks to <jordan@mjh.teddy-net.com>) is to use 50 secondary_zone; which basically eats BIND zone files and populates 51 the directory. this can be very useful for "trying out" data. some 52 warnings (from me): 53 1. make sure that if you're going to use $RELATIVE_NAMES 54 that you set it in the environment whenever you run 55 secondary_zone 56 57 (more to come) 58 59and that's it! the admin scripts should now work as you'd expect. 60Rather: as I would expect. 61 62just remember that set_sub_alias/mx ACTUALLY modifies the "source" 63instead of the "destination" (think of these as the direction of 64aliasing) 65