diff options
| author | Andrea Gottardo <andrea@tailscale.com> | 2024-05-29 12:11:02 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-29 12:11:02 -0700 |
| commit | dd77111462afd9dd257eeb6eea015ce45f8fe0ee (patch) | |
| tree | 547dfe331fceded8162b7aa8d9d95485792db3c6 /control/controlknobs | |
| parent | 08a9551a73adb220dc0ed1b71a2d5845efc754b8 (diff) | |
| download | tailscale-dd77111462afd9dd257eeb6eea015ce45f8fe0ee.tar.xz tailscale-dd77111462afd9dd257eeb6eea015ce45f8fe0ee.zip | |
xcode/iOS: set MatchDomains when no route requires a custom DNS resolver (#10576)
Updates https://github.com/tailscale/corp/issues/15802.
On iOS exclusively, this PR adds logic to use a split DNS configuration in more cases, with the goal of improving battery life. Acting as the global DNS resolver on iOS should be avoided, as it leads to frequent wakes of IPNExtension.
We try to determine if we can have Tailscale only handle DNS queries for resources inside the tailnet, that is, all routes in the DNS configuration do not require a custom resolver (this is the case for app connectors, for instance).
If so, we set all Routes as MatchDomains. This enables a split DNS configuration which will help preserve battery life. Effectively, for the average Tailscale user who only relies on MagicDNS to resolve *.ts.net domains, this means that Tailscale DNS will only be used for those domains.
This PR doesn't affect users with Override Local DNS enabled. For these users, there should be no difference and Tailscale will continue acting as a global DNS resolver.
Signed-off-by: Andrea Gottardo <andrea@tailscale.com>
Diffstat (limited to 'control/controlknobs')
0 files changed, 0 insertions, 0 deletions