Questions tagged [dns-policies]

DNS Policies are a new feature in Windows Server 2016 DNS which allow for DNS requests to behave differently based on various criteria. This allows for scenarios such as Split Brain DNS, Application Load Balancing, Geo-Location Based Traffic Management, Filtering, Forensics, and Time of day based redirection.

DNS Policies can support the following scenarios (From DNS Policies Overview):

  • Application Load Balancing - When you have deployed multiple instances of an application at different locations, you can use DNS policy to balance the traffic load between the different application instances, dynamically allocating the traffic load for the application.
  • Geo-Location Based Traffic Management - You can use DNS Policy to allow primary and secondary DNS servers to respond to DNS client queries based on the geographical location of both the client and the resource to which the client is attempting to connect, providing the client with the IP address of the closest resource.
  • Split Brain DNS - With split-brain DNS, DNS records are split into different Zone Scopes on the same DNS server, and DNS clients receive a response based on whether the clients are internal or external clients. You can configure split-brain DNS for Active Directory integrated zones or for zones on standalone DNS servers.
  • Filtering - You can configure DNS policy to create query filters that are based on criteria that you supply. Query filters in DNS policy allow you to configure the DNS server to respond in a custom manner based on the DNS query and DNS client that sends the DNS query. Forensics. You can use DNS policy to redirect malicious DNS clients to a non-existent IP address instead of directing them to the computer they are trying to reach.
  • Time of day based redirection - You can use DNS policy to distribute application traffic across different geographically distributed instances of an application by using DNS policies that are based on the time of day.
6 questions
10
votes
1 answer

Are Windows 2016 DNS Policies / Split DNS possible on AD integrated zones with older DCs?

Windows Server 2016 supports DNS Policies, which provide support for split-brain DNS among other scenarios: You can configure DNS policies to specify how a DNS server responds to DNS queries. DNS responses can be based on client IP address …
6
votes
2 answers

DNS Policies are not properly resolving CNAMEs in Zone Scopes if the Query Resolution Policy includes the NE operator for Client Subnets

I'm fairly sure I've uncovered a bug, but I'm trying to make sense of it and maybe get a sanity check. Scenario A policy where if the request is looking for a specific record AND the client IP is not in a particular subnet, the policy matches and…
3
votes
1 answer

Can I use server 2016 DNS policies to return alternative IPs but only for some records in a domain?

I need to provide a kind of DNS split-brain scenario with two key goals: "special" DNS clients (based on their subnet) must resolve certain A records in one domain to different IP addresses than the rest of clients all other records in the same…
3
votes
2 answers

What are the minimum permissions needed to manage DNS Policies in Server 2016?

I'm implementing DNS Policies, writing PowerShell scripts for certain tasks, and of course I don't want to schedule these tasks as domain admins; I want to use a least-privileged service account. The thing is, I can't seem to figure out what's…
1
vote
0 answers

What is the difference between geo DNS policy and local subnet prioritization (netmask ordering)?

Starting with Windows Server 2016, MS DNS supports DNS Policies with "Geo-Location Based Traffic Management". But with older Windows Server versions I could configure local subnet prioritization (aka netmask ordering) to implement a similar…
bahrep
  • 664
  • 1
  • 9
  • 27
0
votes
1 answer

Windows DNS server recursive resolving issue with dns policy

I am using dns policy with windows dns server. In my scenario I want to allow recursive queries in local subnet (192.168.1.0/24) and deny for others. It works great until querying for a domain (example.com) from local subnet. After resolving from…
Baran
  • 149
  • 2
  • 7