premise back to premises

Author: greg-lindsay

articles/dns/dns-private-resolver-get-started-portal.md

@@ -15,7 +15,7 @@ ms.custom: mode-ui
 
 This quickstart walks you through the steps to create an Azure DNS Private Resolver (Public Preview) using the Azure portal. If you prefer, you can complete this quickstart using [Azure PowerShell](private-dns-getstarted-powershell.md).
 
-Azure DNS Private Resolver enables you to query Azure DNS private zones from an on-premise environment, and vice versa, without deploying VM based DNS servers. You no longer need to provision IaaS based solutions on your virtual networks to resolve names registered on Azure private DNS zones. You can configure conditional forwarding of domains back to on-premise, multi-cloud and public DNS servers. For more information, including benefits, capabilities, and regional availability, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md).
+Azure DNS Private Resolver enables you to query Azure DNS private zones from an on-premises environment, and vice versa, without deploying VM based DNS servers. You no longer need to provision IaaS based solutions on your virtual networks to resolve names registered on Azure private DNS zones. You can configure conditional forwarding of domains back to on-premise, multi-cloud and public DNS servers. For more information, including benefits, capabilities, and regional availability, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md).
 
 ## Prerequisites
 
@@ -101,13 +101,13 @@ Next, add a virtual network to the resource group that you created, and configur
 
 ## Create a second virtual network
 
-Create a second virtual network to simulate an on-premise or other environment. To create a second virtual network:
+Create a second virtual network to simulate an on-premises or other environment. To create a second virtual network:
 
 1. Select **Virtual Networks** from the **Azure services** list, or search for **Virtual Networks** and then select **Virtual Networks**.
 2. Select **Create**, and then on the **Basics** tab select your subscription and choose the same resource group that you have been using in this guide (ex: myresourcegroup).
 3. Next to **Name**, enter a name for the new virtual network (ex: myvnet2).
 4. Verify that the **Region** selected is the same region used previously in this guide (ex: West Central US).
-5. Select the **IP Addresses** tab and edit the default IP address space. Replace the address space with a simulated on-premise address space (ex: 12.0.0.0/8). 
+5. Select the **IP Addresses** tab and edit the default IP address space. Replace the address space with a simulated on-premises address space (ex: 12.0.0.0/8). 
 6. Select **Add subnet** and enter the following:
     - Subnet name: backendsubnet
     - Subnet address range: 12.2.0.0/24
@@ -131,7 +131,7 @@ To apply your forwarding ruleset to the second virtual network, you must create
 
 Add or remove specific rules your DNS forwarding ruleset as desired, such as:
 - A rule to resolve an Azure Private DNS zone linked to your virtual network: azure.contoso.com.
-- A rule to resolve an on-premise zone: internal.contoso.com.
+- A rule to resolve an on-premises zone: internal.contoso.com.
 - A wildcard rule to forward unmatched DNS queries to a protective DNS service.
 
 ### Delete a rule from the forwarding ruleset
@@ -166,7 +166,7 @@ Add three new conditional forwarding rules to the ruleset.
 
 In this example: 
 - 10.0.0.4 is the resolver's inbound endpoint. 
-- 192.168.1.2 is an on-premise DNS server.
+- 192.168.1.2 is an on-premises DNS server.
 - 10.5.5.5 is a protective DNS service.
 
 ## Test the private resolver

articles/dns/dns-private-resolver-get-started-powershell.md

@@ -17,7 +17,7 @@ This article walks you through the steps to create your first private DNS zone a
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
-Azure DNS Private Resolver is a new service currently in public preview. Azure DNS Private Resolver enables you to query Azure DNS private zones from an on-premise environment and vice versa without deploying VM based DNS servers. For more information, including benefits, capabilities, and regional availability, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md).
+Azure DNS Private Resolver is a new service currently in public preview. Azure DNS Private Resolver enables you to query Azure DNS private zones from an on-premises environment and vice versa without deploying VM based DNS servers. For more information, including benefits, capabilities, and regional availability, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md).
 
 ## Prerequisites
 
