named-xfer(1Mtcp)

named-xfer -- ancillary agent for inbound zone transfers

Synopsis

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 ...

Description

named-xfer is an ancillary program executed by named(1Mtcp) to perform an inbound zone transfer. It is rarely executed directly, and then only by system administrators who are trying to debug a zone transfer problem. See RFCs 1033, 1034, and 1035 for more information on the Internet Domain Name System (DNS).

Options are:

-z zone_to_transfer: Specifies the name of the zone to be transferred.
-f db_file: Specifies the name of the file, db_file, into which the zone should be dumped when it is received from the primary server.
-s serial_no: Specifies the serial number of our current copy of this zone. If the SOA RR we get from the primary server does not have a serial number higher than this, the transfer will be aborted.
-d debuglevel: Print debugging information. The debuglevel is a number that determines the level of messages printed.
-l debug_log_file: Specifies a log file for debugging messages. The default is /var/tmp/xfer.ddt.XXXXXX where the value of XXXXXX is adjusted by the system to make the file unique. Note that this only applies if -d is also specified.
-t trace_file: Specifies a trace_file which will contain a protocol trace of the zone transfer. This is probably only of interest to people debugging the name server itself.
-p port: Use a different port number. The default is the standard port number as returned by getservbyname(3N) for the service domain.
-S: 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(1Mtcp) but will be used to determine when to verify the NS records. See the stubs directive in named for more information.

Additional arguments are taken as name server addresses in ``dotted-quad'' syntax only; no hostnames are allowed here. At least one address must be specified. Any additional addresses will be tried, in order, if the first one fails to transfer to us successfully.

References

hostname(1bsd), named(1Mtcp), resolv.conf(4tcp), resolver(3N)

RFC 882, RFC 883, RFC 973, RFC 974, RFC 1033, RFC 1034, RFC 1035, RFC 1123