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

IETF · RFC · RFC8767

RFC8767 · Serving Stale Data to Improve DNS Resiliency

Serving Stale Data to Improve DNS Resiliency

This document defines a method (serve-stale) for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data. One of the motivations for serve-stale is to make the DNS more resilient to DoS attacks and thereby make them less attractive as an attack vector. This document updates the definitions of TTL from RFCs 1034 and 1035 so that data can be kept in the cache beyond the TTL expiry; it also updates RFC 2181 by interpreting values with the high-order bit set as being positive, rather than 0, and suggests a cap of 7 days.

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

This document defines a method (serve-stale) for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data. One of the motivations for serve-stale is to make the DNS more resilient to DoS attacks and thereby make them less attractive as an attack vector. This document updates the definitions of TTL from RFCs 1034 and 1035 so that data can be kept in the cache beyond the TTL expiry; it also updates RFC 2181 by interpreting values with the high-order bit set as being positive, rather than 0, and suggests a cap of 7 days.

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

updates: RFC1034, RFC1035, RFC2181

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

Полные импортированные сведения карточки
{
  "id": "RFC8767",
  "number": 8767,
  "title_en": "Serving Stale Data to Improve DNS Resiliency",
  "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": "This document defines a method (serve-stale) for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data. One of the motivations for serve-stale is to make the DNS more resilient to DoS attacks and thereby make them less attractive as an attack vector. This document updates the definitions of TTL from RFCs 1034 and 1035 so that data can be kept in the cache beyond the TTL expiry; it also updates RFC 2181 by interpreting values with the high-order bit set as being positive, rather than 0, and suggests a cap of 7 days.",
  "authors": [
    "D. Lawrence",
    "W. Kumari",
    "P. Sood"
  ],
  "organizations": [],
  "publication_date": "2020-03-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "dnsop",
  "source_draft": "draft-ietf-dnsop-serve-stale-10",
  "page_count": 12,
  "doi": "10.17487/RFC8767",
  "keywords": [
    "DNS",
    "DDoS",
    "Resiliency",
    "Denial-of-Service",
    "Expired"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC1034",
      "RFC1035",
      "RFC2181"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8767/",
    "html": "https://www.rfc-editor.org/rfc/rfc8767.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8767.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8767/"
  }
}