RFC 10029: DNS Multiple QTYPEs
In plain English — editorial summary, not part of the RFC
This document specifies a method for a DNS client to request additional DNS record types to be delivered alongside the primary record type specified in the Question section of a DNS QUERY (OpCode=0).
Document record
- Document ID
- RFC10029
- Published
- July 2026
- Authors
- R. Bellis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3110RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)Updated
May 2001
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 4641DNSSEC Operational PracticesObsoleted
September 2006
- RFC 9539Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNSCurrent
February 2024
- RFC 9527DHCPv6 Options for the Homenet Naming AuthorityCurrent
January 2024
- RFC 9526Simple Provisioning of Public Names for Residential NetworksCurrent
January 2024
- RFC 9463DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)Current
November 2023
- RFC 9462Discovery of Designated ResolversCurrent
November 2023
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?