Skip to content

Commit 11236ed

Browse files
committed
remove sentence
1 parent 85a9cde commit 11236ed

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: dns
55
author: greg-lindsay
66
ms.service: dns
77
ms.topic: conceptual
8-
ms.date: 10/23/2023
8+
ms.date: 03/26/2024
99
ms.author: greglin
1010
#Customer intent: As an administrator, I want to understand components of the Azure DNS Private Resolver.
1111
---
@@ -109,7 +109,7 @@ A query for `secure.store.azure.contoso.com` matches the **AzurePrivate** rule f
109109
110110
#### Rule processing
111111

112-
- 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. Destination addresses that are marked as unresponsive aren't used for 30 minutes.
112+
- 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.
113113
- Certain domains are ignored when using a wildcard rule for DNS resolution, because they are 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.
114114

115115
> [!IMPORTANT]

0 commit comments

Comments
 (0)