08-25-2025 01:14 PM
We have a ASAv with Secure Client setup in a Azure tenant. We have a URL in another tenant that people can access while connected to the VPN client using a cross tenant peering. It's internal access only
Problem is the domain/dns for the VPN client is different that domain/dns of the VM so obviously can not do any name resolution. The work around I have for now is to just add a host file entry and it works just fine.
Just curious if there would there be anyway to apply that using the VPN client. It is setup as a split-tunnel and I have that internal IP listed in the secure routes.
Thanks
Solved! Go to Solution.
08-25-2025 01:39 PM - edited 08-25-2025 01:40 PM
Use split-dns
-split-dns value cab.n.com.ua hr.n.com.ua
-split-tunnel-all-dns disable
MHM
08-25-2025 01:39 PM - edited 08-25-2025 01:40 PM
Use split-dns
-split-dns value cab.n.com.ua hr.n.com.ua
-split-tunnel-all-dns disable
MHM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide