How to setup point to site vpn to got access to azure resource by private link

Hi Radek,

Sorry for the Delay!!

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

It sounds like you’ve configured your VPN and PostgreSQL database with a private endpoint but are encountering issues with name resolution when trying to access the database. Here’s a checklist of things to verify and steps to troubleshoot this issue.

1. Forwarding DNS Requests:

Deploy a DNS forwarder VM within your VNet. This VM will forward DNS requests for privatelink.postgres.database.azure.com to the appropriate Azure DNS server for resolution.

Custom DNS Servers: (Limited functionality)

Edit the downloaded Azure VPN client configuration file (azurevpnconfig.xml) and add the custom DNS server IP address responsible for resolving private link names.

Using a DNS Forwarder is the solution nowadays to resolve private DNS zones and it works fine.

If you want a more in-depth documentation about it, you can go here:

• https://video2.skills-academy.com/en-us/azure/private-link/private-endpoint-dns#dns-configuration-scenarios

1. Protection against data leakage: A private endpoint is mapped to an instance of a PaaS resource instead of the entire service. Consumers can only connect to the specific resource. Access to any other resource in the service is blocked. This mechanism provides basic protection against data leakage risks.

NOTE: Assumptions and needs for these scenarios are shown below as examples for Reference.

• Below is diagram with the DNS name resolution flow from P2S VPN connection. The solution is broken down in two solutions where in first configuration is set DNS Server IP (Forwarder/Proxy) on VNET DNS settings, which is the easiest way to implement, and second solution is to specific DNS Server settings directly on Azure VPN client XML profile. The main reason to break down is two solutions is because having DNS settings at the VNET level does not affect only P2S VPN clients but also all resources deployed inside the VNET. Therefore, you may have the flexibility only to set that setting over VPN client XLM profile to only be used by those remote user VPN connections instead of affecting also resources deployed inside the VNET. Below you can review a reference diagram of this solution as well as traffic pattern for DNS name resolution and access to Private Endpoint:

• Specify DNS Server for the Virtual Network

Specify DNS Setting at the VNET level as shown:

After you save the settings above you a reconnected-on Azure VPN Client will trigger it to learn DNS Server settings specified at VNET level as shown:

Name Resolution Validation

Use PowerShell command:

Resolve-DnsName -Name ["Storage account FQDN name"]- (DNS Only)

For example, using storage account name is: dmcentralus.blob.core.windows.net output is:

• Specify DNS Server inside VPN Client Profile:

Download VPN Client profile to your computer and add DNS settings.

Refer: https://video2.skills-academy.com/en-us/azure/vpn-gateway/point-to-site-entra-vpn-client-windows#how-do-i-add-custom-dns-servers-to-the-vpn-client

If you are still facing any further issues, please don't hesitate to reach out to us. We are happy to assist you.

Looking forward to your response and appreciate your time on this.

Regards,

Ganesh