DNS Load Balancing
Balance the load across multiple servers for outstanding speed and reliability
CloudfloorDNS Load Balancing gives you the leg up when it comes to handling incoming DNS requests with ease. Whether you are running a global marketing campaign or your latest video just went viral, you need the DNS capacity to handle large bursts of traffic to your website or other mission critical applications.
Our DNS Load Balancing services are included free with all of our DNS packages, allowing you to send requests to multiple IP’s/Servers instead of just one. Use the Aux record on the load balancing records to add priority to some servers instead of others. When tied into our Netmon server monitoring features, you can add and remove IP’s/Servers from the load balancing pool if they are slow or degraded. Add them back when they speed up.
Our GEO DNS Load Balancing can segregate your DNS traffic by country or distance and apply to all of our load balancing features. Fine tune your load and direct your traffic with pinpoint accuracy. Our DNS Load Balancing can help you scale and grow your business without breaking your budget.
- Spread visitors across multiple A records
- Load Balance traffic using weighted distribution
- DNS Failover & Load Balancing work together
- Smart Load Balancing – If a server fails, remove from LB pool
- GEO Load Balancing can balance based on Distance, closest Server
Our Weighted Load Balancing services utilize the aux record to set priority on the round robin pool of load balanced IP’s. You can set the ratio that each IP gets served, allowing you to provide the greater amount of traffic to the fastest servers in the pool. Need to change the ratio? It’s as simple as using the Web-based management panel to change the Aux values or IP’s. The Weighted Load Balancing service also works with our DNS Failover and Netmon services, allowing you to remove and add IP’s into your server pool automatically based on the servers ability to respond.
Round Robin Load Balancing simply spreads all the hits over all of your servers, evenly alternating between each server. A simple and effective way to avoid traffic spikes taking down a single server. You setup multiple A records in the DNS for the same subdomain such as WWW and the server will return all the A records while evenly distributing the records handed back to the client. Also works with our DNS Failover to remove any server from the pool if it’s slow, degraded or not responding.
Our DNS Alias record gives you CNAME at the Root/Apex capabilities. Due to today’s complex cloud naming structures, it’s necessary to have a service that is compliant with these cloud naming structures. The “Alias Record” in our DNS allows users to add a CNAME to any record group and have it treated by the resolving client as an A Record, saving users time and money.
Cloud services such as Google, Amazon EC2 and Elastic Load Balancers (ELB) generally make it easy to integrate DNS, as most supply a CNAME record to which users point their DNS host names. However, CNAMEs come with many limitations. For example, users cannot normally point a naked domain or root record to a CNAME. Additionally, CNAMEs cannot be present with other record types of the same host name, so if users wish to use load-balancing features with groups of A Records and CNAMEs in this instance, they are unable to do so. These limitations not only add unnecessary complexity but also require valuable time to avoid.
CNAMEs are used as low maintenance DNS setups. If a service provider’s IP address changes, the settings would not have to change (as opposed to A Records, which would have to be changed to reflect the new IP). Additionally, ELBs often change their IP addresses in response to load. This can even be done without notice to the users, therefore making the CNAME the only reasonable solution for these technologies.
Our Performance based Load Balancing services utilize our Netmon global server monitoring service along with our DNS Load Balancing. You set a Netmon test up for each server in the Load Balancing Pool, and within that test you can then set a response time (in ms) that you expect for performance. When the performance drops below the set threshold and becomes slow or unresponsive, the Load Balancing service can then remove that particular Server/IP from the pool. When the server response time returns to an acceptable level, it can automatically add that back into the pool
Our Distance-based Load Balancing services utilize our GEO DNS services along with our DNS Load Balancing. Our intelligent GEO DNS coupled with our Load Balancing determines the distance between the user and the load balanced pool of IP’s and will hand back the closest server automatically. Closest doesn’t always mean fastest, so you can also interact with our Netmon server monitoring and also manipulate the pool to remove slow or unresponsive servers from the pool. The CloudfloorDNS systems are fully compliant with EDNS0 or client-IP which allows our GEO DNS to precisely pinpoint the client IP at the browser level.