Best way to handle multiple retries from BIND?

I have an authoritative server which performs a resource intensive operation to determine an answer; sometimes it takes long enough that BIND asks again (and again!). Firing off multiple attempts to determine the answer just digs the hole deeper. What's the best approach, assuming the same client

Re: Best way to handle multiple retries from BIND?

> On 26 Jun 2023, at 11:05, Fred Morris wrote: > > I have an authoritative server which performs a resource intensive operation > to determine an answer; sometimes it takes long enough that BIND asks again > (and again!). Firing off multiple attempts to determine the answer just digs > the h

Re: Best way to handle multiple retries from BIND?

> 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 multiple clients on the same address. i gotta ask. so, for address foux, how do i know if there is one client or more than one? randy --

Re: Best way to handle multiple retries from BIND?

> On 26. 6. 2023, at 6:04, Randy Bush wrote: > > so, for address foux, how do i know if there is one client or more than > one? I think you only know that for an established TCP connection. Everything else could be port reuse. Ondřej -- Ondřej Surý — ISC (He/Him) My working hours and your wo

Re: Best way to handle multiple retries from BIND?

> On 26 Jun 2023, at 14:25, Ondřej Surý wrote: > > >> On 26. 6. 2023, at 6:04, Randy Bush wrote: >> >> so, for address foux, how do i know if there is one client or more than >> one? > > I think you only know that for an established TCP connection. Everything else > could be port reuse. W