Hello,
Is “was_ratelimited” intended to be undocumented? There’s no mention of it in libunbound(3).
Thank you!
-FG
Hello,
Is “was_ratelimited” intended to be undocumented? There’s no mention of it in libunbound(3).
Thank you!
-FG
Hi Felipe,
That wasn't the intention; seems I missed to update the manpage when I
introduced the field.
It is now commited on master.
'was_ratelimited' will be true if ratelimiting is enabled in unbound
(via the ratelimit* options) that results in SERVFAIL answers back to
the client.
'was_ratelimited' will be useful then if you want to queue the query for
later.
Thanks for noticing!
Best regards,
-- George
Hello,
What is the idea of this value? Is it that, if libunbound has met a threshold of concurrent requests, it will refuse to send out any further requests until some have finished?
If so, is that threshold configurable?
Thank you!
cheers,
-Felipe Gasper
Hi Felipe,
This was added to help users that have set a ratelimiting option towards nameservers (i.e. the ratelimit* options, not the ip-ratelimit* options) differentiate between SERVFAIL answers for other reasons and SERVFAIL answers because the ratelimit was engaged.
Best regard,
-- George