What is the name of the domain?
example.local
What is the error number?
n/a
What is the error message?
n/a
What is the issue you’re encountering
We have a DNS server with IP 192.168.200.4 added as a local domain fallback in a Warp profile that we use to resolve hostnames for “example.local”. This Server’s IP is within the a tunneled range 192.168.200.0/24 and 192.168.200.0/24 is included in the Warp profile split tunnels. All devices are remote and have no other access to this subnet besides Warp. On occasions devices will automatically EXCLUDE 192.168.200.4 from routing and therefore DNS resolution fails and causes name resolution issues on the network. it seems to happen more often than not but sometimes works correctly and DOESN’T exlude 192.168.200.4. From my understanding this shouldn’t happen. I could understand if 192.168.200.4 was reachable BEFORE Warp connects but this is not the case. I’m wondering if Warp is updating the routes AFTER it connects and incorrectly assuming 192.168.200.4 was reachable before Warp connected. I logged this as a support ticket with Cloudflare 3 days ago and have heard nothing from them even after repeated followup and a chat with the team - we are paying a Warp standard monthly subscription which should be “Email and chat with 4 hour median initial response for urgent issues” so I’m under underwhelmed at support at the momemt. Please see the screenshot showing 192.168.200.4 being excluded.
What steps have you taken to resolve the issue?
Workaround: Added a persistent route on the affected devices so the route gets included
What are the steps to reproduce the issue?
setup a local domain fallback configuration, include the destination DNS server (or subnet) listed in local domain fallback to tunnel and warp profile
Screenshot of the error
