From a1f8826b11178d07f85993f9723751c58c5e1d2f Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Thu, 11 Feb 2016 16:06:19 -0800 Subject: [PATCH] minor formatting update --- articles/remoteapp/remoteapp-hybridtrouble.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/articles/remoteapp/remoteapp-hybridtrouble.md b/articles/remoteapp/remoteapp-hybridtrouble.md index 06f3935e1fe..52aba1bc94c 100644 --- a/articles/remoteapp/remoteapp-hybridtrouble.md +++ b/articles/remoteapp/remoteapp-hybridtrouble.md @@ -38,7 +38,8 @@ You can add additional network security groups to the VMs deployed by you in the ## Are you using your own DNS servers? And are they accessible from your VNET subnet? ## >[AZURE.NOTE] You have to make sure the DNS servers in your VNET are always up and always able to resolve the virtual machines hosted in the VNET. Don't use google dns for this. -> + + For hybrid collections you use your own DNS servers. You specify them in your network configuration schema or through the management portal when you create your virtual network. DNS servers are used in the order that they are specified in a failover manner (as opposed to round robin). Make sure the DNS servers for your collection are accessible and available from the VNET subnet you specified for this collection.