Skip to content

Commit e72cff0

Browse files
authored
Merge pull request #127366 from malopMSFT/patch-181
Update private-endpoint-dns.md
2 parents b8ef762 + 8523869 commit e72cff0

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,16 @@ You can use the following options to configure your DNS settings for private end
2121
- **Use your DNS forwarder (optional)**. You can use your DNS forwarder to override the DNS resolution for a particular private link resource. If your [DNS server](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server) is hosted on a virtual network, you can create a DNS forwarding rule to use a private DNS zone to simplify the configuration for all private link resources.
2222

2323
> [!IMPORTANT]
24-
> We don't recommend that you override a zone that's actively in use to resolve public endpoints. Connections to resources won't be able to resolve correctly without DNS forwarding to the public DNS. To avoid issues, create a different domain name or follow the suggested name for each service below.
24+
> Is not recommended to override a zone that's actively in use to resolve public endpoints. Connections to resources won't be able to resolve correctly without DNS forwarding to the public DNS. To avoid issues, create a different domain name or follow the suggested name for each service below.
2525
2626
## Azure services DNS zone configuration
2727
Azure services will create a canonical name DNS record (CNAME) on the public DNS service to redirect the resolution to the suggested private domain name. You can override the resolution with the private IP address of your private endpoints.
2828

2929
Your applications don't need to change the connection URL. When trying to resolve using a public DNS service, the DNS server will now resolve to your private endpoints. The process does not affect your existing applications.
3030

31+
> [!IMPORTANT]
32+
> 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.
33+
3134
For Azure services, use the recommended zone names as described in the following table:
3235

3336
| Private link resource type / Subresource |Private DNS zone name | Public DNS zone forwarders |

0 commit comments

Comments
 (0)