5b85f848dd
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> |
||
|---|---|---|
| .. | ||
| debug.go | ||
| doh_test.go | ||
| forwarder.go | ||
| forwarder_test.go | ||
| macios_ext.go | ||
| tsdns.go | ||
| tsdns_server_test.go | ||
| tsdns_test.go | ||