Adrian Dewhurst 8bdf878832 net/dns/resolver: use forwarded dns txid directly ... Previously, we hashed the question and combined it with the original txid which was useful when concurrent queries were multiplexed on a single local source port. We encountered some situations where the DNS server canonicalizes the question in the response (uppercase converted to lowercase in this case), which resulted in responses that we couldn't match to the original request due to hash mismatches. This includes a new test to cover that situation. Fixes #2597 Signed-off-by: Adrian Dewhurst <adrian@tailscale.com>		2021-08-06 14:56:11 -04:00
..
doh_test.go	net/dns/resolver: fix skipped DoH test that bitrot	2021-08-02 15:26:27 -07:00
forwarder_test.go	net/dns/resolver: add test that I forgot to git add earlier	2021-08-03 08:32:18 -07:00
forwarder.go	net/dns/resolver: use forwarded dns txid directly	2021-08-06 14:56:11 -04:00
macios_ext.go	all: gofmt with Go 1.17	2021-08-05 15:54:00 -07:00
neterr_darwin.go	net/dns/resolver: permit larger max responses, signal truncation	2021-06-08 19:29:12 -04:00
neterr_other.go	all: gofmt with Go 1.17	2021-08-05 15:54:00 -07: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: use forwarded dns txid directly	2021-08-06 14:56:11 -04:00
tsdns_test.go	net/dns/resolver: use forwarded dns txid directly	2021-08-06 14:56:11 -04:00
tsdns.go	net/dns/resolver: race well-known resolvers less aggressively	2021-07-25 20:45:47 -07:00