Contents


Network connectivity is a key differentiator for GoGrid. Services that we provide to enhance our customer's experience is Geographic Load Balancing and Failover. These are separate products that customers can add on to our Managed DNS.


Key Features

  • Instant worldwide network
  • No long-term commitment
  • Reliable performance
  • Fully featured DNS
  • Geographic Load Balancing
  • Failover
  • Fully supported

Data Center Availability

Geographic Load Balancing (GLB) is currently available in US-West-1, US-East-1, and EU-West-1.

Ordering Geographic Load Balancing and Failover

Contact Sales to order this service. There are three different services you can request:

Managed DNS is required if you want Geographic Load Balancing and Geographic Failover. Full pricing for this service can be found here.

Geographic Load Balancing

Use this service if you want reduce latency to your customers in different geographic regions. For example, if you have customers in Europe they'll have less latency if they are routed to a web server in Europe rather than a server in the US. You can use GLB to enable this capability.

Prerequisites

You'll need to have a domain that you own to use this service. Because this is a DNS-based service, a domain is required. Configure this domain with GoGrid's DNS. You'll also need infrastructure in the locations that you want to target. To obtain the most geographic reach, you'll want cloud servers that can serve up your website from all GoGrid data centers (US-West-1, US-East-1, and EU-West-1). Although this isn't required, you'll have the best performance if you distribute your website broadly, especially if you have a highly distributed customer base.

Standard Configuration

For each domain, GoGrid will create a GeoLocation set. This will determine the geographic boundaries of the service. Each GeoLocation will have three views, which are standardized so that they are consistent for every customer. The views are:

  • West US - these are composed of the Mid-West and Western US states
  • East US - these are composed of the Northeast and Southern US states
  • Europe - these are composed of the Eastern, Northern, Southern, and Western regions


There is also a default view that is not part of the GeoLocation set. This is the record to which the domain defaults.


When requesting this service you'll need to have:

  • The domain you want to configure
  • A public IP Address (or even individual domain name) for each view
  • The public IP Address for the default view (it can be one designated for another view)

How Geographic Load Balancing Works

Once configured, GLB will detect the geographic location of a client (an end user browsing your website) and then route them to the nearest server.

As an example, if you have a server in each of our data centers, you can assign each to one of the views. The IPs here are just examples--you'll have to use the IPs associated with your web servers.

  • West US - routes to 240.30.248.145
  • East US - routes to 143.168.230.5
  • Europe - routes to 50.145.33.17


So if this client is in Spain, GLB will detect their location and then route them to 50.145.33.17 because the Europe view states that anyone detected in Europe should go to this IP address. If the client is in a location that is not defined by the views, then they'll be sent to a server defined in the default view.


64-warn.gif
NOTE: The IP address doesn't have to be a server. You can also use a Dynamic Load Balancer. This is a powerful combination because it will offer the capabilities of local load balancing and geographic load balancing.

Geographic Failover

Use this service if you want to ensure that your website is always available. For each record of your domain, you can define a failover server. If the primary server should become non-responsive, the secondary server will automatically take over and continue to serve out content. The secondary server doesn't have to be from the same data center.

Standard Configuration

For each record, Failover will need to be configured. Failover works by monitoring the health of the servers. If the server should fail a health check, then Failover will be initiated and the secondary server will take over.

  • Support will receive the alerts and manage Failover for you
  • You can set multiple failover servers for each record
  • You can select either an HTTP or Ping health checker
    • The health checker will run every 5 minutes
    • HTTP will only check for the root URI
    • Ping will tolerate 0% packet loss before declaring a failure

How Geographic Failover Works

Once configured, Failover will run against the configured records. If the primary server should fail a health check, an alert will be sent to Support and the secondary server will take over. Once the primary server has recovered, Support will contact you to verify that you want to fail back to the primary server.

As an example, if you have multiple servers in one of our data centers, you can assign one as a secondary server (assuming that it is a clone of the primary server).

  • West US - routes to 240.30.248.145
    • Failover configured to 240.30.248.146


In this example, if 240.30.248.145 fails, then 240.30.248.146 will take over and serve up content to your domain. Failover is not required for Geographic Load Balancing, but they are often used in conjunction. You also don't need to use a server in the same data center; you can configure a secondary server if you want to protect against data center failure.

Geographic Failover with Geographic Load Balancing

When you setup Geographic Load Balancing, you are assigning servers to different views based on geographic location. Failover is not a domain level configuration so you'll need to configure Failover for each server in a view if you want each server to have the ability to failover. This means that for one domain with three views (and three severs behind those views), you'll need to configure Failover for each one individually. Each of these count as one Failover record.

Getting Help

See our Support page for information on contacting GoGrid for any questions or issues that arise.

Frequently asked Questions

Can I configure Geographic Load Balancing from the management console?

No. This is currently a service managed by GoGrid.


Can I configured Geographic Load Balancing through an API?

Not at this time.


What is the difference between Geographic Load Balancing and Dynamic Load Balancing?

The Dynamic Load Balancers (DLB) are designed to be local load balancers. They are designed to route traffic based on a specific algorithm to real servers that are usually in the same data center as the load balancer. Geographic Load Balancing detects the location of the client and routes them to the nearest web server. This operates outside the data center but it also doesn't have the same granular controls of the DLB. It's possible to combine the two by using the DLB VIP as the A record for your views.


How do I make changes to my Geographic Load Balancing or Failover configuration?

Please contact Support.


Can I request GLB without using DNS on GoGrid?

GLB is a DNS-based service, so you'll need to use GoGrid DNS in conjunction with GLB.


I have a customer who is consistently routed to a server in US-West-1 when I know that they are in Northeast state. What is happening?

Currently, GLB detects the location of the recursive server the client is using. It's possible that client is at the border of one state and the recursive server is located on a bordering state that is part of the West US view. This is a known issue with the back-end network.


What if I have customers who are in locations that are not defined in the default GeoLocation set views?

Locations that aren't defined in the views will be routed to the server defined in the default view.
Personal tools