Skip to main content

Global Server Load Balancing

The most important reason for the use of GSLB is to provide high availability by hosting websites more than one geographic location. With GSLB technology, incoming requests are redirected to servers in different locations on the internet for load balancing. In addition, when service on a site was interrupted by a broken internet connection, power failure, local load balance device(SLB) failure or DoS attack (Denial of Service), GSLB device becomes aware of  the situation, redirects incoming requests to another site and prevent interruption of the service. GSLB makes necessary routing processes by responding to DNS requests.

DNS Resolution
DNS resolution process in a GSLB infrastructure takes place in the following order.
Suppose that there is a site in Ankara which has virtual IP(VIP) address1.1.1.1 and there is a site in Istanbul which has VIP address Our GSLB device will act as the authoritative DNS server and decide where to redirect incoming requests.
1. Stub resolver (application running on the client computer) makes a DNS request from which is defined on itself. Requests made from the clients are called recursive queries. Client computer will not try any other request because DNS server is responsible for this task.
2. DNS server makes queries on the root DNS servers on behalf of the client and reaches GSLB device acting as Authoritative DNS server.
3. GSLB device contacts with local SLB devices in each site and receives information about local SLB's status like number of connections, response time etc.
4. Local SLB devices can make dynamic performance measurements like Round trip time RTT, topgraphical footrace, BGP hop count if desired.
5. GSLB device decides to route requests to which site using information obtained from the third and fourth steps. In this example response can be or This response is sent to DNS server which is defined on the client computer.
6. DNS server sends IP information to the stub resolver (application running on the client). So the client begins communicating most available site on the internet.


Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

PowerShell Script for Switching Between Multiple Windows

Windows PowerShell has strong capabilities. I have a separate computer with a big lcd screen in which I am watching regularly some web based monitoring applications. So I need those application windows switch between on a timely basis. Then I wrote this simple powershell script to achieve this. You can change it according to your needs.