Hi Wolfgang,
This domain gives a lot of IPv6 timeouts for me while resolving (which
contribute to the global send out quota).
Could you try with 'do-ip6: no' or 'prefer-ip4: yes' and see if the
problem persists?
Best regards,
-- Yorgos
On 06/11/2024 18:26, Wolfgang Breyha via Unbound-users wrote:
On 06/11/2024 16:32, Yorgos Thessalonikefs via Unbound-users wrote:
Thanks for bringing this up!
We also had other operational feedback about the value and we decided to
bump it up to 200 from the initial 128.
Still keeping the possible amplification factor for CAMP-style issues in
the hundreds.
https://github.com/NLnetLabs/unbound/commit/
fd1a1d5fa0f012e8eeaa0ecc89da52d9ca25c216
Ok, tried that as well. Changed config only by adding
max-global-quota: 200
The empty cache produced for
at.mirrors.cicku.me. AAAA
debug: request at.mirrors.cicku.me. has exceeded the maximum global quota
on number of upstream queries 201
with a final top of 222 :( I think even 200 is too low especially with near
empty cache or there is something else involved as well.
I'm tempted to raise the bar to full 8 bits;-)
Greetings, Wolfgang
