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
..
dns.c	A few changes for TTL processing:	2025-09-15 10:03:35 +02:00
dns.h	A few changes for TTL processing:	2025-09-15 10:03:35 +02:00
infra.c	- Fix #1263: Exempt loopback addresses from wait-limit.	2025-04-03 09:45:36 +02:00
infra.h	Fast Reload Option (#1042)	2025-03-31 15:25:24 +02:00
rrset.c	A few changes for TTL processing:	2025-09-15 10:03:35 +02:00
rrset.h	- When a granchild delegation is returned, remove any cached child delegations	2024-04-22 15:46:06 +02:00