Skip to content

Commit a896bee

Browse files
committed
remove changes
1 parent 72ae40e commit a896bee

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

articles/dns/dns-private-resolver-overview.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.custom: references_regions
66
author: greg-lindsay
77
ms.service: dns
88
ms.topic: overview
9-
ms.date: 05/20/2024
9+
ms.date: 12/05/2023
1010
ms.author: greglin
1111
#Customer intent: As an administrator, I want to evaluate Azure DNS Private Resolver so I can determine if I want to use it instead of my current DNS resolver service.
1212
---
@@ -92,10 +92,6 @@ A DNS forwarding rule includes one or more target DNS servers that are used for
9292
- A target IP address
9393
- A target Port and Protocol (UDP or TCP)
9494

95-
## Requirements
96-
97-
Inbound endpoints must be accessible on UDP and TCP port 53 for the clients that it serves. The DNS service uses UDP port 53 for most communications, but relies on TCP port 53 for transmission of large DNS packets. If UDP or TCP port 53 is blocked, this can cause DNS resolution issues.
98-
9995
## Restrictions
10096

10197
The following limits currently apply to Azure DNS Private Resolver:

0 commit comments

Comments
 (0)