Domain Name Resolution Fallback via Backup Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing domain name resolution processes suffer from instability, leading to poor user experience.
Innovation Solution
A method and apparatus that involve obtaining request information from a client, retrieving candidate node information from a second server when the first server lacks necessary data, and sending this information to the client to improve stability and speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the first server relies on local DNS resolution results to process domain name resolution requests, then the processing speed may be improved, but the stability deteriorates due to potential DNS hijacking or local DNS failures
Solution Approach 1:
The patent introduces a second server as an intermediary to provide backup domain name resolution services. When the first server cannot obtain reliable node information through local DNS resolution (due to hijacking or failure), it queries the second server for candidate node information, ensuring stable service continuity without over-relying on local DNS results
Solution Approach 2:
The system performs preliminary checks by first attempting local DNS resolution, and only when that fails or appears unreliable does it proceed to query the second server. This preliminary action optimizes the resolution process by avoiding unnecessary external queries while ensuring backup availability
2Reliability
If the first server queries the second server for candidate node information, then the stability improves by not relying solely on local DNS, but the waiting time increases due to additional network requests
Solution Approach 1:
The first server performs local DNS resolution first as a preliminary action to obtain node information quickly. Only when local resolution fails or the results appear unreliable does it proceed to query the second server, thereby minimizing additional waiting time while maintaining stability
Solution Approach 2:
The system implements a feedback mechanism where the first server evaluates the reliability of local DNS results and dynamically decides whether to query the second server. This feedback loop ensures that the second server is consulted only when necessary, optimizing the balance between stability and waiting time
3Productivity
If the first server stores and uses local node information, then the processing speed improves, but the adaptability deteriorates when local DNS is hijacked or corrupted
Solution Approach 1:
The second server acts as an intermediary that provides alternative node information when the first server's local storage is compromised by DNS hijacking or corruption. This allows the system to maintain adaptability to malicious scenarios while preserving the efficiency of local caching for legitimate cases
Solution Approach 2:
The system maintains a copy of node information in the second server as a backup to the first server's local storage. When local storage is hijacked or corrupted, the system can retrieve fresh node information from the second server's copy, ensuring adaptability without sacrificing processing speed
Data Source
AI summary
A method for processing a domain name resolution request is provided. The method includes: obtaining first request information of a first domain name resolution request sent by a target client, wherein the first request information comprises a domain name to be resolved carried in the first domain name resolution request, and client information of the target client; obtaining a first information set from a second server, in response to determining that first target node information corresponding to the first request information is not stored in the first server based on the domain name to be resolved and the client information, wherein the first information set is a collection of first candidate node information corresponding to the first request information; taking at least one first candidate node information in the first information set as the first target node information, and sending the first target node information to the target client.