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/dns/dns-security-policy.md
+21-29Lines changed: 21 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,45 +21,37 @@ This article provides an overview of DNS security policy. Also see the following
21
21
22
22
## What DNS security policy?
23
23
24
-
DNS security policy offers the ability to filter DNS queries at the virtual network (VNet) level. You can allow, alert, or block name resolution of known or malicious domains and gain insight into your DNS traffic. Detailed DNS logs can be sent to a storage account, log analytics workspace, or event hubs.
24
+
DNS security policy offers the ability to filter and log DNS queries at the virtual network (VNet) level and view detailed DNS logs. Think of it like a DNS firewall for your cloud resources. You can allow, alert, or block name resolution of known or malicious domains. The logging capability enables you to gain detailed insight into your DNS traffic. DNS logs can be sent to a storage account, log analytics workspace, or event hubs.
25
25
26
26
A DNS security policy has the following associated elements and properties:
27
-
- Location: A security policy can only apply to VNets in the same region.
28
-
- DNS traffic rules: Rules that allow, block, or alert based on priority and domain lists. Rules can be enabled or disabled.
29
-
- Virtual network links: You can link one security policy per VNet. A security policy can be associated to multiple VNets.
30
-
- DNS domain lists: Location-based lists of DNS domains.
27
+
-**Location**: A security policy can only apply to VNets in the same region.
28
+
-**DNS traffic rules**: Rules that allow, block, or alert based on priority and domain lists. Rules can be enabled or disabled.
29
+
-**Virtual network links**: You can link one security policy per VNet. A security policy can be associated to multiple VNets.
30
+
-**DNS domain lists**: Location-based lists of DNS domains.
31
31
32
-
You can create a security policy with diagnostics sent to a storage account (your DNS query logs are visible there).
33
-
You can create a security policy via Portal and have instructions on how to create and manage the security policy, plus setting the diagnostic options to send the DNS query details to a log analytics workspace.
32
+
DNS Security Policy can be configured using Azure PowerShell or the Azure portal.
34
33
35
-
You should now be able to log your DNS traffic to one or multiple locations (storage account, log analytics workspace). DNS security policy should log all DNS queries initiated from your VNET. You can try following two scenarios for your testing.
36
-
1. Create an Azure DNS private zone and link it to the virtual network where you have deployed the resolver. Next create some DNS records in the DNS zone and try to resolve these records from on-prem machines and Azure VMs. You can use nslookup command or Resolve-DnsName PowerShell command to lookup specific DNS records. You can also try variation of this scenario by creating different types of DNS records like AAAA, TXT, CNAME etc.
34
+
### Location
37
35
38
-
## FAQ
36
+
You can create any number of security policies in the same region. In the following example, two polices are created in each of two different regions (East US and Central US). Keep in mind that the policy:VNet relationship is 1:N. When you associate a VNet with a security policy (via virtual network links), that VNet can't then be associated with another security policy. However, a single DNS security policy can be associated with multiple VNets in the same region.
39
37
40
-
What is a DNS security policy?
41
-
- DNS security policy is an object that contains monitoring settings for DNS query logging which can be applied to one or more Virtual Networks. This is a 1:N relationship.
38
+

42
39
43
-
What is a Virtual Network Link?
44
-
- Virtual Network links enable the policy on Virtual Networks which are linked to a DNS security policy. This is a 1:1 relationship.
40
+
### DNS traffic rules
41
+
42
+
### Virtual network links
43
+
44
+
### DNS domain lists
45
45
46
-
Virtual network restrictions: The following restrictions are held with respect to virtual networks:
47
-
- DNS security policy can reference a virtual network in the same region as the DNS security policy only.
48
-
- DNS security policy restrictions: DNS security policy has the following limitations:
49
-
- DNS security policy cannot be deleted unless the virtual network links under it are deleted.
50
46
51
-
What is a Domain List?
52
-
- A domain list is essentially a collection of domain names grouped together for a specific purpose. In the context of DNS security policy, a domain list can be used for DNS filtering.
53
-
- For example, in DNS security policies, a domain list can be used to specify which domains should be allowed or blocked. This can help in managing and securing network traffic by filtering out unwanted or harmful domains. Additionally, domain lists can be linked to multiple rules for DNS filtering, allowing for more granular control over DNS traffic.
47
+
## Requirements and restrictions
48
+
49
+
Virtual network restrictions:
50
+
- DNS security policies can only be applied to virtual networks in the same region as the DNS security policy.
51
+
- DNS security policy cannot be deleted unless the virtual network links under it are deleted.
54
52
55
-
What is a DNS traffic rule?
56
-
- A DNS traffic rule is a set of predefined criteria or policies used to manage and control the flow of DNS queries and responses within a virtual network. These rules can be applied to virtual networks to which a DNS security policy is linked to and may contain 1 or Domain List.
57
53
58
-
Security Policies: These rules can help protect against DNS-based attacks by allowing or blocking specific domain names, helping to filter out unwanted or harmful domains and enhance network security.
59
54
60
-
## Next steps
55
+
## Related content
61
56
62
-
- Learn how to [sign a DNS zone with DNSSEC](dnssec-how-to.md).
63
-
- Learn how to [unsign a DNS zone](dnssec-unsign.md).
64
-
- Learn how to [host the reverse lookup zone for your ISP-assigned IP range in Azure DNS](dns-reverse-dns-for-azure-services.md).
65
-
- Learn how to [manage reverse DNS records for your Azure services](dns-reverse-dns-for-azure-services.md).
57
+
-[How to filter and view DNS traffic (Preview)](dns-traffic-log-how-to.md).
0 commit comments