Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPNs can also use DNS for routing decisions (section 3.3) #25

Closed
magicalo opened this issue Sep 9, 2020 · 1 comment
Closed

VPNs can also use DNS for routing decisions (section 3.3) #25

magicalo opened this issue Sep 9, 2020 · 1 comment

Comments

@magicalo
Copy link

magicalo commented Sep 9, 2020

In addition to scenarios described, VPNs can use DNS for making routing decisions. So there is a scenario where VPNs need to introspect DNS traffic on both the public and private interfaces in order to make a routing decisions of that traffic. It is unclear how that capability will continue to function. (split include / split exclude based on domains) - also known as dynamic split tunneling.

@chris-box
Copy link
Contributor

Yes I can see that dynamic split tunneling could be a problem if DNS is encrypted, unless the relevant code is running on the endpoint and has the ability to see the DNS queries before they are encrypted. But I'll close the case for now as draft -01 is simplified and doesn't now consider VPNs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants