--- Begin Message ---
Tony Finch wrote:
>
> So I wonder if Google have implemented EDNS TCP keepalive. If you change
> what BIND calls tcp-advertised-timeout, do Google's TCP connection
> lifetimes change to match?
Google Public DNS has not implemented EDNS TCP keepalive, neither as a
server for its clients, nor in its TCP connections to authoritative
servers. Has BIND added support on its client side, or only as a DNS
server? It seems like Unbound has client and server-side support (
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231283), and the GetDNS
client code also supports it (https://getdnsapi.net/releases/getdns-0-9-0/)
but those are the only ones I found. I don't see any implementations of RFC
8490 (DNS Stateful Operations).
In any case, as I wrote before, the TCP connections Jake is seeing are not
from Google Public DNS, and quite possibly not even DNS at all (let alone
EDNS).
@alex
smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
