DNS Wildcard Beaconing for Global Traffic Load Balancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Global load balancing systems face inaccuracies in routing decisions due to insufficient data, as they rely on the location and congestion of local DNS resolvers rather than the actual client, leading to incorrect proximity mapping and inadequate load balancing.
Innovation Solution
Implementing DNS wildcard beaconing to determine the number and location of clients behind local DNS resolvers, using globally unique wildcard hostnames to gather data on client IP addresses and load, which is then aggregated and used for more accurate routing decisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If GLB uses LDNS resolver location for routing decisions, then routing decisions can be made with available data, but client proximity mapping becomes inaccurate
Solution Approach 1:
The patent introduces DNS wildcard beaconing as an intermediary mechanism. Instead of directly using LDNS resolver location, the system deploys wildcard DNS records that act as mediators to collect actual client connection data. These beacons capture client IP addresses and connection information, which then feed into the proximity mapping system, resolving the inaccuracy between LDNS location and actual client location.
2Adaptability or versatility
If GLB relies on LDNS resolver data, then the system can function with current infrastructure, but load balancing accuracy deteriorates due to caching
Solution Approach 1:
The patent implements a feedback mechanism through DNS wildcard beaconing. The system continuously collects actual client connection data via wildcard DNS records deployed across data centers. This feedback loop provides real-time information about actual client load and connection patterns, allowing the GLB system to adjust routing decisions based on observed data rather than relying solely on cached LDNS information.
3Measurement precision
If DNS wildcard beaconing is implemented to gather client data, then client proximity and load determination improves, but system complexity increases
Solution Approach 1:
The patent leverages the existing DNS infrastructure for multi-functional purposes. The wildcard DNS records serve multiple functions: they act as beacons for collecting client data, they provide actual client proximity information, and they enable load measurement. By making the DNS system universal and multi-functional, the patent avoids adding separate complex infrastructure while achieving precise client determination.
Data Source
AI summary
Techniques are described to determine clients residing behind LDNS resolvers. Web beacons instruct clients to retrieve zero-content images at unique hostnames. A request to the hostname is made by a client to an LDNS resolver. The LDNS sends the request to an authoritative server/beacon resolver for the hostname. The beacon resolver records the hostname with the LDNS resolver's IP address and responds with an IP address of a beacon collection server that is forwarded to the client by the LDNS. The client sends a request containing the unique hostname to the beacon collection server. The beacon collection server records the IP address of the client and the hostname. An aggregation server collects data from the beacon resolver and the beacon collection server. Using the hostnames as keys, IP addresses of clients are mapped to IP addresses of LDNS resolvers. Mapped data is exported to load balancing servers to determine routing.