Iterative CNAME Resolution Server for DNS Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing domain name resolution methods require multiple requests and are inefficient when dealing with multiple levels of CNAME records, leading to prolonged resolution times and increased processing complexity.

Innovation Solution

A domain name resolution method and system that uses a server with processors and memory to receive a domain name resolution request, iteratively resolve the target domain name using the resolution result as a new target until a network address of a preset type is obtained, simplifying the process and improving efficiency by potentially enabling accelerated resolution for CNAME records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If traditional domain name resolution methods are used to resolve multiple levels of CNAME records, then the resolution can be completed, but multiple requests are required and resolution time is prolonged

Engineering Contradiction:
Improveresolution timeVSAvoidresolution efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The server pre-resolves CNAME records and stores the mapping relationships between CNAME records and domain names in advance. When a resolution request arrives, the server directly queries the pre-stored mapping information, eliminating the need for multiple sequential resolution requests and significantly reducing resolution time.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traditional domain name resolution methods are used for multiple levels of CNAME records, then complete resolution is achieved, but the number of requests increases and processing complexity increases

Engineering Contradiction:
Improveresolution completenessVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server performs preliminary resolution of CNAME records and stores the complete mapping information in advance. This pre-processing consolidates multiple resolution steps into a single stored dataset, reducing the complexity of processing subsequent resolution requests while ensuring complete and accurate resolution results.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The server creates and stores copies of the CNAME resolution mapping relationships in a lookup table. Instead of performing complex multi-step resolution processes for each request, the server simply queries the pre-created copy of the resolution data, significantly simplifying the processing complexity while maintaining resolution completeness.

Inventive Principle:
Principle #26Copying

3Measurement precision

If iterative resolution is performed for CNAME records, then accurate resolution results are obtained, but the number of requests increases

Engineering Contradiction:
Improveresolution accuracyVSAvoidrequest volume
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The server performs the iterative CNAME resolution process in advance and stores the final accurate mapping relationships. When resolution requests arrive, the server directly queries the pre-computed accurate results without performing iterative resolution, thereby maintaining resolution accuracy while dramatically reducing the number of requests required.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10757065B2Domain name resolution method, device and system, and storage medium
Publication Date: 2020.08.25 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US10757065B2 patent drawing
  • US10757065B2 patent drawing
  • US10757065B2 patent drawing

AI summary

Embodiments of the present disclosure disclose a domain name resolution method, apparatus, and system, and a storage medium. The method includes: receiving a domain name resolution request sent by a network device, the domain name resolution request carrying a first target domain name that needs to be resolved; using the first target domain name as an initial value of a second target domain name; resolving the second target domain name, to obtain a corresponding resolution result; determining whether the resolution result is corresponds to a network address of a preset type; and repeating the aforementioned operations using the resolution result as the second target domain name until a resolution result corresponding to the network address of the preset type is obtained; and after obtaining the resolution result corresponding to the network address of the preset type, returning the resolution result to the network device.