Ondřej Surý 8bf311c769 Shutdown the fetch context after canceling the last fetch ... Currently, the fetch context will continue running even when the last fetch (response) has been removed from the context, so named can process and cache the answer. This can lead to a situation where the number of outgoing recursing clients exceeds the the configured number for recursive-clients. Be more stringent about the recursive-clients limit and shutdown the fetch context immediately after the last fetch has been canceled from that particular fetch context.		2025-01-22 14:21:51 +01:00
..
bind9	Remove redundant parentheses from the return statement	2024-11-19 16:06:16 +01:00
dns	Shutdown the fetch context after canceling the last fetch	2025-01-22 14:21:51 +01:00
irs	Reduce sizeof isc_sockaddr from 152 to 48 bytes	2025-01-22 14:12:38 +01:00
isc	Reduce struct isc__nm_uvreq size from 1560 to 560 bytes	2025-01-22 14:12:38 +01:00
isccc	Remove redundant parentheses from the return statement	2024-11-19 16:06:16 +01:00
isccfg	Implement 'max-query-count'	2024-12-06 15:17:53 +00:00
ns	Remove --with-tuning=small/large configuration option	2025-01-22 14:16:40 +01:00
.gitignore	The isc/platform.h header has been completely removed	2021-07-06 05:33:48 +00:00
Makefile.am	move samples/resolve.c to bin/tests/system	2021-04-16 14:29:43 +02:00