A. Schulze via Unbound-users:
On a plattform with broken TCP FASTOPEN support (even if not
supported by the kernel)
I currently cant disable it, I would need an other unbound binary - right?
is there really no option to disable TCP_FASTOPEN usage by configuration?
clarification is
W.C.A. Wijngaards via Unbound-users:
The failure you see is in the code for TCP FASTOPEN. It was enabled
when you gave the configure option --enable-tfo-client.
TCP FASTOPEN...
your explanation match perfectly to my observation :-)
I just tried to disable any ipfilter on the failing host.
Hi Andreas,
The failure you see is in the code for TCP FASTOPEN. It was enabled
when you gave the configure option --enable-tfo-client.
We cannot do r = sendmsg(fd, , MSG_FASTOPEN); to perform a TCP
FASTOPEN on the tcp connection. It returns the errno that you see printed.
That cheap VM has
Hello,
the Domain use huge keys: https://zonemaster.net/test/f8b42c485139ea99
Also DNSViz http://dnsviz.net/d/kernel-error.de/dnssec/ show warnings.
But most of my unbound-host resolve without problems except instances on
"cheap hosted virtual machines"
As far as I can tell all unbound servers
