Skip to content

Commit d9c0e45

Browse files
authored
Remove misleading statement for Public IP
Public IP address is not required for internet FQDN name resolution. If keep this statement in public, please clarify the benefit and scenario.
1 parent 7d8158f commit d9c0e45

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ ms.tgt_pltfrm: na
1212
ms.workload: infrastructure-services
1313
ms.date: 3/2/2020
1414
ms.author: rohink
15+
ms.custom: fasttrack-edit
1516
---
1617

1718
# Name resolution for resources in Azure virtual networks
@@ -181,8 +182,7 @@ If forwarding queries to Azure doesn't suit your needs, you should provide your
181182
* Be secured against access from the internet, to mitigate threats posed by external agents.
182183

183184
> [!NOTE]
184-
> For best performance, when you are using Azure VMs as DNS servers, IPv6 should be disabled. A [public IP address](virtual-network-public-ip-address.md) should be assigned to each DNS server VM.
185-
>
185+
> For best performance, when you are using Azure VMs as DNS servers, IPv6 should be disabled.
186186
187187
### Web apps
188188
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:

0 commit comments

Comments
 (0)