@@ -107,7 +107,7 @@ $virtualNetwork | Set-AzVirtualNetwork
 
 ### Create the inbound endpoint
 
-Create an inbound endpoint to enable name resolution from on-premise or another private location using an IP address that is part of your private virtual network address space.
+Create an inbound endpoint to enable name resolution from on-premises or another private location using an IP address that is part of your private virtual network address space.
 
 ```Azure PowerShell
 $ipconfig = New-AzDnsResolverIPConfigurationObject -PrivateIPAllocationMethod Dynamic -SubnetId /subscriptions/<your sub id>/resourceGroups/myresourcegroup/providers/Microsoft.Network/virtualNetworks/myvnet/subnets/snet-inbound
@@ -189,7 +189,7 @@ $virtualNetworkLink.ToJsonString()
 
 ## Create a second virtual network and link it to your DNS forwarding ruleset
 
-Create a second virtual network to simulate an on-premise or other environment.
+Create a second virtual network to simulate an on-premises or other environment.
 
 ```Azure PowerShell
 $vnet2 = New-AzVirtualNetwork -Name myvnet2 -ResourceGroupName myresourcegroup -Location westcentralus -AddressPrefix "12.0.0.0/8"
@@ -221,7 +221,7 @@ $forwardingrule = New-AzDnsForwardingRulesetForwardingRule -ResourceGroupName my
 
 In this example: 
 - 10.0.0.4 is the resolver's inbound endpoint. 
-- 192.168.1.2 and 192.168.1.3 are on-premise DNS servers.
+- 192.168.1.2 and 192.168.1.3 are on-premises DNS servers.
 - 10.5.5.5 is a protective DNS service.
 
 ## Test the private resolver

articles/dns/dns-private-resolver-overview.md

@@ -13,7 +13,7 @@ ms.author: greglin
 
 # What is Azure DNS Private Resolver? 
 
-Azure DNS Private Resolver is a new service that enables you to query Azure DNS private zones from an on-premise environment and vice versa without deploying VM based DNS servers. 
+Azure DNS Private Resolver is a new service that enables you to query Azure DNS private zones from an on-premises environment and vice versa without deploying VM based DNS servers. 
 
 > [!IMPORTANT]
 > Azure DNS Private Resolver is currently in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). 
@@ -36,7 +36,7 @@ The DNS query process when using an Azure DNS Private Resolver is summarized bel
 8. If multiple matches are present, the longest suffix is used.
 9. If no match is found, no DNS forwarding occurs and Azure DNS is used to resolve the query.
 
-The architecture for Azure DNS Private Resolver is summarized in the following figure. DNS resolution between Azure virtual networks and on-premise networks requires [Azure ExpressRoute](../expressroute/expressroute-introduction.md) or a [VPN](../vpn-gateway/vpn-gateway-about-vpngateways.md).
+The architecture for Azure DNS Private Resolver is summarized in the following figure. DNS resolution between Azure virtual networks and on-premises networks requires [Azure ExpressRoute](../expressroute/expressroute-introduction.md) or a [VPN](../vpn-gateway/vpn-gateway-about-vpngateways.md).
 
 [ ![Azure DNS Private Resolver architecture](./media/dns-resolver-overview/resolver-architecture.png) ](./media/dns-resolver-overview/resolver-architecture_highres.png#lightbox)
 
@@ -76,7 +76,7 @@ Azure DNS Private Resolver is available in the following regions:
 
 ### Inbound endpoints
 
-An inbound endpoint enables name resolution from on-premise or other private locations via an IP address that is part of your private virtual network address space. To resolve your Azure private DNS zone from on-premise, enter the IP address of the inbound endpoint into your on-premise DNS conditional forwarder. The on-premise DNS conditional forwarder must have a network connection to the virtual network.
+An inbound endpoint enables name resolution from on-premises or other private locations via an IP address that is part of your private virtual network address space. To resolve your Azure private DNS zone from on-premise, enter the IP address of the inbound endpoint into your on-premises DNS conditional forwarder. The on-premises DNS conditional forwarder must have a network connection to the virtual network.
 
 The inbound endpoint requires a subnet in the VNet where it’s provisioned. The subnet can only be delegated to **Microsoft.Network/dnsResolvers** and can't be used for other services. DNS queries received by the inbound endpoint will ingress to Azure. You can resolve names in scenarios where you have Private DNS zones, including VMs that are using auto registration, or Private Link enabled services.
 
@@ -133,7 +133,7 @@ Outbound endpoints have the following limitations:
 ## Next steps
 
 * Learn how to create an Azure DNS Private Resolver by using [Azure PowerShell](./dns-private-resolver-get-started-powershell.md) or [Azure portal](./dns-private-resolver-get-started-portal.md).
-* Understand how to [Resolve Azure and on-premise domains](private-resolver-hybrid-dns.md) using the Azure DNS Private Resolver.
+* Understand how to [Resolve Azure and on-premises domains](private-resolver-hybrid-dns.md) using the Azure DNS Private Resolver.
 * Learn about [Azure DNS Private Resolver endpoints and rulesets](private-resolver-endpoints-rulesets.md).
 * Learn how to [Set up DNS failover using private resolvers](tutorial-dns-private-resolver-failover.md)
 * Learn how to [configure hybrid DNS](private-resolver-hybrid-dns.md) using private resolvers.

articles/dns/private-resolver-endpoints-rulesets.md

@@ -19,7 +19,7 @@ In this article, you'll learn about components of the [Azure DNS Private Resolve
 
 ## Inbound endpoints
 
-As the name suggests, inbound endpoints will ingress to Azure. Inbound endpoints provide an IP address to forward DNS queries from on-premise and other locations outside your virtual network. DNS queries sent to the inbound endpoint are resolved using Azure DNS. Private DNS zones that are linked to the virtual network where the inbound endpoint is provisioned are resolved by the inbound endpoint. 
+As the name suggests, inbound endpoints will ingress to Azure. Inbound endpoints provide an IP address to forward DNS queries from on-premises and other locations outside your virtual network. DNS queries sent to the inbound endpoint are resolved using Azure DNS. Private DNS zones that are linked to the virtual network where the inbound endpoint is provisioned are resolved by the inbound endpoint. 
 
 The IP address associated with an inbound endpoint is always part of the private virtual network address space where the private resolver is deployed.  No other resources can exist in the same subnet with the inbound endpoint. The following screenshot shows an inbound endpoint with an IP address of 10.10.0.4 inside the subnet `snet-E-inbound` provisioned within a virtual network with address space of 10.10.0.0/16.
 
@@ -75,7 +75,7 @@ A query for `secure.store.azure.contoso.com` will match the **AzurePrivate** rul
 
 * Review components, benefits, and requirements for [Azure DNS Private Resolver](dns-private-resolver-overview.md).
 * Learn how to create an Azure DNS Private Resolver by using [Azure PowerShell](./dns-private-resolver-get-started-powershell.md) or [Azure portal](./dns-private-resolver-get-started-portal.md).
-* Understand how to [Resolve Azure and on-premise domains](private-resolver-hybrid-dns.md) using the Azure DNS Private Resolver.
+* Understand how to [Resolve Azure and on-premises domains](private-resolver-hybrid-dns.md) using the Azure DNS Private Resolver.
 * Learn how to [Set up DNS failover using private resolvers](tutorial-dns-private-resolver-failover.md)
 * Learn how to [configure hybrid DNS](private-resolver-hybrid-dns.md) using private resolvers.
 * Learn about some of the other key [networking capabilities](../networking/fundamentals/networking-overview.md) of Azure.