24bdcbe5c7
* net/dns, net/dns/resolver, wgengine: refactor DNS request path Previously, method calls into the DNS manager/resolver types handled DNS requests rather than DNS packets. This is fine for UDP as one packet corresponds to one request or response, however will not suit an implementation that supports DNS over TCP. To support PRs implementing this in the future, wgengine delegates all handling/construction of packets to the magic DNS endpoint, to the DNS types themselves. Handling IP packets at this level enables future support for both UDP and TCP. Signed-off-by: Tom DNetto <tom@tailscale.com> |
||
|---|---|---|
| .. | ||
| dns | ||
| dnscache | ||
| dnsfallback | ||
| flowtrack | ||
| interfaces | ||
| netcheck | ||
| neterror | ||
| netknob | ||
| netns | ||
| netstat | ||
| nettest | ||
| netutil | ||
| packet | ||
| portmapper | ||
| proxymux | ||
| socks5 | ||
| speedtest | ||
| stun | ||
| tlsdial | ||
| tsaddr | ||
| tsdial | ||
| tshttpproxy | ||
| tstun | ||