xNAME RCODE and Status Bits Clarification
RFC 6604, “xNAME RCODE and Status Bits Clarification”, is a Proposed Standard document published in April 2012 by D. Eastlake 3rd. It updates RFC 1035, RFC 2308, RFC 2672. The canonical text is published by the RFC Editor.
Abstract
The Domain Name System (DNS) has long provided means, such as the CNAME (Canonical Name), whereby a DNS query can be redirected to a different name. A DNS response header has an RCODE (Response Code) field, used for indicating errors, and response status bits. This document clarifies, in the case of such redirected queries, how the RCODE and status bits correspond to the initial query cycle (where the CNAME or the like was detected) and subsequent or final query cycles. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6604 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6603 Prefix Exclude Option for DHCPv6-based Prefix Delegation
- RFC 6605 Elliptic Curve Digital Signature Algorithm for DNSSEC
- RFC 6602 Bulk Binding Update Support for Proxy Mobile IPv6
- RFC 6606 Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network Routing
- RFC 6601 Generic Connection Admission Control Algorithm Specification for IP/MPLS Networks
- RFC 6607 Virtual Subnet Selection Options for DHCPv4 and DHCPv6
- RFC 6608 Subcodes for BGP Finite State Machine Error
- RFC 6609 Sieve Email Filtering: Include Extension