An application already connects to a storage account by its normal FQDN. After a private endpoint is created, the team wants the same application connection string to resolve to the private IP address without changing the URL. What DNS approach should be used?

Question

Accepted Answer

A. Create a private DNS zone by using the recommended privatelink zone name for the service. For private endpoints, Azure public DNS creates a CNAME to the private domain, and the recommended private DNS zone such as the appropriate privatelink zone lets the normal FQDN resolve to the private endpoint IP. Option c is wrong because NAT Gateway performs SNAT for outbound traffic and doesn't change DNS resolution.

An application already connects to a storage account by its normal FQDN. After a private endpoint is created, the team wants the same application connection string to resolve to the private IP address without changing the URL. What DNS approach should be used?

Related Questions

Discussion