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

[open5443]

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]

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

[Manouchehri]

Not super related to warp.sh (as it works without WARP), but for those who want to use a custom DNS location from Zero Trust with systemd-resolved, here's the config you need to set:

/etc/systemd/resolved.conf

[Resolve]
DNS=2606:4700:5c::a29f:2e07#REMOVED.cloudflare-gateway.com 2606:4700:54::a29f:2407#REMOVED.cloudflare-gateway.com
DNSOverTLS=yes

Replace REMOVED with your DNS over TLS (DoT) endpoint from Cloudflare Access Zero Trust. You do not need to enable any of the other endpoint types.

(These IPs can be found here: https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/agentless/pac-files/#configure-firewall.)

sudo systemctl restart systemd-resolved.service