metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 6604: xNAME RCODE and Status Bits Clarification

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6604
Published
April 2012
Authors
D. Eastlake 3rd
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
5
Also known as
—
Updates:
RFC 1035, RFC 2308, RFC 2672

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6604-xname-rcode-and-status-bits-clarification