Robert EdmondsandGitHub fceb4e8585 Mesh reply counters (#1374)
* Statistics counter for number of queries dropped by limit on reply addresses

Request list entries can be associated with multiple pending "reply
addresses". Basically each request list entry keeps its own list of
clients that should receive the response once the recursion is finished.
This requires keeping allocations around for each client, and there is
a global limit on the number of *additional* reply addresses that can
be allocated. (Each new request list entry seems to get its own initial
reply address which is not counted against the limit.)

This commit adds a statistics counter "num_queries_replyaddr_limit" that
counts the number of incoming client queries that have been dropped due
to the restriction on allocating additional reply addresses. This allows
distinguishing these drops from other kinds of drops.

* Statistics counter for number of mesh reply entries

Request list entries can be associated with multiple pending "reply
addresses". Since there is a limit on the number of additional reply
addresses that can be allocated which can cause incoming queries to be
dropped if exceeded, it would be nice to be able to track this number.

This commit basically exports the mesh_area's internal counter
`num_reply_addrs` as "threadX.requestlist.current.replies" /
"total.requestlist.current.replies".
2025-11-13 09:33:05 +01:00
2025-11-13 09:33:05 +01:00
2021-11-13 16:56:15 +02:00
2025-11-13 09:33:05 +01:00
2025-11-13 09:33:05 +01:00
2025-11-13 09:33:05 +01:00
2025-11-13 09:33:05 +01:00
2025-11-12 11:49:21 +01:00
2024-10-09 10:32:03 +02:00
2024-04-09 11:15:14 +08:00
2024-04-09 11:15:14 +08:00
2025-07-02 10:57:23 +02:00
2025-09-03 14:04:24 +02:00
2012-02-10 10:34:15 +00:00
2021-11-13 16:56:15 +02:00
2022-07-05 16:39:04 +02:00

Unbound

Github Build Status Packaging status Fuzzing Status Documentation Status Mastodon Follow

Unbound is a validating, recursive, caching DNS resolver. It is designed to be fast and lean and incorporates modern features based on open standards. If you have any feedback, we would love to hear from you. Dont hesitate to create an issue on Github or post a message on the Unbound mailing list. You can learn more about Unbound by reading our documentation.

Compiling

Make sure you have the C toolchain, OpenSSL and its include files, and libexpat installed. If building from the repository source you also need flex and bison installed. Unbound can be compiled and installed using:

./configure && make && make install

You can use libevent if you want. libevent is useful when using many (e.g., 10000) outgoing ports. Use the --with-libevent configure option to compile Unbound with libevent support.

If not, the default builtin alternative opens max 256 ports at the same time and is equally capable and a little faster.

Unbound configuration

All of Unbound's configuration options are described in the unbound.conf(5) man page, which will be installed and is also available on the Unbound documentation page for the latest version.

An example configuration file, with minimal documentation, is located in doc/example.conf.

S
Description
No description provided
Readme BSD-3-Clause
134 MiB
Languages
C 83.7%
Shell 6.1%
M4 2.4%
Makefile 2%
Yacc 1.8%
Other 4%