Minimizing ANY-Query Responses at Recursive Resolvers
draft-li-any-responses-minimization-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | 李子涵 , Wenhao Wu , Li Qinxin , Zhaohua Wang , Jin Yan , Zhenyu Li , Zhiwei Yan | ||
| Last updated | 2026-09-03 (Latest revision 2026-03-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The "ANY" query in DNS is a meta-query intended to match multiple resource record types associated with a given domain name, and can elicit responses that are significantly larger than those generated by single-type queries. While RFC 8482 defines a mechanism for authoritative servers to minimize ANY responses, a recursive resolver may still generate an ANY query response directly from its cache, thereby bypassing the authoritative side's ANY query minimization strategy. This document provides supplementary guidance for recursive resolvers on processing ANY queries to mitigate potential operational and security issues.
Authors
李子涵
Wenhao Wu
Li Qinxin
Zhaohua Wang
Jin Yan
Zhenyu Li
Zhiwei Yan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)