draft-khrabrov-dnsop-aname-axfr-00 - Address-specific DNS Aliases (ANAME) and Zone Transfer
Skip to main content
Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.<br>Please enable Javascript for full functionality.
Address-specific DNS Aliases (ANAME) and Zone Transfer
draft-khrabrov-dnsop-aname-axfr-00
Status
Email expansions
History
Versions:
This document is an Internet-Draft (I-D).<br>Anyone may submit an I-D to the IETF.<br>This I-D is not endorsed by the IETF and has no formal standing in the<br>IETF standards process.
Document<br>Type
Active Internet-Draft<br>(individual)
Author
Alexy Khrabrov
Last updated
2026-07-30
RFC stream
(None)
Intended RFC status
(None)
Formats
txt
html
xml
htmlized
bibtex
bibxml
Stream
Stream state
(No stream defined)
Consensus boilerplate
Unknown
RFC Editor Note
(None)
IESG
IESG state
I-D Exists
Telechat date
(None)
Responsible AD
(None)
Send notices to
(None)
Email authors
IPR
References
Referenced by
Nits
Nits v3
Search email archive
draft-khrabrov-dnsop-aname-axfr-00
Domain Name System Operations A. Khrabrov<br>Internet-Draft QueryGraph<br>Intended status: Standards Track 30 July 2026<br>Expires: 31 January 2027
Address-specific DNS Aliases (ANAME) and Zone Transfer<br>draft-khrabrov-dnsop-aname-axfr-00
Abstract
This document defines the ANAME DNS resource record. ANAME provides<br>name-to-name indirection for address queries while allowing other<br>resource record types to exist at the same owner name. It is<br>therefore usable at a zone apex.
This document also defines authoritative processing, TTL and failure<br>behavior, DNSSEC considerations, and interoperable transport of ANAME<br>records in full and incremental zone transfers. In particular, each<br>ANAME-capable authoritative server resolves the transferred target<br>independently. This avoids treating transient, synthesized address<br>records as the portable source of zone data.
Discussion Venue
This note is to be removed before publishing as an RFC.
Source for this draft and an issue tracker are available at<br>https://github.com/querygraph/rgbdns/tree/master/ietf.
Status of This Memo
This Internet-Draft is submitted in full conformance with the<br>provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering<br>Task Force (IETF). Note that other groups may also distribute<br>working documents as Internet-Drafts. The list of current Internet-<br>Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months<br>and may be updated, replaced, or obsoleted by other documents at any<br>time. It is inappropriate to use Internet-Drafts as reference<br>material or to cite them other than as "work in progress."
This Internet-Draft will expire on 31 January 2027.
Khrabrov Expires 31 January 2027 [Page 1]<br>Internet-Draft ANAME and Zone Transfer July 2026
Copyright Notice
Copyright (c) 2026 IETF Trust and the persons identified as the<br>document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal<br>Provisions Relating to IETF Documents (https://trustee.ietf.org/<br>license-info) in effect on the date of publication of this document.<br>Please review these documents carefully, as they describe your rights<br>and restrictions with respect to this document. Code Components<br>extracted from this document must include Revised BSD License text as<br>described in Section 4.e of the Trust Legal Provisions and are<br>provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3<br>2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3<br>3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4<br>4. The ANAME Resource Record . . . . . . . . . . . . . . . . . . 4<br>4.1. Presentation and Wire Format . . . . . . . . . . . . . . 4<br>4.2. Cardinality and Coexistence . . . . . . . . . . . . . . . 5<br>5. Target Resolution and Address Synthesis . . . . . . . . . . . 5<br>5.1. Resolution Timing and Caching . . . . . . . . . . . . . . 6<br>5.2. Negative Answers and Failure . . . . . . . . . . . . . . 6<br>6. Query Processing . . . . . . . . . . . . . . . . . . . . . . 6<br>6.1. A and AAAA Queries . . . . . . . . . . . . . . . . . . . 6<br>6.2. ANAME Queries . . . . . . . . . . . . . . . . . . . . . . 7<br>6.3. Other Query Types and Delegations . . . . . . . . . . . . 7<br>7. Zone Transfer . . . . . . . . . . . . . . . . . . . . . . . . 7<br>7.1. Native AXFR . . . . . . . . . . . . . . . . . . . . . . . 7<br>7.2. Native IXFR . . . . . . . . . . . . . . . . . . . . . . . 8<br>7.3. Capability Signaling . . . . . . . . . . . . . . . . . . 8<br>7.4. Transition with ANAME-oblivious Secondaries . . . . . . . 8<br>7.5. Transfer Authentication . . . . . . . . . . . . . . . . . 9<br>8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9<br>8.1. Native Primary and Secondary . . . . . . . . . . . . . . 9<br>8.2. Changing the Target . . . ....