Skip to content

Commit 6353bba

Browse files
authored
Merge pull request #104343 from KumudD/ghissue47014
Remove broken link
2 parents f49969a + 65a950a commit 6353bba

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -100,8 +100,7 @@ There are a number of different DNS caching packages available (such as dnsmasq)
100100

101101
> [!NOTE]
102102
> The dnsmasq package is only one of many DNS caches available for Linux. Before using it, check its suitability for your particular needs, and check that no other cache is installed.
103-
>
104-
>
103+
105104

106105
### Client-side retries
107106

@@ -164,8 +163,7 @@ If forwarding queries to Azure doesn't suit your needs, you should provide your
164163
* Be secured against access from the internet, to mitigate threats posed by external agents.
165164

166165
> [!NOTE]
167-
> 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. For additional performance analysis and optimizations when you are using Windows Server as your DNS server, see [Name resolution performance of a recursive Windows DNS Server 2012 R2](https://blogs.technet.com/b/networking/archive/2015/08/19/name-resolution-performance-of-a-recursive-windows-dns-server-2012-r2.aspx).
168-
>
166+
> 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.
169167
>
170168
171169
### Web apps

0 commit comments

Comments
 (0)