RFC 7901: CHAIN Query Requests in DNS
In plain English — editorial summary, not part of the RFC
This document defines an EDNS0 extension that can be used by a security-aware validating resolver configured to use a forwarding resolver to send a single query, requesting a complete validation path along with the regular query answer. The reduction in queries potentially lowers the latency and reduces the need to send multiple queries at once. This extension mandates the use of source-IP- verified transport such as TCP or UDP with EDNS-COOKIE, so it cannot be abused in amplification attacks.
Document record
- Document ID
- RFC7901
- Published
- June 2016
- Authors
- P. Wouters
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3226DNSSEC and IPv6 A6 aware server/resolver message size requirementsUpdated
December 2001
- RFC 7871Client Subnet in DNS QueriesCurrent
May 2016
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 8078Managing DS Records from the Parent via CDS/CDNSKEYUpdated
March 2017
- RFC 8145Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)Updated
April 2017
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
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?