mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 11:35:35 +00:00
68ddf134d7
Amazingly, there doesn't seem to be a documented way of updating network configuration programmatically in a way that Windows takes notice of. The naturopathic remedy for this is to invoke ipconfig /registerdns, which does a variety of harmless things and also invokes the private API that tells windows to notice new adapter settings. This makes our DNS config changes stick within a few seconds of us setting them. If we're invoking a shell command anyway, why futz with the registry at all? Because netsh has no command for changing the DNS suffix list, and its commands for setting resolvers requires parsing its output and keeping track of which server is in what index. Amazingly, twiddling the registry directly is the less painful option. Fixes #853. Signed-off-by: David Anderson <danderson@tailscale.com> |
||
|---|---|---|
| .. | ||
| config.go | ||
| direct.go | ||
| manager_default.go | ||
| manager_freebsd.go | ||
| manager_linux.go | ||
| manager_openbsd.go | ||
| manager_windows.go | ||
| manager.go | ||
| nm.go | ||
| noop.go | ||
| resolvconf.go | ||
| resolved.go | ||