diff options
| author | David Lönnhager <david.l@mullvad.net> | 2021-03-31 13:16:39 +0200 |
|---|---|---|
| committer | David Lönnhager <david.l@mullvad.net> | 2021-03-31 13:16:39 +0200 |
| commit | ad1070d5252ff06691667fecebf6a31451683616 (patch) | |
| tree | d2ac4446992a75d8edd4d4a7f94e8a01c1b65b64 | |
| parent | 34146f17bee2e62fea0437a553a110d02bd139ca (diff) | |
| parent | 95e11ef39b1d55c77490a5526ac5c87971a570ef (diff) | |
| download | mullvadvpn-ad1070d5252ff06691667fecebf6a31451683616.tar.xz mullvadvpn-ad1070d5252ff06691667fecebf6a31451683616.zip | |
Merge branch 'update-split-tunnel-docs'
| -rw-r--r-- | docs/split-tunneling.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/split-tunneling.md b/docs/split-tunneling.md index b4eb40b151..ff9838f81d 100644 --- a/docs/split-tunneling.md +++ b/docs/split-tunneling.md @@ -21,7 +21,9 @@ or not running. But this is very hard/impossible to achieve on some platforms. One reason for this is that on some operating systems, programs call into a system service for name resolution. This system service will then perform the actual DNS lookup. Since all DNS requests then originate from the same process/system service, it becomes hard -to know which ones are for excluded apps and which ones are not. +to know which ones are for excluded apps and which ones are not. Because the DNS service is not +excluded, DNS lookups **will fail** in the connecting, disconnecting, and error +[states](architecture.md) whenever they must be sent through a tunnel. Some definitions of terms used later to describe behavior: |
