Use dns insurance policy for geo-location based traffic management with primary servers

Geo-Location Based Traffic Management Example
Geo-Location Based Traffic Management Example
The way the DNS name resolution process works
- What is Policy?

With new DNS policies, you may create a DNS policy that enables the DNS server to reply to a customer query requesting the Ip of the Server. Cases of the net server may be situated in different datacenters at different physical locations. DNS can measure the client and Server locations, then react to the customer request by supplying the customer having a Server Ip for any Server that’s physically located nearer to the customer.

You should use the next DNS policy parameters to manage the DNS server responses to queries from DNS clients.

Client Subnet. Name of the predefined client subnet. Accustomed to verify the subnet that the query was sent.
Transport Protocol. Transport protocol utilized in the query. Possible records are UDP and TCP.
Ip Address. Network protocol utilized in the query. Possible records are IPv4 and IPv6.
Server Interface Ip. Ip from the network interface from the DNS server which received the DNS request.
FQDN. The Properly Accredited Website Name (FQDN) from the record within the query, with the potential of utilizing a wild card.
Query Type. Kind of record being queried (A, SRV, TXT, etc.).
Time. Time the totally received.

You are able to combine the next criteria having a logical operator (AND/OR) to formulate policy expressions. When these expressions match, the coverage is likely to perform among the following actions.

Ignore. The DNS server quietly drops the query.
Deny. The DNS server responds that question having a failure response.
Allow. The DNS server responds back with traffic managed response.

Geo-Location Based Traffic Management Example

Following is a good example of the best way to use DNS policy to attain traffic redirection based on the location from the client that performs a DNS query.

This situation uses two imaginary companies – Contoso Cloud Services, which supplies web and domain hosting solutions and Woodgrove Food Services, which supplies food delivery services in multiple metropolitan areas around the world, and with a Site named woodgrove.com.

Contoso Cloud Services has two datacenters, one out of the U.S. and the other in Europe. The Ecu datacenter hosts a food ordering portal for woodgrove.com.

To make sure that woodgrove.com customers obtain a responsive experience from their site, Woodgrove wants European clients forwarded to the ecu datacenter and American clients forwarded to the U.S. datacenter. Customers located elsewhere on the planet could be forwarded to either from the datacenters.

You should use the next DNS policy parameters to manage the DNS server responses to queries from DNS clients.

Client Subnet. Name of the predefined client subnet. Accustomed to verify the subnet that the query was sent.
Transport Protocol. Transport protocol utilized in the query. Possible records are UDP and TCP.
Ip Address. Network protocol utilized in the query. Possible records are IPv4 and IPv6.
Server Interface Ip. Ip from the network interface from the DNS server which received the DNS request.
FQDN. The Properly Accredited Website Name (FQDN) from the record within the query, with the potential of utilizing a wild card.
Query Type. Kind of record being queried (A, SRV, TXT, etc.).
Time. Time the totally received.

Ignore. The DNS server quietly drops the query.
Deny. The DNS server responds that question having a failure response.
Allow. The DNS server responds back with traffic managed response.

Geo-Location Based Traffic Management Example

Following is a good example of the best way to use DNS policy to attain traffic redirection based on the location from the client that performs a DNS query.

Contoso Cloud Services has two datacenters, one out of the U.S. and the other in Europe. The Ecu datacenter hosts a food ordering portal for woodgrove.com.

The next illustration depicts this.

The way the DNS name resolution process works

Throughout the name resolution process, the consumer tries to connect with www.woodgrove.com. This produces a DNS name resolution ask that is distributed towards the DNS server that’s configured within the Network Connection qualities around the user’s computer. Typically, this is actually the DNS server supplied by the neighborhood ISP serving as a caching resolver, and it is referred because the LDNS.

When the DNS name isn’t present from our cache of LDNS, the LDNS server forwards the query towards the DNS server that’s authoritative for woodgrove.com. The authoritative DNS server responds using the requested record (www.woodgrove.com) towards the LDNS server, which caches the record in your area before delivering it towards the user’s computer.

Because Contoso Cloud Services uses DNS Server policies, the authoritative DNS server that hosts contoso.com is configured to come back geo-location based traffic managed responses. This results in direction of European Clients towards the European datacenter and also the direction of yankee Clients towards the U.S. datacenter, as portrayed within the illustration.

Within this scenario, the authoritative DNS server usually sees the name resolution request from the LDNS server and, hardly ever, in the user’s computer. Due to this, the origin Ip within the name resolution request as seen through the authoritative DNS server is the LDNS server and never those of anyone’s computer. However, while using Ip from the LDNS server whenever you configure geo-location based query responses supplies a fair estimate from the geo-location from the user, since the user is querying the DNS server of his local ISP.

Resourse: https://docs.microsoft.com/en-us/home windows-server/networking/dns/deploy/