CDN Edge Node Scheduling via Proxy to Avoid DNS Hijacking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
DNS domain hijacking leads to incorrect IP address returns for CDN edge nodes, causing video service play failures, with over 50% of failures attributed to this issue.
Innovation Solution
Implement a scheduling proxy server that determines the target CDN scheduling center and edge node IP addresses based on terminal device IP addresses, bypassing direct DNS resolution, ensuring correct IP address acquisition and integrating authentication processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DNS domain resolution is used for CDN edge node scheduling, then the scheduling system can resolve domain names to IP addresses, but DNS domain hijacking occurs causing incorrect IP address returns and video service play failures
Solution Approach 1:
The patent introduces a scheduling proxy server as an intermediary between the terminal device and the CDN scheduling center. This proxy server obtains the IP address of the target CDN edge node through proxy scheduling requests, bypassing the traditional DNS resolution process. By using this intermediary, the system avoids DNS domain hijacking attacks while still achieving proper IP address acquisition for CDN edge node scheduling.
2Device complexity
If terminal device directly initiates scheduling requests to CDN scheduling center, then the scheduling process is simple, but DNS domain hijacking is prone to occur causing play failures
Solution Approach 1:
The scheduling proxy server serves as a mediator that the terminal device communicates with instead of directly contacting the CDN scheduling center. The proxy server handles the scheduling requests and obtains IP addresses through proxy scheduling, preventing DNS hijacking while maintaining a relatively simple interface for the terminal device. This resolves the contradiction by adding an intermediary layer that protects against security threats without significantly complicating the user-facing process.
3Reliability
If proxy scheduling is implemented through scheduling proxy server, then DNS hijacking is avoided and IP address correctness is ensured, but additional interaction steps are introduced
Solution Approach 1:
The scheduling proxy server performs preliminary actions by obtaining the IP address of the target CDN edge node in advance through proxy scheduling requests. By pre-acquiring the correct IP address before the terminal device needs it, the system eliminates the need for terminal devices to perform DNS resolution and subsequent scheduling requests. This preliminary action ensures IP address correctness while minimizing actual interaction delays during content access.
Solution Approach 2:
The scheduling proxy server creates a copy of the scheduling function, allowing terminal devices to obtain IP addresses through the proxy without directly interacting with the CDN scheduling center. This copying mechanism enables the proxy server to handle scheduling requests efficiently and return correct IP addresses to multiple terminal devices, reducing overall interaction delays while maintaining high reliability.
Data Source
AI summary
A content delivery network (CDN) edge node scheduling method includes receiving, by a scheduling proxy server, a first request message from a terminal device, determining, based on a first Internet Protocol (IP) address and configuration information, a target CDN scheduling center corresponding to the first IP address, sending a second request message to the target CDN scheduling center when the target CDN scheduling center supports proxy scheduling setting, receiving the second IP address from the target CDN scheduling center, and sending a request response message to the terminal device to obtain delivery content from the target CDN edge node based on the second IP address.