named-xfer(8) [osf1 man page]

named-xfer(8)						      System Manager's Manual						     named-xfer(8)

NAME

       named-xfer - Pulls BIND zones from another server

SYNOPSIS

       /usr/sbin/named-xfer  -z  zone_to_transfer  -f  db_file	-s  serial_no  [-d debug_level] [-l debug_log_file] [-t trace_file] [-p port] [-S]
       servers...

OPTIONS

       Specifies the name of the BIND zone for the named-xfer daemon to transfer, for example, dec.com. This option is required to  pull  a  zone.
       Specifies  the  name  of the file into which the pulled zone information is placed. This option is  required to pull a zone.  Specifies the
       current serial number of the SOA record for the zone zone_to_transfer.  If serial_no is set to 0, the zone is always pulled. This option is
       required  to  pull  a  zone.  Sets the debug level and determines the amount of debug information to be displayed.  Specifies the file that
       will contain any debug messages from the zone pull.  Specifies the file that will contain a trace from the zone pull.  Specifies  the  port
       that  will  be  used  instead  of the default name server port listed in /etc/services.	Performs a restricted transfer of only the SOA, NS
       records and glue A records for the zone. The SOA record is not loaded by named, but is used to determine when to  verify  the  NS  records.
       See named(8) for more information.  Specifies a list of Internet addresses, in dotted-quad format, from which to pull a zone.  If the first
       host cannot be reached, the named transfer daemon tries to pull the zone from the next host listed.

DESCRIPTION

       The named transfer daemon, /usr/sbin/named-xfer, is a server that is usually run by the named daemon, /usr/sbin/named, but it can  also	be
       run  manually  with  the  given	arguments.   The named transfer daemon runs on a BIND secondary server and pulls BIND zones from a primary
       server. This daemon is not run by default, nor can it be started up from inetd(8).

SEE ALSO

       Commands: named(8)

       Files: resolver(4), services(4)

																     named-xfer(8)

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)