We offer five traffic optimization services from failover to advanced load balancing. Use these tools to optimize end-user experiences, increase redundancy, and cut down on resolution times.
Load balancing at the DNS level is a service that distributes your query traffic across multiple endpoints (IP addresses or hostnames). It is also called round robin or load distribution.
Enhanced failover uses real-time monitoring metrics to automatically move traffic to a backup IP address if your primary IP is unavailable.
The most basic of load balancing services is called round robin. Round robin is often compared to a rotor because it returns one endpoint at a time in a cyclical manner.
Let’s say you want to point your domain to three geographically distributed web servers: 220.127.116.11, 18.104.22.168, and 22.214.171.124 with round robin enabled. Each time your domain is queried, it will return the next IP in the list.
The second kind of load balancing is called weighted round robin and allows you to distribute uneven amounts of traffic across endpoints. This is great way to prioritize endpoints with more capacity or if you want to slowly roll out an update to only segments of your users at a time.
In Constellix, you need to configure weighted round robin using record pools. Pools are groups of endpoints that a record can point to. You can choose how many are returned each time the record is queried and specify weights for each endpoint.
But round robin isn’t a perfect system. If one of the IP’s is not responding, the record will continue to serve that IP as it is requested. If any resolving nameservers or users have that endpoint cached, it will continue to request that IP until the cache expires. This defeats the idea of using round robin as a way to add more redundancy.
You could decrease the TTL (Time to Live) for your round robin record, but this will increase your costs overtime since your nameservers will be queried more.
You can integrate monitoring checks with your round robin records. That way, only healthy endpoints are served to users. If an endpoint is detected as down, it will be removed from the rotation. But if it comes back as healthy, it will be included in the next cycle.
You can also use Round Robin with Failover if you want just one endpoint to be returned unless it is down. If it does come back as down, then we will failover the other endpoints which will be returned in a round robin fashion.
In this case, you would create two pools, one with just your primary endpoint. The second pool would contain the endpoints you want to failover to.
Like weighted round robin, latency-based load balancing uses record pools. This type of load balancing ensures that only that fastest responding endpoint(s) in a pool are served to users.
We call this service ITO, Internet Traffic Optimization, because it actually optimizes individual end-user experiences. ITO is configured regionally, so all routing decisions are specific to end-users’ locations.
Failover decisions are informed by real-time metrics gathered from our Sonar monitoring beacon.
As soon as an IP is offline or underperforming, DNS automatically moves your traffic over to your backup IP. Sonar continues to monitor your old IP and will failback your traffic when it becomes available.
There are three setting for enhanced failover. Rankings determine the order the backup IP addresses will be served when the primary IP in unavailable.
|Ranking Mode||Description||How It Works|
|Normal||Always lowest levels||Attempt to keep the IP address to the most preferred system in the list.|
|Off On Any Failover||Move to an active IP||Turn off failover after any failover.|
|One Way||Move to higher levels||Only failover your domains to IPs that are further down the list. For example, IP #1 will failover to #2, and #2 will failover to #3, but it will never go back to #1 unless manually changed.|
Learn how to build your own CDN service with just DNS and a few web servers.Read more
New Video! Learn how to setup DNS Failover in Constellix in just a few minutes.Watch now
Do you have a plan? Don't worry, we have one for you.Read it now!
Learn how in just five minutes! You can even add location-specific rules for a global roll out.Read more