Scenario: You have several servers around the world publishing a website or an application that is accessed by users coming from different countries and geographies. You want to be able to decide which server(s) users will reach based on their country/countries of origin, and you want to handle “fallback” scenarios in case one or more servers are not available. GSLB.me georouting allows the creation of an unrestricted number of “routing rules” to achieve flexible, granular and precise DNS balancing and traffic distribution. Georouting rules can be based on: country of origin of the requesting DNS client region of origin of the requesting DNS client ASN (Autonomous System Number) of origin… Read More
Continue ReadingGeographical Proximity
Scenario: You have at least two datacenters running the same application and both datacenters are simultaneously active (business continuity) Your application is mapped on a well-defined hostname (ie. www.myapplication.com) On the first datacenter www.myapplication.com is running on IP a.b.c.d. One the second datacenter www.myapplication.com is running on IP x.y.z.t You need your clients traffic to be sent to the geographically closest datacenter through geographical proximity Solution: Use GSLB.me in geographical balancing mode Define one geohost that will be pointed by www.myapplication.com via a DNS CNAME record Create two targets, one for each datacenter Assign the relevant checks to each target Configure the CNAME record on the primary DNS… Read More
Continue Reading