Skip to content

Commit 569e4f7

Browse files
Merge pull request #270993 from asudbring/vnet-dns
Updated web app section for newer endpoint integration and github issue
2 parents 72104ee + 583d257 commit 569e4f7

File tree

1 file changed

+2
-8
lines changed

1 file changed

+2
-8
lines changed

articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Name resolution scenarios for Azure IaaS, hybrid solutions, between
55
author: asudbring
66
ms.service: virtual-network
77
ms.topic: how-to
8-
ms.date: 04/27/2023
8+
ms.date: 04/02/2024
99
ms.author: allensu
1010
ms.custom: fasttrack-edit, linux-related-content
1111
---
@@ -338,11 +338,7 @@ If you provide your own DNS solution, it needs to:
338338

339339
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:
340340

341-
1. Enable virtual network integration for your web app, if not done already, as described in [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-
![Screenshot of virtual network name resolution](./media/virtual-networks-name-resolution-for-vms-and-role-instances/webapps-dns.png)
341+
Enable virtual network integration for your web app, if not done already, as described in [Integrate your app with a virtual network](../app-service/overview-vnet-integration.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
346342

347343
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.
348344

@@ -356,8 +352,6 @@ To use custom DNS servers:
356352
357353
* 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).
358354
359-
* In the Azure portal, for the App Service plan hosting the web app, select **Sync Network** under **Networking**, **Virtual Network Integration**.
360-
361355
To use an Azure DNS Private Resolver, see [Ruleset links](../dns/private-resolver-endpoints-rulesets.md#ruleset-links).
362356
363357
## Specify DNS servers

0 commit comments

Comments
 (0)