Client DNS Caching for Geographic Load Balancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Default DNS lookup servers often result in suboptimal geographic balancing and load balancing when resolving host names to IP addresses, leading to inefficient routing of requests to content servers.
Innovation Solution
A client computing device stores and uses a local DNS lookup table to cache IP address sets for frequently accessed content servers, allowing it to bypass the default DNS lookup server and route requests directly to optimized servers based on geographic location and load balancing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a default DNS lookup server is used for resolving host names to IP addresses, then the DNS resolution service is provided broadly to cover multiple client computing devices, but the geographic balancing and load balancing become suboptimal
Solution Approach 1:
The patent implements a distributed DNS resolution system where each client computing device maintains its own copy of the DNS resolution data (IP address set) locally in memory. Instead of relying on a single centralized DNS server, each client independently stores and uses the resolved IP addresses for future requests, effectively copying the DNS resolution functionality to the client side. This resolves the contradiction by enabling broad coverage while improving local geographic balancing efficiency.
2Adaptability or versatility
If a default DNS lookup server is used for resolving host names to IP addresses, then the DNS resolution service is provided broadly to cover multiple client computing devices, but the load balancing becomes suboptimal
Solution Approach 1:
Each client computing device copies the DNS resolution results locally, creating an independent load balancing decision mechanism at the client side. This distributes the load balancing responsibility across multiple clients rather than relying on a single centralized DNS server, thereby improving overall load balancing efficiency while maintaining broad service coverage.
Solution Approach 2:
The patent extracts the DNS resolution functionality from the centralized DNS server and places it at the client computing devices. By taking out the resolution process and implementing it locally at each client, the system eliminates the bottleneck of centralized processing and achieves better load balancing across the distributed client population.
3Ease of operation
If requests are routed through intermediate cities (e.g., from San Francisco to Seattle via Atlanta and New York City), then the default DNS routing is used, but the routing efficiency and latency increase
Solution Approach 1:
The system performs preliminary DNS resolution at the client side before making the actual request to the content server. By resolving the host name to IP address locally in advance and storing it in the client's memory, the system eliminates the need for requests to traverse suboptimal intermediate routes through the default DNS system, thereby reducing routing latency.
Solution Approach 2:
Each client computing device copies the optimized IP address information locally, enabling direct routing decisions at the client side without relying on centralized DNS routing. This distributed approach allows each client to select the optimal server based on its own geographic location, avoiding inefficient intermediate routing paths.
Data Source
AI summary
Systems and methods for resolving a request associated with a host expression to an Internet Protocol (IP) address are provided. In some aspects, a request for content from a content server is transmitted from a client computing device. The request is associated with a host expression of the content server. A message including the requested content and an indication of an Internet Protocol (IP) address set of a DNS resolution of the host expression of the content server is received in response to the request. The requested content includes text or an image. The IP address set of the DNS resolution of the host expression of the content server is stored in a local memory of the client computing device. The IP address set is stored for resolution of future requests associated with the host expression of the content server locally at the client computing device.