That is also a good option. It really surprised me as I did not know that TCP was a hard requirement for queries. In my old know how, TCP was for zone transfers, but not for queries, but I admit I never dove into it extremely deep. Naive, no, but lacking knowledge, yes (those are not the same...).
> On 6 May 2021, at 12:37, Anand Buddhdev via Unbound-users > <[email protected]> wrote: > > On 06/05/2021 11:25, Gerben Wierda via Unbound-users wrote: > > TCP has been a requirement for a long time. > > Perhaps unbound should drop the "do-tcp" option altogether. I don't > really see a need to disable TCP, and providing such an option just > allows naive users to shoot themselves in the foot. > > Regards, > Anand > >> Ah. I was under the impression that I could have a setup that >> doesn’t >> do TCP at all, but it seems that these days, TCP is a requirement. >> >> Basically, do-tcp must be a yes to be able to resolve the entire >> internet. do-tcp: no means some names will not resolve. And this will >> become worse over time. Setting do-tcp to no might come with a decent >> warning, then.
