Developer's Daily | Unix by Example |
main | java | perl | unix | dev directory | web log |
NAMED-XFER(8) BSD System Manager’s Manual NAMED-XFER(8)
NAME
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] [?i ixfr_file] [?t trace_file] [?p port#] [?S] nameserver [[file ... axfr] | [ixfr]] |
DESCRIPTION |
Named-xfer is an ancillary program executed by named(8) 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 RFC’s 1033, 1034, and 1035 for more information on the Internet name-domain system. Options are: |
?z zone_to_transfer
specifies the name of the zone to be transferred. ?f db_file ?s serial_no ?d debuglevel ?l debug_log_file ?i ixfr_file ?t trace_file ?p port#’ Use a different port number. The default is the standard port number as returned by getservbyname(3) 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(8) but will be used to determine when to verify the NS records. See the ‘‘stubs’’ directive in named(8) for more information. Additional arguments are taken as name server addresses in so-called ‘‘dotted-quad’’ syntax only; no host name 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. The axfr or ixfr after name server address designates the type of zone transfer to perform. Use axfr for a full zone transfer or ixfr for an incremental zone transfer. SEE ALSO |
hostname(7), named(8), resolver(3), resolver(5), RFC 882, RFC 883, RFC 973, RFC 974, RFC 1033, RFC 1034, RFC 1035, RFC 1123, RFC 1995 ‘‘Name Server Operations Guide for BIND’’. 4th Berkeley Distribution June 26, 1993 4th Berkeley Distribution |