Skip to content

Commit d12c85e

Browse files
authored
Update vpn-gateway-vpn-faq.md
added Azure DNS Private Resolver's forwarding rule
1 parent a9432c5 commit d12c85e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/vpn-gateway/vpn-gateway-vpn-faq.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,8 @@ To help ensure proper functionality and healthy state for your VPN gateway, cons
7070
* Revert to the Azure DNS default by removing the custom DNS within the VNet settings (recommended configuration).
7171
* Add in your custom DNS configuration a DNS forwarder that points to Azure DNS (168.63.129.16). Depending on the specific rules and nature of your custom DNS, this setup might not resolve the issue as expected.
7272

73+
When configuring the Azure DNS Private Resolver's forwarding rule in the VNet where the VPN Gateway is deployed, if you include a wildcard in the DNS forwarding ruleset, ensure that the forwarding destination IP points to the built-in Azure DNS service (168.63.129.16) to resolve public URLs.
74+
7375
### Can two VPN clients connected in point-to-site to the same VPN gateway communicate?
7476

7577
No. VPN clients connected in point-to-site to the same VPN gateway can't communicate with each other.

0 commit comments

Comments
 (0)