Scenario: You want to use GSLB.me as the authoritative DNS for your domain “mydomain.com“. mydomain.com can be a new domain you’re about to register, or it can be an already existing domain. Once done, you want to run “www.mydomain.com” from your webserver which sits on an Internet connection with a dynamic IP. How to configure it: Log on to GSLB.me using your credentials or register if you still don’t have an account Create a new “customer zone”: this is the domain name you want to handle using GSLB.me as your authoritative DNS. You can create a customer zone for a domain name you already own (in this case… Read More
Continue ReadingDynamic CDN Offload
Scenario: You have one or more datacenters running your application Your application is mapped on a well-defined hostname (ie. www.myapplication.com) You are using a third-party CDN (Content Delivery Network) solution to offload your traffic to your content provider You need your clients traffic to be sent to your datacenter(s) as long as it/they is/are available If one or more datacenters are not available you want your traffic to be dynamically and automatically offloaded to your CDN provider Solution: Use GSLB.me with your load balancing algorithm of choice and enable CDN offload Define one geohost that will be pointed by www.myapplication.com via a DNS CNAME record Create your target… 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
Active-Standby between two datacenters
Scenario: You have at least two datacenters running the same application. The primary datacenter is always active. In case of failure/disaster the secondary/backup datacenter must kick in taking control and providing access to your application (disaster recovery) Your application is mapped on a well-defined hostname (ie. www.myapplication.com) On the primary datacenter www.myapplication.com is running on IP a.b.c.d. One the secondary/backup datacenter www.myapplication.com is running on IP x.y.z.t You need your clients traffic to be sent to the primary datacenter and, only in case of unavailability, be transparently sent to the secondary/backup datacenter Solution: Use GSLB.me in priority balancing mode Define one geohost that will be pointed by www.myapplication.com… Read More
Continue ReadingLoad balancing between two datacenters
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 equally split between the two datacenters Solution: Use GSLB.me in round robin 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 server that… Read More
Continue ReadingUsing aliases for datacenter dependencies
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 to monitor your application health using IP addresses that are different from a.b.c.d and x.y.z.t Solution: Use GSLB.me in round robin 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 and define their aliases. Targets will be healthcheck-monitored using their IP addresses but… Read More
Continue Reading