Skip to content

Commit 206c8e1

Browse files
authored
Update private-resolver-endpoints-rulesets.md
Addressing ask: https://msazure.visualstudio.com/One/_workitems/edit/16998514
1 parent 04da52e commit 206c8e1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/dns/private-resolver-endpoints-rulesets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ A query for `secure.store.azure.contoso.com` matches the **AzurePrivate** rule f
112112
113113
#### Rule processing
114114

115-
- If multiple DNS servers are entered as the destination for a rule, the first IP address that is entered is used unless it doesn't respond. An exponential backoff algorithm is used to determine whether or not a destination IP address is responsive.
115+
- If multiple DNS servers are entered as the destination for a rule, the first IP address that is entered is used unless it doesn't respond. If the first DNS Server does not respond, the next DNS Server on the list is used for the next attempt. An exponential backoff algorithm is used to determine whether or not a destination IP address is responsive.
116116
- Certain domains are ignored when using a wildcard rule for DNS resolution, because they're reserved for Azure services. See [Azure services DNS zone configuration](../private-link/private-endpoint-dns.md#azure-services-dns-zone-configuration) for a list of domains that are reserved. The two-label DNS names listed in this article (for example: windows.net, azure.com, azure.net, windowsazure.us) are reserved for Azure services.
117117

118118
> [!IMPORTANT]

0 commit comments

Comments
 (0)