Re: Best way to handle multiple retries from BIND?

Well in this case... I'd be more interested in ways to tune BIND's internal resolver behavior. On Sun, 25 Jun 2023, Randy Bush wrote: If you have a true duplicate you only need to answer it once otherwise you have different clients and you need to answer all of them. Note there can be

Changes to GitLab Sign-Up policy

Hey all, we had a massive Spam surge over couple past days, so we had to tighten the GitLab Sign-Up policy, so we don't waste our time on deleting spam from the issues. There's now couple of domains that are on denylist for signups: - hotmail.com - outlook.com

Re: DNSSEC doubt

Perhaps this article is a better read for you: https://kb.isc.org/v1/docs/en/dnssec-key-and-signing-policy Best regards, Matthijs On 6/22/23 22:03, Daniel A. Rodriguez via bind-users wrote: Thanks, I was reading but wasn't able to decode that. Best regards El 22 de junio de 2023 4:27:21

Re: Best way to handle multiple retries from BIND?

I would suggest doing what forwarders do, joining multiple queries into single upstream request. When the answer arrives, send replies to all requestors of this common transaction. If you cannot fix your server to handle the response right away and have pre-computed answers, as is common for