09-18-2024 12:49 PM
Our BI team has snowflake setup in the azure, they have whitelisted on-prem public ip addresses and Global protect public ip addresses to allow the snowflake access. We have a split tunnel GP VPN so tried with including domain and port number of the snowflake in the global protect config. which is having a DNS resolution issue? is any one have any suggestion or solution for this kind of issue? How to make this split tunnel vpn should work as a full tunnel if they have connected form remotely?
09-24-2024 08:11 PM - edited 09-24-2024 08:12 PM
Hi @tthapa23 ,
So if you try resolving the URLs, im guessing your getting the public IPs? Try creating a private DNS zone for xyz.snowflakecomputing.com in Azure. In the zone you can then configure the various CNAMEs for each of your snowflake URLS and route traffic to your Snowflake endpoints. On your AD servers that you point DNS to for GP clients, forward queries to xyz.snowflakecompting.com to the resolver inbound endpoint. I have more experience in AWS so my terms might be a bit confusing. Hope this points you in the right direction.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
