Options¶

-b

LDAP Base DN. LDAP systems require a "base dn", which is generally considered the LDAP Directory root. If the zone you are loading is different from the base, then you will need to tell zone2ldap what your LDAP base is.

-v

Print version information, and immediately exit.

-f

Zone file. Bind 9.1 compatible zone file, from which zone information will be read.

-d

Dump debug information to standard out.

-w

LDAP Bind password, corresponding the the value of "-b".

-h

LDAP Directory host. This is the hostname of the LDAP system you wish to store zone information on. An LDAP server should be listening on port 389 of the target system. This may be omitted, and will default to "localhost".

-c

This will create the zone portion of the DN you are importing. For instance, if you are creating a domain.com zone, zone2ldap should first create "dc=domain,dc=com". This is useful if you are creating multiple domains.

-z

This is the name of the zone specified in the SOA record.

Loading zone domain.com, with an LDAP Base DN of dc=domain,dc=com¶

zone2ldap -D dc=root -w secret -h localhost -z domain.com -f domain.com.zone

This will add Resource Records into an ALREADY EXISTING dc=domain,dc=com. The final SOA DN in this case, will be dc=@,dc=domain,dc=com

Loading customer.com, if your LDAP Base DN is dc=provider,dc=net.¶

zone2ldap -D dc=root -w secret -h localhost -z customer.com -b dc=provider,dc=net -f customer.com.zone -c

This will create dc=customer,dc=com under dc=provider,dc=net, and add all necessary Resource Records. The final root DN to the SOA will be dc=@,dc=customer,dc=com,dc=provider,dc=net.