Skip to content

Commit 3e2047f

Browse files
Merge pull request #215924 from greg-lindsay/dns-upd
Update private-resolver-endpoints-rulesets.md
2 parents d897abd + cd51461 commit 3e2047f

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: greg-lindsay
66
ms.service: dns
77
ms.custom: ignite-2022
88
ms.topic: conceptual
9-
ms.date: 10/13/2022
9+
ms.date: 10/25/2022
1010
ms.author: greglin
1111
#Customer intent: As an administrator, I want to understand components of the Azure DNS Private Resolver.
1212
---
@@ -86,6 +86,9 @@ For example, if you have the following rules:
8686

8787
A query for `secure.store.azure.contoso.com` will match the **AzurePrivate** rule for `azure.contoso.com` and also the **Contoso** rule for `contoso.com`, but the **AzurePrivate** rule takes precedence because the prefix `azure.contoso` is longer than `contoso`.
8888

89+
> [!NOTE]
90+
> You can't enter the Azure DNS IP address of 168.63.129.16 as the destination IP address for a rule. Attempting to add this IP address will output the error: **Exception while making add request for rule**. Instead, use the private resolver's inbound endpoint IP address as the destination.
91+
8992
## Next steps
9093

9194
* Review components, benefits, and requirements for [Azure DNS Private Resolver](dns-private-resolver-overview.md).

0 commit comments

Comments
 (0)