On Fri, Jun 19, 2026 at 6:23 AM, Philip Homburg <[email protected]> wrote:
> Something that came up a couple of times, in the context of DELEG and the > NS . proposal, is that there is no way for a server to indicate how long > DNS errors (other than NXDOMAIN) can be cached. > > I created a small draft to add a SOA record to the addional section. In > the current version, all processing is entirely optional. Please let me > know if this would be useful. > I think that the base idea is great, but I'm not so sure about the " the server should add a SOA record to the additional section of the reply. [...] The SOA record MUST have "_error_ttl." as owner name, and as TTL the time to live of the error. MNAME and RNAME SHOULD be set to ".". SERIAL, REFRESH, RETRY, and EXPIRE SHOULD be set to 0. For compatibility with existing SOA processing for NXDOMAIN and NODATA, The MINIMUM field SHOULD be set to the TTL of the SOA record." This feels a little clunky / hacky, and I think something more along the lines of: "The server should add the ERROR_TTL resource record (code TBD) to the additional section of the reply. The server SHOULD keep the Answer and Authority sections empty and the ERROR_TTL record SHOULD be the first record of the Additional section." instead. New RR types are (still) cheap, and not overloading an existing RR type seems to keep the intent clear. I also think that the document should provide a bit more guidance on what the server might want to set the TTL value to. But, these are just niggles, the base idea seems great, W > -------- Forwarded Message -------- > Subject: New Version Notification for draft-homburg-dnsop-dettl-00.txt > Date: Fri, 19 Jun 2026 03:13:28 -0700 > From: [email protected] > To: Philip Homburg <[email protected]> > > A new version of Internet-Draft draft-homburg-dnsop-dettl-00.txt has been > successfully submitted by Philip Homburg and posted to the IETF repository. > > Name: draft-homburg-dnsop-dettl > Revision: 00 > Title: Add TTLs to DNS errors > Date: 2026-06-19 > Group: Individual Submission > Pages: 4 > URL: https://www.ietf.org/archive/id/draft-homburg-dnsop-dettl-00.txt > Status: https://datatracker.ietf.org/doc/draft-homburg-dnsop-dettl/ HTML: > https://www.ietf.org/archive/id/draft-homburg-dnsop-dettl-00.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-homburg-dnsop-dettl > > Abstract: > > When a DNS server replies an error other than NXDOMAIN, there is no > mechanism to specify how long this error can be cached by the recepient. > This document introduces a mechanism where a server can specify the time to > live (TTL) of an error by adding a SOA record to the additional section of > a reply. Clients can use this TTL at their discretion. In particular, > clients can limit the TTL to a maximum value, impose a minimum value or > just ignore the TTL value all together. > > The IETF Secretariat > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] > >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
