-
Notifications
You must be signed in to change notification settings - Fork 14
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
Configure DNS routing domains when using systemd-resolved on Linux #798
Comments
We could hard code that behavior in ZET and it would be useful. Still, if ZET provided a configuration hook or plug-in runner for this, then I can imagine how useful that would be for both:
For example, if a domain name is added or removed to ZET's list of intercepts, it could sort and execute each in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ziti-edge-tunnel currently sets itself up as a DNS server with systemd-resolved, but it doesn't set the "routing domains" to the specific domains that are being intercepted. This means that:
Setting the routing domains for the zitiN interface to the list of intercepted domains would solve these problems. This would also match the behavior that we see with the Desktop tunnelers.
The text was updated successfully, but these errors were encountered: