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
Copy file name to clipboardExpand all lines: articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Name resolution scenarios for Azure IaaS, hybrid solutions, between
5
5
author: asudbring
6
6
ms.service: virtual-network
7
7
ms.topic: how-to
8
-
ms.date: 04/27/2023
8
+
ms.date: 04/02/2024
9
9
ms.author: allensu
10
10
ms.custom: fasttrack-edit, linux-related-content
11
11
---
@@ -338,11 +338,7 @@ If you provide your own DNS solution, it needs to:
338
338
339
339
Suppose you need to perform name resolution from your web app built by using App Service, linked to a virtual network, to VMs in the same virtual network. In addition to setting up a custom DNS server that has a DNS forwarder that forwards queries to Azure (virtual IP 168.63.129.16), perform the following steps:
340
340
341
-
1. Enable virtual network integration foryour web app, if not done already, as describedin [Integrate your app with a virtual network](../app-service/overview-vnet-integration.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
342
-
343
-
1. In the Azure portal, for the App Service plan hosting the web app, select**Sync Network** under **Networking**, **Virtual Network Integration**.
344
-
345
-

341
+
Enable virtual network integration foryour web app, if not done already, as describedin [Integrate your app with a virtual network](../app-service/overview-vnet-integration.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
346
342
347
343
If you need to perform name resolution from your vnet-linked web app (built by using App Service) to VMs in a different vnet that is **not linked** to the same private zone, use custom DNS servers or [Azure DNS Private Resolvers](../dns/dns-private-resolver-overview.md) on both vnets.
348
344
@@ -356,8 +352,6 @@ To use custom DNS servers:
356
352
357
353
* Enable virtual network integration for your web app to link to the source virtual network, following the instructions in [Integrate your app with a virtual network](../app-service/overview-vnet-integration.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
358
354
359
-
* In the Azure portal, for the App Service plan hosting the web app, select **Sync Network** under **Networking**, **Virtual Network Integration**.
360
-
361
355
To use an Azure DNS Private Resolver, see [Ruleset links](../dns/private-resolver-endpoints-rulesets.md#ruleset-links).
0 commit comments