Skip to content

Commit 4a3db46

Browse files
committed
add note about forwarding rules
1 parent c3d19d6 commit 4a3db46

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/dns/dns-private-resolver-get-started-powershell.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: In this quickstart, you learn how to create and manage your first p
44
services: dns
55
author: greg-lindsay
66
ms.author: greglin
7-
ms.date: 02/28/2024
7+
ms.date: 04/05/2024
88
ms.topic: quickstart
99
ms.service: dns
1010
ms.custom: devx-track-azurepowershell, mode-api, ignite-2022
@@ -230,6 +230,8 @@ $virtualNetworkLink2.ToJsonString()
230230

231231
## Create forwarding rules
232232

233+
234+
233235
Create a forwarding rule for a ruleset to one or more target DNS servers. You must specify the fully qualified domain name (FQDN) with a trailing dot. The **New-AzDnsResolverTargetDnsServerObject** cmdlet sets the default port as 53, but you can also specify a unique port.
234236

235237
```Azure PowerShell
@@ -247,6 +249,9 @@ In this example:
247249
- 192.168.1.2 and 192.168.1.3 are on-premises DNS servers.
248250
- 10.5.5.5 is a protective DNS service.
249251

252+
> [!IMPORTANT]
253+
> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the fowarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.
254+
250255
## Test the private resolver
251256

252257
You should now be able to send DNS traffic to your DNS resolver and resolve records based on your forwarding rulesets, including:

0 commit comments

Comments
 (0)