⌕ Поиск по атласу

IETF · RFC · RFC6604

RFC6604 · xNAME RCODE and Status Bits Clarification

xNAME RCODE and Status Bits Clarification

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]

Официальная английская аннотация

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]

Связи документа

updates: RFC1035, RFC2308, RFC2672

Официальный источник · 2012-04-01

Полные импортированные сведения карточки
{
  "id": "RFC6604",
  "number": 6604,
  "title_en": "xNAME RCODE and Status Bits Clarification",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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]",
  "authors": [
    "D. Eastlake 3rd"
  ],
  "organizations": [],
  "publication_date": "2012-04-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "int",
  "area_ru": "Интернет",
  "working_group": "dnsext",
  "source_draft": "draft-ietf-dnsext-xnamercode-00",
  "page_count": 5,
  "doi": "10.17487/RFC6604",
  "keywords": [
    "DNS",
    "DNSSEC",
    "CNAME",
    "DNAME",
    "Domain Name",
    "response code",
    "canonical name"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC1035",
      "RFC2308",
      "RFC2672"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6604/",
    "html": "https://www.rfc-editor.org/rfc/rfc6604.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6604.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6604/"
  }
}