4 commits

Author	SHA1	Message	Date
Yorgos Thessalonikefs	73e408f1d0	A few changes for TTL processing: ... - Cached messages that reach 0 TTL are considered expired. This prevents Unbound itself from issuing replies with TTL 0 and possibly causing a thundering herd at the last second. Upstream replies of TTL 0 still get the usual pass-through but they are not considered for caching from Unbound or any of its caching modules. - 'serve-expired-reply-ttl' is changed and is now capped by the original TTL value of the record to try and make some sense when replying with expired records. - TTL decoding was updated to adhere to RFC8767 section 4 where a set high-order bit means the value is positive instead of 0.	2025-09-15 10:03:35 +02:00
W.C.A. Wijngaards	c3206f4568	- Fix for the DNSBomb vulnerability CVE-2024-33655. Thanks to Xiang Li ... from the Network and Information Security Lab of Tsinghua University for reporting it.	2024-05-01 10:10:58 +02:00
W.C.A. Wijngaards	4d530920e0	- Fixup unit test for cachedb server expired client timeout with ... a check if response if from upstream or from cachedb.	2024-04-12 11:51:00 +02:00
W.C.A. Wijngaards	08fb9a9209	- Fix cachedb for serve-expired with serve-expired-client-timeout.	2024-04-12 11:26:53 +02:00