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

ZeroTrust/Team name servers not used with option -T enabled #15

Open
open5443 opened this issue Sep 30, 2024 · 1 comment
Open

ZeroTrust/Team name servers not used with option -T enabled #15

open5443 opened this issue Sep 30, 2024 · 1 comment

Comments

@open5443
Copy link

Hi,

when creating a WireGuard config for ZeroTrust/Teams (option -T), the general Cloudflare name servers are used in the config that is output:
DNS = 1.1.1.1, 1.0.0.1, 2606:4700:4700::1111, 2606:4700:4700::1001

However these are not the name servers of ZeroTrust. Consequently ZeroTrust DNS filtering features etc. will not work. The name servers need to be changed to the ones shown in the ZeroTrust Web Interface:
ZeroTrust Web Interface → Gateway → DNS locations → Default location → IPv4 endpoint & IPv6 endpoint (172.64.XX.1, 172.64.XX.2, 2a06:98c1:54::XXXX:XXXX)

Not sure if that is on purpose and if the right name servers can be automatically used when creating the WireGuard config. If not, then it might be worth making a note in the readme, so people who try to create a ZeroTrust profile will know about this issue and know how to manually change the name servers with the ones shown in their accounts.

@MagneticNeedle
Copy link

+1 for this, i'll try to find some way to fetch them

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