Update virtual-networks-name-resolution-for-vms-and-role-instances.md

ShawnJackson · web-flow · commit a1ca4ef9d112 · 2024-11-22T15:10:56.000-06:00
diff --git a/articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md b/articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md
@@ -278,8 +278,7 @@ DNS forwarding also enables DNS resolution between virtual networks and allows y
 Two virtual networks and an on-premises network use this method to do DNS resolution between virtual networks, as shown in the following diagram. An example DNS forwarder is available in the [Azure Quickstart Templates gallery](https://azure.microsoft.com/resources/templates/dns-forwarder) and [GitHub](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/dns-forwarder).
 
 > [!NOTE]
-> A role instance can perform name resolution of VMs within the same virtual network. It uses the FQDN, which consists of the VM's hostname and the `internal.cloudapp.net` DNS suffix. In this case, name resolution is successful only if the role instance has the VM name defined in the [Role Schema (.cscfg file)](/previous-versions/azure/reference/jj156212(v=azure.100)).
-> `<Role name="<role-name>" vmName="<vm-name>">`
+> A role instance can perform name resolution of VMs within the same virtual network. It uses the FQDN, which consists of the VM's hostname and the `internal.cloudapp.net` DNS suffix. In this case, name resolution is successful only if the role instance has the VM name defined in the [Role Schema (.cscfg file)](/previous-versions/azure/reference/jj156212(v=azure.100)): `<Role name="<role-name>" vmName="<vm-name>">`.
 >
 > Role instances that need to perform name resolution of VMs in another virtual network (FQDN by using the `internal.cloudapp.net` suffix) have to use the method described in this section (custom DNS servers forwarding between the two virtual networks).
 

Original file line number	Diff line number	Diff line change
`@@ -278,8 +278,7 @@ DNS forwarding also enables DNS resolution between virtual networks and allows y`
`278`	`278`	`Two virtual networks and an on-premises network use this method to do DNS resolution between virtual networks, as shown in the following diagram. An example DNS forwarder is available in the [Azure Quickstart Templates gallery](https://azure.microsoft.com/resources/templates/dns-forwarder) and [GitHub](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/dns-forwarder).`
`279`	`279`
`280`	`280`	`> [!NOTE]`
`281`		-> A role instance can perform name resolution of VMs within the same virtual network. It uses the FQDN, which consists of the VM's hostname and the `internal.cloudapp.net` DNS suffix. In this case, name resolution is successful only if the role instance has the VM name defined in the [Role Schema (.cscfg file)](/previous-versions/azure/reference/jj156212(v=azure.100)).
`282`		-> `<Role name="<role-name>" vmName="<vm-name>">`
	`281`	+> A role instance can perform name resolution of VMs within the same virtual network. It uses the FQDN, which consists of the VM's hostname and the `internal.cloudapp.net` DNS suffix. In this case, name resolution is successful only if the role instance has the VM name defined in the [Role Schema (.cscfg file)](/previous-versions/azure/reference/jj156212(v=azure.100)): `<Role name="<role-name>" vmName="<vm-name>">`.
`283`	`282`	`>`
`284`	`283`	> Role instances that need to perform name resolution of VMs in another virtual network (FQDN by using the `internal.cloudapp.net` suffix) have to use the method described in this section (custom DNS servers forwarding between the two virtual networks).
`285`	`284`