<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dnsop-caching-resolution-failures" target="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-caching-resolution-failures-08">
   <front>
      <title>Negative Caching of DNS Resolution Failures</title>
      <author initials="D." surname="Wessels" fullname="Duane Wessels">
         <organization>Verisign</organization>
      </author>
      <author initials="W." surname="Carroll" fullname="William Carroll">
         <organization>Verisign</organization>
      </author>
      <author initials="M." surname="Thomas" fullname="Matthew Thomas">
         <organization>Verisign</organization>
      </author>
      <date month="September" day="21" year="2023" />
      <abstract>
	 <t>   In the DNS, resolvers employ caching to reduce both latency for end
   users and load on authoritative name servers.  The process of
   resolution may result in one of three types of responses: (1) a
   response containing the requested data; (2) a response indicating the
   requested data does not exist; or (3) a non-response due to a
   resolution failure in which the resolver does not receive any useful
   information regarding the data&#x27;s existence.  This document concerns
   itself only with the third type.

   RFC 2308 specifies requirements for DNS negative caching.  There,
   caching of type (2) responses is mandatory and caching of type (3)
   responses is optional.  This document updates RFC 2308 to require
   negative caching for DNS resolution failures.

   RFC 4035 allows DNSSEC validation failure caching.  This document
   updates RFC 4035 to require caching for DNSSEC validation failures.

   RFC 4697 prohibits aggressive requerying for NS records at a failed
   zone&#x27;s parent zone.  This document updates RFC 4697 to expand this
   requirement to all query types and to all ancestor zones.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dnsop-caching-resolution-failures-08" />
   
</reference>
