Local Domain Fallback
Hi Everyone,
I’m hoping someone might be able to assist. I’ve configured Local Domain Fallback in the Warp client, but it doesn’t seem to resolve anything. I followed the documentation here: , it looks pretty straightforward.
I’ve already set up tunnels to my AWS infrastructure, and that part works fine, for example, I can SSH into servers through the Zero Trust Warp client from my local machine.
However, when I try running an nslookup, I’m getting the following error:
Has anyone managed to get Local Domain Fallback working successfully and could share some guidance?
I’m also facing another issue, we’re using an HAProxy connected via a VPN from the office to AWS. The HAProxy currently whitelists our VPN IPs, allowing local users to connect. I need to achieve the same setup using the Warp client. From what I understand, HAProxy will only see the egress IP from the Warp client, not the internal IP assigned on connection.
Does anyone know what those egress IPs might be so I can temporarily whitelist them for testing as i cant find any mention of what the egress IPs might be for the warp client? From my research, it seems static egress IPs are only available on Enterprise plans, but if there’s a workaround or known IP range, that would be great to know.
Thanks in advanced..
I’m hoping someone might be able to assist. I’ve configured Local Domain Fallback in the Warp client, but it doesn’t seem to resolve anything. I followed the documentation here: , it looks pretty straightforward.
I’ve already set up tunnels to my AWS infrastructure, and that part works fine, for example, I can SSH into servers through the Zero Trust Warp client from my local machine.
However, when I try running an nslookup, I’m getting the following error:
nslookup 'server' Server: connectivity-check.warp-svc Address: 127.0.2.2 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to connectivity-check.warp-svc timed-out
Has anyone managed to get Local Domain Fallback working successfully and could share some guidance?
I’m also facing another issue, we’re using an HAProxy connected via a VPN from the office to AWS. The HAProxy currently whitelists our VPN IPs, allowing local users to connect. I need to achieve the same setup using the Warp client. From what I understand, HAProxy will only see the egress IP from the Warp client, not the internal IP assigned on connection.
Does anyone know what those egress IPs might be so I can temporarily whitelist them for testing as i cant find any mention of what the egress IPs might be for the warp client? From my research, it seems static egress IPs are only available on Enterprise plans, but if there’s a workaround or known IP range, that would be great to know.
Thanks in advanced..
