CDN Mapping Server Correlating Client and ISP DNS IP Addresses
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current content distribution networks (CDNs) face inefficiencies in redirecting content requests to edge servers due to reliance on source IP address masking, which can lead to suboptimal selection of closer edge servers, resulting in increased latency and resource overload on content servers.
Innovation Solution
Implementing a CDN system that correlates client systems' locations with ISP DNS servers to predict actual request origins, allowing for more accurate selection of edge servers based on network proximity measures, and optionally downloading CDN client software to enhance location determination and content delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If CDNs use source IP address masking to redirect content requests to edge servers, then content distribution is simplified, but location accuracy deteriorates leading to suboptimal edge server selection
Solution Approach 1:
The system performs preliminary actions by establishing correlations between client systems and ISP DNS servers before actual content requests occur. The mapping server pre-establishes the relationship between client IP addresses and their corresponding ISP DNS servers, so when a request comes in, the CDN can accurately determine the client's true location even though the DNS request appears to come from the ISP DNS server. This preliminary mapping resolves the location accuracy problem while maintaining the simplicity of using DNS-based redirection.
2Speed
If CDNs redirect requests to geographically dispersed edge servers, then content delivery speed is improved, but system complexity increases due to multiple server locations
Solution Approach 1:
The mapping server acts as an intermediary that simplifies the system architecture. Instead of requiring each CDN edge server to independently determine client locations and manage complex multi-location routing logic, the mapping server centralizes the location correlation function. It receives DNS requests, determines the actual client location using the pre-established mappings, and redirects requests to appropriate edge servers. This intermediary approach maintains fast content delivery through geographically dispersed servers while reducing overall system complexity by centralizing the location management function.
Data Source
AI summary
A method receives from a first server a first domain name system (DNS) request including a first internet protocol (IP) address of the first server, and a second IP address received by the first server from a first system. The method also maps a correlation between the first IP address and the second IP address, and receives from the first server a second DNS request. In response to receiving the second DNS request, the method responds to the first server with a third IP address of a second server, wherein the third IP address is chosen based upon the second IP address.