You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Data Lake File System Gen2 (Microsoft.Storage/storageAccounts) | Data Lake File System Gen2 (dfs, dfs_secondary) | privatelink.dfs.core.windows.net | dfs.core.windows.net|
| Azure Database for PostgreSQL - Single server (Microsoft.DBforPostgreSQL/servers) | postgresqlServer | privatelink.postgres.database.azure.com | postgres.database.azure.com|
49
-
| Azure Database for MySQL (Microsoft.DBforMySQL/servers) | mysqlServer | privatelink.mysql.database.azure.com | mysql.database.azure.com|
| Data Lake File System Gen2 (Microsoft.Storage/storageAccounts) | Data Lake File System Gen2 (dfs, dfs_secondary) | privatelink.dfs.core.windows.net | dfs.core.windows.net |
@@ -112,7 +112,7 @@ In order to get on premises clients to resolve the IP address of a private endpo
112
112
113
113
The following scenario is appropriate for an on premises network that has a DNS forwarder in Azure, which in turn is responsible for resolving all the DNS queries via a server level forwarder to the Azure provided DNS [168.63.129.16](../virtual-network/what-is-ip-address-168-63-129-16.md)
114
114
115
-
>[!NOTE]
115
+
> [!NOTE]
116
116
> This scenario is using Azure SQL database recommended Private DNS zone. For other services you can adjust the model using the following reference [Azure services DNS zone configuration](#azure-services-dns-zone-configuration).
117
117
118
118
To configure properly you would need the following resources:
@@ -129,7 +129,7 @@ The following diagram illustrates the DNS resolution sequence from an
129
129
This configuration can be extended for an on premise network that has already a DNS solution in place.
130
130
The on premises DNS solution needs to be configured to forward DNS traffic to the Azure DNS via a [conditional forwarder](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server) referencing the Custom DNS deployed in Azure.
131
131
132
-
>[!NOTE]
132
+
> [!NOTE]
133
133
> This scenario is using Azure SQL database recommended Private DNS zone. For other services you can adjust the model using the following reference [Azure services DNS zone configuration](#azure-services-dns-zone-configuration).
134
134
135
135
To configure properly you would need the following resources :
@@ -141,7 +141,7 @@ To configure properly you would need the following resources :
141
141
- Private endpoint information (FQDN record name and Private IP Address)
142
142
The following diagram illustrates the DNS resolution sequence from an on premise network that conditionally forwards DNS traffic to Azure, where the resolution is made by an private DNS zone linked to a virtual network
143
143
144
-
>[!IMPORTANT]
144
+
> [!IMPORTANT]
145
145
> The conditional forwarding must be made to the [public DNS zone](#azure-services-dns-zone-configuration) Ex: `database.windows.net` , instead of **privatelink**.database.windows.net
146
146
147
147
:::image type="content" source="media/private-endpoint-dns/on-premise-forwarding-to-azure.png" alt-text="on premise forwarding to azure dns":::
0 commit comments