Tom DNetto 5b85f848dd net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver ... Moves magicDNS-specific handling out of Resolver & into dns.Manager. This greatly simplifies the Resolver to solely issuing queries and returning responses, without channels. Enforcement of max number of in-flight magicDNS queries, assembly of synthetic UDP datagrams, and integration with wgengine for recieving/responding to magicDNS traffic is now entirely in Manager. This path is being kept around, but ultimately aims to be deleted and replaced with a netstack-based path. This commit is part of a series to implement magicDNS using netstack. Signed-off-by: Tom DNetto <tom@tailscale.com>		2022-04-30 10:18:59 -07:00
..
debug.go	net/dns/resolver: add debug HTML handler to see what DNS traffic was forwarded	2021-12-21 14:32:36 -08:00
doh_test.go	net/dns: schedule DoH upgrade explicitly, fix Resolver.Addr confusion	2022-04-19 12:00:22 -07:00
forwarder_test.go	net/dns: schedule DoH upgrade explicitly, fix Resolver.Addr confusion	2022-04-19 12:00:22 -07:00
forwarder.go	net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver	2022-04-30 10:18:59 -07:00
macios_ext.go	all: simplify ts_macext build tags	2021-08-17 11:13:03 -07:00
tsdns_server_test.go	all: use any instead of interface{}	2022-03-17 11:35:09 -07:00
tsdns_test.go	net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver	2022-04-30 10:18:59 -07:00
tsdns.go	net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver	2022-04-30 10:18:59 -07:00