Skip to content

Commit 7e66289

Browse files
authored
Update private-endpoint-dns.md
A file share needs to be remounted if the customer was using it for private end point we had a customer case around this
1 parent b848841 commit 7e66289

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/private-link/private-endpoint-dns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ You can use the following options to configure your DNS settings for private end
3333

3434
Azure creates a canonical name DNS record (CNAME) on the public DNS. The CNAME record redirects the resolution to the private domain name. You can override the resolution with the private IP address of your private endpoints.
3535

36-
Your applications don't need to change the connection URL. When resolving to a public DNS service, the DNS server will resolve to your private endpoints. The process doesn't affect your existing applications.
36+
Your applications don't need to change the connection URL. When resolving to a public DNS service, the DNS server will resolve to your private endpoints. The process doesn't affect your existing applications.However the share will need to be remounted if currently mounted using public endpoint.
3737

3838
> [!IMPORTANT]
3939
> * Private networks already using the private DNS zone for a given type, can only connect to public resources if they don't have any private endpoint connections, otherwise a corresponding DNS configuration is required on the private DNS zone in order to complete the DNS resolution sequence.

0 commit comments

Comments
 (0)