Known Issue: "DNS server could not be reached" when creating or updating a RemoteApp collection using template images for some locales


  • When trying to create or update Azure RemoteApp collections that use a template image for some non-EN-US locales, it might fail with error "DNS server could not be reached". You might also see error code "DnsNotReachable". 
    Friday, March 13, 2015 2:59 PM


  • Cause:  There was a issue in Azure in which decimal punctuation was not treated properly if the locale of the template image used a comma (,) instead of a period (.).

    Workaround:  Before a fix was applied, the workaround was to use template images based on a locale that uses a period to delimit decimals, such as EN-US.

    Resolution:  As of March 19, 2015, a fix for this issue has been applied to Azure. You should once again be able to create collections from template images that use non-EN-US locales. If you continue to have this problem, please try the workaround. If that works and the only difference in the template images is the locale, please email remoteappforum (at Microsoft). If the workaround does not work, the issue is likely caused by a DNS configuration issue such as:

    • No valid forwarders to public DNS servers configured on your internal DNS server(s).
    • A valid internal DNS server is not specified on your Azure RemoteApp VNet.
    • A VNet or internal network configuration issue is preventing the internal DNS servers from be reached by the VMs in the RemoteApp collection.

    Friday, March 13, 2015 3:05 PM