You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/net/dns/resolver
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>
4 years ago
..
debug.go net/dns/resolver: add debug HTML handler to see what DNS traffic was forwarded 4 years ago
doh_test.go net/dns: schedule DoH upgrade explicitly, fix Resolver.Addr confusion 4 years ago
forwarder.go net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver 4 years ago
forwarder_test.go net/dns: schedule DoH upgrade explicitly, fix Resolver.Addr confusion 4 years ago
macios_ext.go all: simplify ts_macext build tags 4 years ago
tsdns.go net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver 4 years ago
tsdns_server_test.go all: use any instead of interface{} 4 years ago
tsdns_test.go net/dns,net/dns/resolver: refactor channels/magicDNS out of Resolver 4 years ago