In a typical DNS deployment, a DNS server hosts and serves data for the domain(s); when an incoming DNS query for, e.g. web server appears, DNS server then replies it with IP resolved for the web server. This mechanism is designed for translating domain name into IP address, while it does not check if there are any network outages or congestion when replying. In case a link failure occurs, DNS server might resolve the web server to the IP addresses that are associated with the failed link. Thus, the incoming request would not be able to access the web server in this case.
Problems to be Solved:
> Hosted service disruption during planned network downtime.
> Hosted services unavailable to incoming requests due to either WAN outages or congestion.
> Changing network status and conditions
> Bandwidth efficiency for uplinks
Solution: Inbound Failover and Load Balancing
> Deploying Q-Balancer device and add additional WAN links.
> Automatically directing incoming requests to the remaining active links in case the primary WAN link becomes unavailable.
> Effectively distributing connection requests to all active link(s) or directing them to best-performing link(s).
> WAN scalability.
Inbound Load Balancing
