Skip to content

Commit bc7b509

Browse files
committed
on-premises wording fix
1 parent b614b54 commit bc7b509

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ In this scenario, there's a [hub & spoke](https://docs.microsoft.com/azure/archi
110110
For on-premises workloads to be able to resolve an FQDN of a private endpoint into the private IP address, you must use a DNS forwarder to make the resolution of the Azure service [public DNS zone](#azure-services-dns-zone-configuration) deployed in Azure.
111111

112112

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)
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)
114114

115115
> [!NOTE]
116116
> 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).
@@ -123,7 +123,7 @@ To configure properly, you would need the following resources:
123123
- Private DNS zones [privatelink.database.windows.net](../dns/private-dns-privatednszone.md) with [type A Record](../dns/dns-zones-records.md#record-types)
124124
- Private endpoint information (FQDN record name and Private IP Address)
125125

126-
The following diagram illustrates the DNS resolution sequence from an on premises network that uses a DNS forwarder deployed in Azure,
126+
The following diagram illustrates the DNS resolution sequence from an on-premises network that uses a DNS forwarder deployed in Azure,
127127
where the resolution is made by a private DNS zone linked to a virtual network.
128128

129129
:::image type="content" source="media/private-endpoint-dns/on-premises-using-azure-dns.png" alt-text="On-premises using Azure DNS":::

0 commit comments

Comments
 (0)