Skip to main content

Measures for Making DNS More Resilient against Forged Answers
RFC 5452

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The current Internet climate poses serious threats to the Domain Name System. In the interim period …
Received changes through RFC Editor sync (changed abstract to 'The current Internet climate poses serious threats to the Domain Name System. In the interim period before the DNS protocol can be secured more fully, measures can already be taken to harden the DNS to make 'spoofing' a recursing nameserver many orders of magnitude harder.

Even a cryptographically secured DNS benefits from having the ability to discard bogus responses quickly, as this potentially saves large amounts of computation.

By describing certain behavior that has previously not been standardized, this document sets out how to make the DNS more resilient against accepting incorrect responses. This document updates RFC 2181. [STANDARDS-TRACK]')
2017-05-16
(System) Changed document authors from "Remco Mook" to "Remco Mook, Bert Hubert"
2015-10-14
(System) Notify list changed from dnsext-chairs@ietf.org, draft-ietf-dnsext-forgery-resilience@ietf.org to (None)
2009-02-02
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2009-02-02
Cindy Morgan [Note]: 'RFC 5452' added by Cindy Morgan
2009-01-28
(System) RFC published