Skip to content

Commit 329e828

Browse files
committed
warnings and typos
1 parent dcf64e3 commit 329e828

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -122,12 +122,13 @@ To configure properly you would need the following resources:
122122
- Private DNS zones [privatelink.database.windows.net](../dns/private-dns-privatednszone.md)  with [type A Record](../dns/dns-zones-records.md#record-types)
123123
- Private endpoint information (FQDN record name and Private IP Address)
124124

125-
The following diagram illustrates the DNS resolution sequence from an on premise network that use a DNS server deployed in Azure, where the resolution is made by an private DNS zone linked to a virtual network.
125+
The following diagram illustrates the DNS resolution sequence from an on premise network that use a DNS server deployed in Azure,
126+
where the resolution is made by an private DNS zone linked to a virtual network.
126127

127128
:::image type="content" source="media/private-endpoint-dns/on-premise-using-azure-dns.png" alt-text="on premise using azure dns":::
128129

129130
This configuration can be extended for an on premise network that has already a DNS solution in place. 
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+
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.
131132

132133
> [!NOTE]
133134
> 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).
@@ -139,7 +140,8 @@ To configure properly you would need the following resources :
139140
- Virtual network [connected to on premises](https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/) 
140141
- Private DNS zones [privatelink.database.windows.net](../dns/private-dns-privatednszone.md)  with [type A Record](../dns/dns-zones-records.md#record-types)
141142
- Private endpoint information (FQDN record name and Private IP Address)
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+
144+
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
143145

144146
> [!IMPORTANT]
145147
> 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

0 commit comments

Comments
 (0)