Query Resolution Policies (Geo-location Traffic Management)

[Philip Luke]

It may not be specific to QRP but we have the following need. As an overview, there are around 100 sites each with a local Domain Controller. We are implementing a split core services design to separate the likes of Exchange/SharePoint/IIS applications across two Datacentres. Each Datacentre will contain the necessary fabric to provide these services. All 100 sites are part of the same Domain. The internal and external namespace is the same. So, to the requirement. We need to be able to direct around half of these sites to one Datacentre for services published with specific FQDN's, and the other half of the sites to the other Datacentre. Im investigating the option of using the Server 2016 Query Resolution Policies to define the parameters to carry this out, but in doing this Im hitting some hurdles. The main issues I have with this is the fact that these would need to be applied to EACH DNS server which is responsible for the local sites users. In the event that one of the Datacentres should fail then the need to update these policies to return a different IP address per A record seems overly complex and vast. I cant see this is any different with Server 2019 either. In an ideal world I would like it so that the service IP address ISNT actually published as an A record in the root zone, but is actually added as a Zone Scope, and that all 'site' DNS servers are somehow configured to recuse a query for specific A records to a couple of CORE DNS Servers, and on these the Query Resolution Policies are defined. This way none of the regional DNS servers ever need reconfiguration, but only the CORE DNS servers would need the IP addresses for the A records to be updated.

So, this is more of a cry for help to see if anyone has been able to ustilise the new features in Server 2016 to achieve this?

Thanks for any help.


Phil

Continue reading...