You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: