Show TTL of negative response in query log #3142

New issue

Open

opened 2026-03-04 03:04:24 -05:00 by deekerman · 0 comments

deekerman commented

2026-03-04 03:04:24 -05:00

Owner

Originally created by @EugeneOne1 on GitHub (Oct 27, 2021).

In #3707 AGH began caching negative responses closer to RFC 2308. But we should improve the way they are shown in the query log. For the moment it only considers the TTL values of the message's answer section but as section 4 of RFC 2308 says:

The SOA minimum field has been overloaded in the past to have three different meanings, the minimum TTL value of all RRs in a zone, the default TTL of RRs which did not contain a TTL value and the TTL of negative responses.

Both the backend and the frontend should consider the ability of DNS message to have a TTL outside of the answer section.

Originally created by @EugeneOne1 on GitHub (Oct 27, 2021). In #3707 AGH began caching negative responses closer to [RFC 2308](https://datatracker.ietf.org/doc/html/rfc2308). But we should improve the way they are shown in the query log. For the moment it only considers the TTL values of the message's answer section but as [section 4](https://datatracker.ietf.org/doc/html/rfc2308#section-4) of RFC 2308 says: > The SOA minimum field has been overloaded in the past to have three different meanings, the minimum TTL value of all RRs in a zone, the default TTL of RRs which did not contain a TTL value and the TTL of negative responses. Both the backend and the frontend should consider the ability of DNS message to have a TTL outside of the answer section.