Sun Microsystems, Inc.
spacer | | |  
black dot
A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z
System Administration Commandsnamed-xfer(1M)


 named-xfer - ancillary agent for inbound zone transfers


 named-xfer -z zone_to_transfer -f db_file -s serial_no [-d debuglevel] [-l debug_log_file] [-t trace_file] [-p port#] [-S] nameserver ...



The named-xfer program is an ancillary program executed by in.named to perform an inbound zone transfer. It is rarely executed directly, and only by system administrators who are trying to debug a zone transfer problem. See RFC's 1033, 1034, and 1035 for more information on the Internet name-domain system.


Specifies the name of the zone to be transferred.
Specifies the name of the file into which the zone should be dumped when it is received from the primary server.
Specifies the serial number of the current copy of this zone. If the SOA RR from the primary server does not have a serial number higher than this, the transfer will be aborted.
Print debugging information. A number after the ``d'' determines the level of messages printed.
Specifies a log file for debugging messages. The default is system- dependent but is usually in /var/tmp or /usr/tmp. Note that this only applies if -d is also specified.
Specifies a trace file which will contain a protocol trace of the zone transfer. This is probably only of interest to those debugging the name server itself.
Use a different port number. The default is the standard port number as returned by getservbyname(3SOCKET) for service ``domain''.
Perform a restricted transfer of only the SOA, NS records and glue A records for the zone. The SOA record will not be loaded by named but will be used to determine when to verify the NS records. See the ``stubs'' directive in in.named(1M) for more information.

Additional arguments are taken as name server addresses in so-called ``dotted-quad'' syntax only; no host names are allowed. At least one address must be specified. If the first one fails to transfer successfully, the additional addresses will be tried in the order given.



See attributes(5) for descriptions of the following attributes:




in.named(1M), resolver(3RESOLV), resolv.conf(4), hostname(1),

RFC 882

RFC 883

RFC 973

RFC 974

RFC 1033

RFC 1034

RFC 1035

RFC 1123

Name Server Operations Guide for BIND

SunOS 5.9Go To TopLast Changed 6 Nov 2000

Copyright 2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.