Push Internal DNS Servers to warp clients while they're connected?
We have a endpoint thats got routing to an airgapped network thats connected to cloudflare with cloudflared and can only connect to cloudflare and nothing else,
we're replacing corporate VPN With warp but allowing warp clients to connect to specific internal hosts through that endpoint internally based on their roles in the internal AD, my question is we have an internal view on our internal DNS Server, is there a way to force clients to use our internal DNS through warp while they're connected?
2 Replies
You can make local domain fallbacks: https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/ so that a tld/domain and all subdomains or specific subdomain fall back to a specified DNS Server on a specific WARP Profile
Cloudflare Docs
Local Domain Fallback | Cloudflare Zero Trust docs
By default, Cloudflare Zero Trust excludes common top-level domains, used for local resolution, from being sent to Gateway for processing. These top-level domains are resolved by the local DNS resolver configured for the device on its primary interface.
I'l give that a shot tyvm ❤️