Backup resolver after X seconds

[Frank Cusack]

How about pointing unbound to a local dnsmasq instance, configured to use
parallel upstreams?

https://serverfault.com/questions/732920/how-to-do-parallel-queries-to-the-upstream-dns-using-unbound

If you don't need some specific feature of unbound, you could just use
dnsmasq by itself.

On Mon, Jun 3, 2024 at 2:02 PM Scott Q. <qmail at top-consulting.net> wrote:

> Some apps have even longer and don't even try a backup resolver
>
> On Monday, 03/06/2024 at 15:57 Frank Cusack wrote:
>
> Sorry that this isn't actually an answer, but does it matter? What client
> has a 5s timeout before the client moves on to its own next resolver?
>
> On Mon, Jun 3, 2024 at 8:28 AM Scott Q. via Unbound-users <
> unbound-users at lists.nlnetlabs.nl> wrote:
>
>> Is there a way to configure within Unbound a backup resolver for all
>> queries that take over 5 seconds for example ?
>>
>> Aka, I'd like to forward to 8.8.8.8 all queries that I can't resolve for
>> whatever reason: network issues, firewalls, etc.
>>
>> For example: dig +trace 77.184.100.61.in-addr.arpa
>>
>> This sometimes takes 10 seconds to resolve, other times it times out
>> completely but 8.8.8.8 can return an answer within 1 second.
>>
>> I also don't want to implement a per-host/network/domain solution, I just
>> want to forward all queries that take longer than 5 seconds.
>>
>> Is it possible or is there an alternative ?
>>
>> Thank you
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20240603/3c629882/attachment.htm>