bind2csv2(1) [debian man page]

BIND2CSV2(1)							 MaraDNS reference						      BIND2CSV2(1)

NAME

       bind2csv2 - convert zone files from BIND to MaraDNS compatible format

DESCRPTION

       MaraDNS 1.3 has BIND zone file support. This means it is possible to use BIND zone files in MaraDNS. This makes it easier for people to use
       MaraDNS in mixed DNS server environments.

       Instead of having direct BIND zone file support, MaraDNS has a script, called bind2csv2, that converts BIND zone files in to the "csv2"
       zone file format that MaraDNS 1.2 and 1.3 use. The zone files generated by bind2csv2 are not MaraDNS 1.2 compatible; MaraDNS 1.3 is needed
       to read zone files generated by bind2csv2.

       bind2csv2 is a Python script, written in version 2.2.3 of the Python interpreter. The script should be compatible with more recent versions
       of Python. The script assumes Python is the file /usr/bin/python on your system; if Python is located elsewhere on your system, please
       change the first line of bind2csv2. Naturally, you will need the Python interpreter installed on your system to use bind2csv2.  This is a
       well-known open source language supported by most modern Linux and BSD distributions.

USAGE

       To use the script, enter a directory containing BIND zone files, and invoke the script thusly:

       bind2csv2 -c zone1 zone2 zone3

       Substitute "zone1", "zone2", and "zone3" with a list of one or more BIND zone files you wish be converted in to MaraDNS 1.3 csv2 zone
       files.

       Once the script is run, you should have files with names like "zone1.csv2", "zone2.csv2", and "zone3.csv2". These files are csv2 zone files
       that MaraDNS will be able to parse. Copy these csv2 zone files to a place where MaraDNS can find the zone files.

       Should there already be a "zone1.csv2" file when bind2csv2 is run, the "zone1.csv2" file will be replaced.

OPTIONS

       None. Bind2csv2 can only be used as above.

BUGS

       bind2csv2 is not a perfect zone file converter. In particular, bind2csv2 does not act like BIND when NS records have different TTLs. Please
       make sure all NS records in your BIND zone files have the same TTL.

       In addition, bind2csv2 also does not support all resource record types that BIND supports. Only the following RRs are supported by
       bind2csv2: A AAAA AFSDB CNAME GPOS HINFO ISDN LOC MB MD MF MG MINFO MR MX NS NSAP PTR PX RP RT SOA SPF SRV TXT WKS X25

MARADNS 
							  September 2007						      BIND2CSV2(1)

zone2ldap(1)						      General Commands Manual						      zone2ldap(1)

NAME

       zone2ldap /- Load BIND 9 Zone files into LDAP Directory

SYNOPSIS

       zone2ldap  [-D Bind DN] [-w Bind Password] [-b Base DN] [-z Zone] [-f Zone File ] [-h Ldap Host] [-cd] [-v]

DESCRIPTION

       zone2ldap  will parse a complete BIND 9 format DNS zone file, and load the contents into an LDAP directory, for use with the LDAP sdb back-
       end.

       If the zone already exists, zone2ldap will exit succesfully. If the zone does not exists, or partially exists, zone2ldap  will  attempt	to
       add all/missing zone data.

   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 immediatly 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  lis-
	      tening on port 389 of the target system. This may be ommited, 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.

EXAMPLES

       Following are brief examples of how to import a zone file into your LDAP DIT.

   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.

SEE ALSO

       named(8) ldap(3) http://www.venaas.no/ldap/bind-sdb/

BUGS

       Send all bug reports to Jeff McNeil <jeff@snapcase.g-rock.net>

AUTHOR

       Jeff McNeil <jeff@snapcase.g-rock.net>

								   8 March 2001 						      zone2ldap(1)