Skip to content

Commit e841579

Browse files
ANP CSS-Networking-dns-settings.md
In the DNS proxy configuration section, I added a "Note" indicating that any IP not belonging to the Azure Firewall subnet can be used. Cases of fail state have been reported due to this reason.
1 parent 363fe2d commit e841579

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/firewall/dns-settings.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,10 @@ For example, to use FQDNs in network rule, DNS proxy should be enabled. But if a
8989
DNS proxy configuration requires three steps:
9090
1. Enable the DNS proxy in Azure Firewall DNS settings.
9191
2. Optionally, configure your custom DNS server or use the provided default.
92-
3. Configure the Azure Firewall private IP address as a custom DNS address in your virtual network DNS server settings. This setting ensures DNS traffic is directed to Azure Firewall.
92+
3. Configure the Azure Firewall private IP address as a custom DNS address in your virtual network DNS server settings to direct DNS traffic to the Azure Firewall.
93+
94+
> [!NOTE]
95+
> If you choose to use a custom DNS server, select any IP address within the VNET, excluding those in the Azure Firewall subnet.
9396
9497
#### [Portal](#tab/browser)
9598

0 commit comments

Comments
 (0)