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 functionality (make clients in different subnets contact a resource in the same subnet using the same server name).
So my question is how geo DNS policies that were added in Windows Server 2016 are different from local subnet prioritization?
0 Answers