metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5936: DNS Zone Transfer Protocol (AXFR)

Still current, but amended. Parts of this document are changed or extended by RFC 9103. Read both.

In plain English — editorial summary, not part of the RFC

The standard means within the Domain Name System protocol for maintaining coherence among a zone's authoritative name servers consists of three mechanisms. Authoritative Transfer (AXFR) is one of the mechanisms and is defined in RFC 1034 and RFC 1035. The definition of AXFR has proven insufficient in detail, thereby forcing implementations intended to be compliant to make assumptions, impeding interoperability. Yet today we have a satisfactory set of implementations that do interoperate. This document is a new definition of AXFR -- new in the sense that it records an accurate definition of an interoperable AXFR mechanism. [STANDARDS-TRACK]

Document record

Document ID
RFC5936
Published
June 2010
Authors
E. Lewis; A. Hoenes
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
29
Also known as
—
Updates:
RFC 1034, RFC 1035
Updated by:
RFC 9103

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5936-dns-zone-transfer-protocol-axfr