Adrian Dewhurst 8b11937eaf net/dns/resolver: permit larger max responses, signal truncation ... This raises the maximum DNS response message size from 512 to 4095. This should be large enough for almost all situations that do not need TCP. We still do not recognize EDNS, so we will still forward requests that claim support for a larger response size than 4095 (that will be solved later). For now, when a response comes back that is too large to fit in our receive buffer, we now set the truncation flag in the DNS header, which is an improvement from before but will prompt attempts to use TCP which isn't supported yet. On Windows, WSARecvFrom into a buffer that's too small returns an error in addition to the data. On other OSes, the extra data is silently discarded. In this case, we prefer the latter so need to catch the error on Windows. Partially addresses #1123 Signed-off-by: Adrian Dewhurst <adrian@tailscale.com>		2021-06-08 19:29:12 -04:00
..
forwarder.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
neterr_darwin.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
neterr_other.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
neterr_windows.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
tsdns_server_test.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
tsdns_test.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
tsdns.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00