Self-Resolved Domain Names for Scalable CDN DNS Offloading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The maintenance of massive dedicated domain name resolution records for access network devices in CDN systems is difficult and costly due to frequent updates, straining authoritative DNS servers and impacting service availability.
Innovation Solution
Implement a domain name management method using self-resolved domain names that are automatically generated based on service addresses, eliminating the need for maintaining extensive records and enabling real-time updates, thus reducing maintenance difficulty and costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dedicated domain names are used for HTTPS traffic offloading to access network devices, then security is improved, but the complexity of maintaining domain name resolution records increases significantly
Solution Approach 1:
The access network device automatically generates its own domain name resolution record using its service address through a predetermined algorithm, eliminating the need for manual configuration and reducing maintenance complexity. The device self-updates its domain name record when its service address changes, without requiring intervention from the authoritative DNS server or manual updates.
Solution Approach 2:
The patent changes the parameter representation by deriving the domain name from the service address through a predetermined algorithmic relationship rather than maintaining separate dedicated domain names. This algorithmic transformation allows the domain name to automatically adapt when service address parameters change, reducing maintenance burden.
2Productivity
If dedicated domain names are assigned to massive access network devices, then HTTPS traffic offloading capability is improved, but the strain on authoritative DNS servers increases
Solution Approach 1:
Each access network device independently generates its own domain name resolution record using its service address and a predetermined algorithm, eliminating the need for the authoritative DNS server to store and manage resolution records for hundreds of millions of devices. This significantly reduces the computational burden and resource consumption of authoritative DNS servers.
Solution Approach 2:
The patent extracts the domain name generation function from the authoritative DNS server and relocates it to each access network device. By removing the need for the DNS server to maintain resolution records for access network devices, the system reduces the operational load and resource requirements of authoritative DNS servers.
3Reliability
If domain name resolution records are frequently updated to reflect service address changes, then service availability is improved, but maintenance costs increase
Solution Approach 1:
When an access network device's service address changes, the device automatically generates a new domain name resolution record using its updated service address and the predetermined algorithm. This self-update mechanism ensures service availability is maintained without requiring costly manual interventions or frequent DNS server updates.
Solution Approach 2:
The patent establishes a predetermined algorithmic relationship between service addresses and domain names in advance. This preliminary setup enables automatic domain name generation when service addresses change, eliminating the need for costly real-time manual updates and ensuring continuous service availability.
Data Source
AI summary
In an example method, a scheduling system receives an access request of a user, where the access request includes a service domain name. The scheduling system determines, based on the access request, a target device from a plurality of access network devices that serve the service domain name, and redirects the access request to a target device in a normal service state. A domain name system receives a domain name resolution request of the user, where the domain name resolution request of the user is generated based on redirection information, and the domain name resolution request of the user includes a self-resolved domain name of the target device. The domain name system determines a service address of the target device based on a manner of mapping between a self-resolved domain name and a service address and the self-resolved domain name of the target device.