You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In official document https://learn.microsoft.com/en-us/azure/batch/batch-virtual-network#general-virtual-network-requirements, the third bullet point of "General virtual network requirements" part, it's saying:
If you aren't using Simplified Compute Node Communication, you need to resolve your Azure Storage endpoints by using any custom DNS servers that serve your virtual network. Specifically, URLs of the form .table.core.windows.net, .queue.core.windows.net, and .blob.core.windows.net should be resolvable.
But per my test result, when I create a Batch pool with Azure Virtual Network, but also with Batch managed public IP address, plus the Azure Virtual Network is configured to use Azure DNS as default option, in this case, even without any custom DNS server, the node in this Batch pool can work as expected.
The current expression in the document may make user think the private DNS server is a necessary thing (in fact it's not) when we create Batch pool with Virtual Network. Could you please consider to improve this expression?
The text was updated successfully, but these errors were encountered:
@JerryZhangMS
Thank you for bringing this to our attention.
I've delegated this to content author @Padmalathas, who will review it and offer their insightful opinions.
In official document https://learn.microsoft.com/en-us/azure/batch/batch-virtual-network#general-virtual-network-requirements, the third bullet point of "General virtual network requirements" part, it's saying:
If you aren't using Simplified Compute Node Communication, you need to resolve your Azure Storage endpoints by using any custom DNS servers that serve your virtual network. Specifically, URLs of the form .table.core.windows.net, .queue.core.windows.net, and .blob.core.windows.net should be resolvable.
But per my test result, when I create a Batch pool with Azure Virtual Network, but also with Batch managed public IP address, plus the Azure Virtual Network is configured to use Azure DNS as default option, in this case, even without any custom DNS server, the node in this Batch pool can work as expected.
The current expression in the document may make user think the private DNS server is a necessary thing (in fact it's not) when we create Batch pool with Virtual Network. Could you please consider to improve this expression?
The text was updated successfully, but these errors were encountered: