Dynamic Path Selection based on Domain Names
Domain names can be added to a policy‐based routing as destinations. In a multi-WAN network, network administrators might have the need to set FQDN as a destination in a routing policy in order to route traffic destined for organizations like Dropbox or Youtube via specific path(s). This will make the works of policy configuration much easier as no need to find out and configure the IP addresses for destinations.

When an outbound web request comes up, it receives destination IP through a DNS lookup. The request is then sent out to the internet. The network gateway (or firewall) add an entry in the IP routing rules. Next outbound web requests destined for the same destination will be sent out via the same path based on the routing rule previously created in case it receives same destination IP via DNS lookup or the domain name has only one IP for DNS resolution. However, the organizations such as Youtube or Google usually have so many IP addresses for their domain names, and their DNS servers resolve their domain names into different IP addresses randomly and frequently.

>  Policy Based Routing with Domain Names

Policy Based Routing with Domain Names

Those issues can perhaps be solved by adding all IP addresses of a FQDN or a domain name to the routing rules. Adding those hundreds of IP addresses to policy rules can be time-consuming, error-prone and doesn't guarantee the applications get routed correctly because organizations might still have the need to add or delete IP addresses based on business intent. On top of that, network administrators will probably have the need to deal with many more similarly large organizations.

As a solution to the issue, whenever a outbound request arises, Q-Balancer has the ability to dynamically learn the IP resolved via DNS lookup and add a IP routing rule for the destination IP in real-time. This enables business to simplify the works of policy configurations, especially for the organizations with many IP addresses for their domain names, by setting policy routing rules based on domain names rather than lots of IP addresses. As policy based routing rules can be applied with domain names, link load balancing, link failover, filtering, and QoS can also work with domain name in a single policy routing rule. Other than application based routing, this optionally provides a hybrid WAN network with the ability to efficiently and flexibly ensure the connectivity for critical applications.

Top Benefits

  • Improved application performance

  • Greater business productivity

  • Better network utilization

  • Granular path control over hybrid-WAN network