diff options
| author | Andrew Dunham <andrew@tailscale.com> | 2026-01-26 12:43:24 -0500 |
|---|---|---|
| committer | Andrew Dunham <andrew@du.nham.ca> | 2026-01-26 14:14:39 -0500 |
| commit | 8d875a301c8bdaceb5814eab100a90cb725b2018 (patch) | |
| tree | 381f0657d6fadeb83fb32949440d0b54d0da7e4b /control/controlhttp/controlhttpserver | |
| parent | 0e1b2b15f1a9a609213d99d527ca448711775b13 (diff) | |
| download | tailscale-8d875a301c8bdaceb5814eab100a90cb725b2018.tar.xz tailscale-8d875a301c8bdaceb5814eab100a90cb725b2018.zip | |
net/dns: add test for DoH upgrade of system DNS
Someone asked me if we use DNS-over-HTTPS if the system's resolver is an
IP address that supports DoH and there's no global nameserver set (i.e.
no "Override DNS servers" set). I didn't know the answer offhand, and it
took a while for me to figure it out. The answer is yes, in cases where
we take over the system's DNS configuration and read the base config, we
do upgrade any DoH-capable resolver to use DoH. Here's a test that
verifies this behaviour (and hopefully helps as documentation the next
time someone has this question).
Updates #cleanup
Signed-off-by: Andrew Dunham <andrew@tailscale.com>
Diffstat (limited to 'control/controlhttp/controlhttpserver')
0 files changed, 0 insertions, 0 deletions