Skip to content

Commit b56760e

Browse files
authored
Update virtual-networks-name-resolution-for-vms-and-role-instances.md
1 parent 4e651d7 commit b56760e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ When resources deployed in virtual networks need to resolve domain names to inte
2323

2424
The type of name resolution you use depends on how your resources need to communicate with each other. The following table illustrates scenarios and corresponding name resolution solutions.
2525

26-
Azure Private DNS zones is the preferred solution and gives you flexibility in managing your DNS zones and records. For more information, see [Use Azure DNS for private domains](../dns/private-dns-overview.md).
26+
Azure Private DNS zones are the preferred solution and give you flexibility in managing your DNS zones and records. For more information, see [Use Azure DNS for private domains](../dns/private-dns-overview.md).
2727

2828
> [!NOTE]
2929
> If you use Azure-provided DNS, the appropriate DNS suffix is automatically applied to your VMs.

0 commit comments

Comments
 (0)