ldap2dns - LDAP based DNS management system
ldap2dns[d] [-D binddn] [-b searchbase] [-o data|db] [-h host] [-p
port] [-w password] [-L[filename]] [-u numsecs] [-v[v]] [-V]
This manual page documents briefly the ldap2dns commands. This manual
page was written for the Debian GNU/Linux distribution because the
original program does not have a manual page yet.
ldap2dns is an efficient, administration friendly way to maintain DNS
information and distribute DNS records to multiple primary DNS servers
running djbdns or BIND
A summary of commanline options is included below.
Use the distinguished name binddn to bind to the LDAP directory.
Use bindpasswd as the password for simple authentication.
-b Use searchbase as the starting point for the search instead of
Generate a "data" file to be processed by tinydns-data
-o db For each zone generate a "<zonename>.db" file to be used by
Print output in LDIF format for reimport.
Hostname of LDAP server, defaults to localhost.
Portnumber to connect to LDAP server, defaults to 389
Update DNS data after numsecs. Defaults to 59 if started as
Important notice: data.cdb is rewritten only after DNSserial in
DNSzone is increased.
This command is executed after ldap2dns regenerated its data
-v Run in verbose mode.
-vv Run in even more verbose mode.
-V Print version and exit.
LDAP2DNS_UPDATE The LDAP2DNS_UPDATE environment variable sets the time
interval in seconds to update DNS data. This variable is overridden by
LDAP2DNS_OUTPUT Specify the type of output. It may be set to ’data’ so
that its output may be used by tinydns. It may be set to ’db’ so that
its output may be used by
TINYDNSDIR The root-directory used by tinydns, ie. the one in which to
tinydns expects its ’data’-file.
Options specified here fulfil the same purpose as for other ldap-tools.
ldap.conf(5), ldapsearch(1), tinydns, named.conf(5).
Please visit the project homepage for more detail:
This manual page was written by Johann Botha <email@example.com>, for the
Debian GNU/Linux system and is distributed under the GPL version 2 or
Jacob Rief <firstname.lastname@example.org> is the original author of this
May 22, 2001