You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/firewall-manager/dns-settings.md
+16-21Lines changed: 16 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,25 +5,17 @@ services: firewall-manager
5
5
author: vhorne
6
6
ms.service: firewall-manager
7
7
ms.topic: how-to
8
-
ms.date: 02/17/2021
8
+
ms.date: 04/06/2023
9
9
ms.author: victorh
10
10
---
11
11
12
12
# Azure Firewall policy DNS settings
13
13
14
-
You can configure a custom DNS server and enable DNS proxy for Azure Firewall policies. You can configure these settings when you deploy the firewall or later from the **DNS settings** page.
14
+
You can configure a custom DNS server and enable DNS proxy for Azure Firewall policies. You can configure these settings when you deploy the firewall or later from the **Settings**, **DNS** page.
15
15
16
16
## DNS servers
17
17
18
-
A DNS server maintains and resolves domain names to IP addresses. By default, Azure Firewall uses Azure DNS for name resolution. The **DNS server** setting lets you configure your own DNS servers for Azure Firewall name resolution. You can configure a single or multiple servers.
19
-
20
-
### Configure custom DNS servers
21
-
22
-
1. Select your firewall policy.
23
-
2. Under **Settings**, select **DNS Settings**.
24
-
3. Under **DNS servers**, you can type or add existing DNS servers that have been previously specified in your Virtual Network.
25
-
4. Select **Save**.
26
-
5. The firewall now directs DNS traffic to the specified DNS server(s) for name resolution.
18
+
A DNS server maintains and resolves domain names to IP addresses. By default, Azure Firewall uses Azure DNS for name resolution. The **DNS servers** setting lets you configure your own DNS servers for Azure Firewall name resolution. You can configure a single or multiple servers.
27
19
28
20
## DNS proxy
29
21
@@ -37,25 +29,28 @@ DNS Proxy configuration requires three steps:
37
29
2. Optionally configure your custom DNS server or use the provided default.
38
30
3. Finally, you must configure the Azure Firewall’s private IP address as a Custom DNS address in your virtual network DNS server settings. This ensures DNS traffic is directed to Azure Firewall.
39
31
40
-
### Configure DNS proxy
32
+
## Configure firewall policy DNS
33
+
34
+
1. Select your firewall policy.
35
+
2. Under **Settings**, select **DNS**.
36
+
1. Select **Enabled** to enable DNS settings for this policy.
37
+
1. Under **DNS servers**, you can accept the **Default (Azure provided)** setting, or select **Custom** to add custom DNS servers you'll configure for your virtual network.
38
+
1. Under **DNS Proxy**, select **Enabled** to enable DNS Proxy if you configured a customer DNS server.
39
+
1. Select **Apply**.
41
40
42
-
To configure DNS proxy, you must configure your virtual network DNS servers setting to use the firewall private IP address. Then, enable DNS Proxy in Azure Firewall policy **DNS settings**.
43
41
44
-
#### Configure virtual network DNS servers
42
+
## Configure virtual network
43
+
44
+
To configure DNS proxy, you must also configure your virtual network DNS servers setting to use the firewall private IP address.
45
+
46
+
### Configure virtual network DNS servers
45
47
46
48
1. Select the virtual network where the DNS traffic will be routed through the Azure Firewall.
47
49
2. Under **Settings**, select **DNS servers**.
48
50
3. Select **Custom** under **DNS servers**.
49
51
4. Enter the firewall’s private IP address.
50
52
5. Select **Save**.
51
53
52
-
#### Enable DNS proxy
53
-
54
-
1. Select your Azure Firewall policy.
55
-
2. Under **Settings**, select **DNS settings**.
56
-
3. By default, **DNS Proxy** is disabled. When enabled, the firewall listens on port 53 and forwards DNS requests to the configured DNS servers.
57
-
4. Review the **DNS servers** configuration to make sure that the settings are appropriate for your environment.
0 commit comments