Domain name resolution method and system, server and storage medium
Through the diversion mechanism that matches hot domain name sets with devices, the problem of high hardware and operation and maintenance costs in large-scale domain name resolution services is solved, and efficient resource utilization and performance improvement are achieved.
Patent Information
- Application Number
- CN202511064916.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-30
- Publication Date
- 2025-09-26
AI Technical Summary
In large-scale domain name resolution services, existing technologies rely on a large number of DNS servers, resulting in high hardware and operation and maintenance costs, and the performance of a single device is limited by the cache hit rate and recursive query complexity.
By determining the hot domain name set and matching it with hot devices, domain name resolution requests can be diverted. Hot domain names are processed by high-performance devices, while non-hot domain names are processed by ordinary devices. The highly concentrated characteristics of the hot data set are used to improve cache hit rate and processing capabilities.
The total number of servers has been significantly reduced, lowering hardware procurement, computer room space, and operation and maintenance costs, while improving overall performance and cache hit rates.
Smart Images
Figure CN120710977A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and specifically to a domain name resolution method, system, server, and storage medium. Background Art
[0002] In large-scale domain name resolution services, commonly used technical methods include directly using BIND (Berkeley Internet Name Domain, a server software) to build domain name resolution services or combining self-developed caches with BIND for iterative queries. Whether using BIND directly or combining self-developed caches with BIND for iterative queries, both rely on deploying a large number of DNS servers to handle all DNS request traffic. Regardless of which method is used, due to the complex business processing flow, it is necessary to handle cache hits and misses, perform recursive queries, etc., and the cache's CPU cache hit rate and domain name cache hit rate are limited by the complexity of the overall traffic, resulting in limited performance of a single device. In order to meet the overall high-concurrency resolution requirements, horizontal expansion must be carried out and a large number of servers must be deployed, resulting in high hardware and operation and maintenance costs. Summary of the Invention
[0003] To address the above issues, the present application provides a domain name resolution method, system, server and storage medium.
[0004] According to the first aspect of the present application, a domain name resolution method is provided, including: a hotspot domain name set determination step, determining a preset hotspot domain name as the hotspot domain name set; a hotspot device and hotspot domain name set matching step, matching and determining at least one hotspot device, the above-mentioned hotspot device is used to resolve at least one of the above-mentioned hotspot domain names in the above-mentioned hotspot domain name set; a domain name resolution service diversion step, judging whether the domain name in the domain name resolution request includes the above-mentioned hotspot domain name in the above-mentioned hotspot domain name set; a hotspot device resolution step, when the domain name included in the domain name resolution request is the above-mentioned hotspot domain name in the above-mentioned hotspot domain name set, allocating the above-mentioned domain name resolution request to the above-mentioned hotspot device for resolution.
[0005] In some possible implementations, the method further includes: a non-hotspot device resolution step, where when the domain name included in the domain name resolution request is not the hotspot domain name in the hotspot domain name set, the domain name resolution is assigned to a non-hotspot device for resolution.
[0006] According to the second aspect of the present application, a domain name resolution system is provided, including: a hotspot domain name determination module, used to determine a preset hotspot domain name as a hotspot domain name set; a hotspot device and hotspot domain name set matching module, used to match and determine at least one hotspot device, and the above-mentioned hotspot device is used to resolve at least one of the above-mentioned hotspot domain names in the above-mentioned hotspot domain name set; a business diversion gateway module, used to determine whether the domain name included in the domain name resolution request is a hotspot domain name in the above-mentioned hotspot domain name set, wherein the above-mentioned hotspot device is used to resolve the resolution request of the hotspot domain name in the above-mentioned hotspot domain name set.
[0007] In some possible implementations, the system further includes: a non-hotspot device configured to resolve a resolution request for a domain name that is not included in the hotspot domain name set.
[0008] According to a third aspect of the present application, a server is provided, comprising: a memory and one or more processors, wherein the memory is used to store instructions executed by the processors, and the processors are used to execute the domain name resolution method as described in any one of the first aspects.
[0009] According to a fourth aspect of the present application, a computer program product is provided, comprising a computer program / instruction. When the computer program / instruction is executed by a processor, the domain name resolution method as described in any one of the first aspects is implemented.
[0010] According to a fifth aspect of the present application, a computer-readable storage medium is provided, on which instructions are stored. The instructions enable the computer to execute the domain name resolution method as described in any one of the first aspects.
[0011] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
[0012] The implementation of the present disclosure has the following beneficial effects: the technical solution of the present disclosure determines the preset hotspot domain name as the hotspot domain name set through the hotspot domain name set determination step; the hotspot device and hotspot domain name set matching step, matches and determines at least one hotspot device, and the above-mentioned hotspot device is used to resolve at least one of the above-mentioned hotspot domain names in the above-mentioned hotspot domain name set; the domain name resolution service diversion step, determines whether the domain name in the domain name resolution request includes the above-mentioned hotspot domain name in the above-mentioned hotspot domain name set; the hotspot device resolution step, when the domain name included in the domain name resolution request is the above-mentioned hotspot domain name in the above-mentioned hotspot domain name set, allocates the above-mentioned domain name resolution request to the above-mentioned hotspot device for resolution. The technical solution of the present disclosure significantly reduces the total number of servers required to achieve the same overall performance by classifying the domain name resolution request traffic and processing it by different optimized clusters, thereby directly saving the cost of hardware procurement, computer room space, power consumption and operation and maintenance management.
[0013] Further features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] In order to more clearly illustrate the technical solutions and advantages of the embodiments of this specification or the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0015] Figure 1 A schematic diagram showing a flow chart of a domain name resolution method according to an embodiment of the present disclosure;
[0016] Figure 2 A block diagram of a domain name resolution system according to an embodiment of the present disclosure is shown;
[0017] Figure 3 A schematic diagram of a domain name resolution scenario according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0018] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this invention.
[0019] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0020] Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. Like reference numerals in the drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the drawings, the drawings are not necessarily drawn to scale unless otherwise indicated. The word "exemplary" is used herein to mean "serving as an example, example, or illustration."
[0021] Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
[0022] The term "and / or" herein simply describes an association relationship between associated objects, indicating that three relationships can exist. For example, "A and / or B" can represent the existence of three situations: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" herein refers to any combination of at least two of any one or more of a plurality of items. For example, "at least one of A, B, and C" can represent any one or more elements selected from the set consisting of A, B, and C.
[0023] Furthermore, in order to better illustrate the present disclosure, numerous specific details are given in the following detailed description.
[0024] Those skilled in the art will appreciate that the present disclosure can be implemented without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main points of the present disclosure.
[0025] Figure 1 A flow chart of a domain name resolution method according to an embodiment of the present disclosure is shown as follows: Figure 1 As shown, the above method includes a hotspot domain name set determination step S10, a hotspot device and hotspot domain name set matching step S20, a domain name resolution service diversion step S30, and a hotspot device resolution step S40. Each step is described in detail below.
[0026] S10: a hotspot domain name set determination step, determining preset hotspot domain names as the hotspot domain name set.
[0027] Hot Domains refer to domains that require special attention within a specific network environment due to high traffic volume, business-criticality, or special management requirements (such as security protection and performance optimization). Centrally identifying and managing these domains (such as e-commerce payment interfaces and video streaming sites) allows for targeted acceleration strategies, enhanced security protection, and prioritized resource allocation, significantly improving core service stability, user experience, and operational efficiency, while avoiding significant losses caused by peak service outages or security vulnerabilities.
[0028] The disclosed embodiments do not limit the specific method for determining a hotspot domain name set. For example, the determination of hotspot domain names can be primarily implemented through a combination of multi-dimensional data analysis and business assessment. Methods for determining a hotspot domain name set include, but are not limited to, screening high-frequency request domain names (e.g., the top 10% of traffic) based on historical access logs, identifying core service domain names (e.g., payment and login interfaces) based on business criticality, combining security risk ratings (e.g., vulnerable public interfaces), and supplementing burst traffic domain names (e.g., new domain names associated with hotspot events) through dynamic monitoring. By forming a set of hotspot domain names that require unified management, precise targets are provided for resource optimization and security protection.
[0029] S20: a step of matching hotspot devices with a hotspot domain name set, wherein at least one hotspot device is matched and determined, and the hotspot device is used to resolve at least one hotspot domain name in the hotspot domain name set.
[0030] The disclosed embodiments direct the association of a predefined set of hotspot domain names to specific resolution server devices, also known as hotspot devices, through system configuration or policy rules. This matching process requires the explicit designation of at least one hotspot device, ensuring that this device is specifically configured and optimized to specifically respond to and resolve DNS query requests for at least one domain name in the hotspot domain name set. By setting up hotspot devices, dedicated, high-performance, and highly available resolution services are provided for core domain names, ensuring their resolution efficiency and stability.
[0031] S30: Domain name resolution service diversion step, determining whether the domain name in the domain name resolution request includes the hot domain name in the hot domain name set.
[0032] The disclosed embodiment detects the target domain name in the resolution request in real time. When a domain name resolution request arrives, the system immediately extracts the domain name field in the request, compares it with the hot domain name set preloaded into the memory at high speed to obtain a judgment result, and performs the next resolution action based on the judgment result.
[0033] S40: hotspot device resolution step. When, according to the judgment result of the domain name resolution service diversion step S30, the domain name resolution request includes the hotspot domain name in the hotspot domain name set, the domain name resolution request is allocated to the hotspot device for resolution.
[0034] In some possible embodiments, the domain name resolution method further includes a non-hotspot device resolution step. When the domain name included in the domain name resolution request is not the hotspot domain name in the hotspot domain name set, the domain name resolution is assigned to a non-hotspot device for resolution.
[0035] Based on the business diversion results of the previous step, if the domain name exists in the hot domain name set, the diversion rule will be triggered, and the domain name request will be forwarded to a dedicated high-performance resolution cluster, that is, assigned to the hot device for resolution; if the domain name is not a hot domain name, it will be assigned to the regular resolution pool according to the default path, that is, ordinary devices (non-hotspot devices) for resolution. This ensures that the resolution of core domain names (hot domain names) has priority in obtaining high concurrency processing capabilities and low latency responses.
[0036] Figure 2 A block diagram of a domain name resolution system according to an embodiment of the present disclosure is shown as follows: Figure 2 As shown, the above-mentioned domain name resolution system includes:
[0037] The hotspot domain name determination module 101 is configured to determine preset hotspot domain names as a hotspot domain name set.
[0038] The hotspot device and hotspot domain name set matching module 102 is used to match and determine at least one hotspot device, and the hotspot device is used to resolve at least one hotspot domain name in the hotspot domain name set.
[0039] The service offload gateway module 103 is used to determine whether the domain name included in the domain name resolution request is a hot domain name in the hot domain name set.
[0040] The hotspot device is used to resolve the resolution request of the hotspot domain name in the hotspot domain name set.
[0041] In some possible embodiments, the system further includes a non-hotspot device configured to resolve a resolution request for a domain name that is not included in the hotspot domain name set.
[0042] Figure 3 A schematic diagram of a domain name resolution scenario according to an embodiment of the present disclosure is shown as follows: Figure 3 As shown: The system continuously monitors the domain name resolution requests sent through real-time traffic probes. When the domain name resolution request arrives at the DNS business diversion gateway, the gateway immediately starts the high-speed decision engine: first, the target domain name in the domain name resolution request is extracted, and millisecond-level matching is performed based on the hotspot domain name set pre-loaded into the memory. If the target domain name contained in the domain name resolution request is identified as a hotspot domain name, the gateway will automatically trigger a high-priority routing policy and forward this request to a dedicated hotspot device cluster for domain name resolution; conversely, if the target domain name contained in the domain name resolution request is not in the hotspot domain name set, it will be dispatched to a common device in the shared resource pool for domain name resolution processing. This layered resolution architecture ensures the acceleration of core business (resolution of hotspot domain names) while reducing the resource overhead of long-tail domain names.
[0043] In a specific embodiment, it is necessary to meet the overall performance of 20 million QPS (Queries Per Second is a common unit for measuring system performance, indicating the number of queries per second or the request processing capacity per second). The present disclosure forwards hotspot domain names (such as the Top 100,000 high-frequency domain names) to dedicated hotspot devices for processing through business diversion, and uses its extremely small data set characteristics to achieve a CPU cache hit rate of over 90% and a memory cache hit rate of 95%, so that a single hotspot device can carry 20 million QPS; at the same time, ordinary domain names are forwarded to ordinary devices for processing. Although they need to bear a certain recursive query delay, they only need to process 5% of the total traffic, that is, 1 million QPS. Compared with traditional solutions, due to the massive domain names, the cache hit rate is less than 40%. A single ordinary device is limited by high-frequency cache failures and recursive calculations, and the performance is only 5 million QPS. Four devices need to be deployed to meet the 20 million QPS requirement, and the recursive bandwidth consumption increases by 16 times to 48Gbps. The technical solution provided by the present disclosure only requires one hotspot device and one ordinary device, which saves hardware procurement compared to the traditional solution (four devices + recursive cluster). As the application time increases, the cumulative cost savings will be more substantial.
[0044] In summary, the technical solution disclosed in the present invention accurately classifies domain name resolution requests according to access characteristics through a diversion mechanism, guides high-frequency hotspot traffic to a dedicated high-performance cluster for processing, and utilizes the highly concentrated characteristics of hotspot data sets to significantly improve cache hit efficiency and instruction execution locality, so that the processing capacity of each device can achieve a breakthrough growth; at the same time, it directs long-tail ordinary traffic to a resource-optimized cluster to effectively control recursive query overhead. It fundamentally resolves the problems of low cache efficiency and idle computing resources caused by the randomness of data access in traditional solutions, so that under the condition of meeting the same overall service performance, the total demand for physical servers is greatly reduced, directly leading to a significant decrease in hardware procurement, computer room space occupancy and energy consumption. The deeper benefit lies in the exclusive optimization of system resources by isolating hotspot traffic, avoiding the pollution of cache resources by massive ordinary domain names, systematically reducing the pressure of recursive queries, and ultimately reconstructing the relationship between performance and cost with an architectural-level "divide and conquer" strategy, achieving an intensive leap in infrastructure investment.
[0045] Those skilled in the art will understand that, in the above-mentioned method of the specific implementation mode, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.
[0046] It can also be understood that the above-mentioned method embodiments mentioned in the present disclosure can be combined with each other to form combined embodiments without violating the principle logic. Due to space limitations, the present disclosure will not elaborate on them.
[0047] An embodiment of the present application further provides a server, comprising: a memory and one or more processors, the memory being used to store instructions executed by one or more processors, and the processor being used to execute the domain name resolution method mentioned in any one of the above embodiments of the present application.
[0048] An embodiment of the present application further provides a computer program product, including: a computer program / instruction, which, when executed by a processor, implements the computer program code of the domain name resolution method mentioned in any of the above embodiments of the present application.
[0049] An embodiment of the present application also provides a computer-readable medium having instructions stored thereon. When the instructions are executed on a server, the server executes the domain name resolution method mentioned in any one of the above embodiments of the present application.
[0050] A computer-readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium can be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination thereof. As used herein, a computer-readable storage medium is not to be construed as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through an electrical wire.
[0051] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in the computer-readable storage medium in each computing / processing device.
[0052] The computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages such as Smalltalk, C++, and conventional procedural programming languages such as "C" language or similar programming languages. Computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be personalized by utilizing the state information of the computer-readable program instructions, which may be executed by the computer-readable program instructions to implement various aspects of the present disclosure.
[0053] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0054] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.
[0055] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more blocks in the flowchart and / or block diagram.
[0056] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the above-mentioned module, program segment or instruction contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions specified in the box can also occur in an order different from the order specified in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart, can be implemented by a special hardware-based system that performs the specified function or action, or can be implemented by a combination of special hardware and computer instructions.
[0057] While various embodiments of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or technological improvements in the marketplace, or to enable others skilled in the art to understand the embodiments disclosed herein.
Claims
1. A domain name resolution method, characterized in that: The domain name resolution method includes: a hotspot domain name set determining step, determining the preset hotspot domain names as the hotspot domain name set; The hotspot device and the hotspot domain name set matching step, matching to determine at least one hotspot device, The hotspot device is used to resolve at least one hotspot domain name in the hotspot domain name set; A domain name resolution service diversion step, determining whether the domain name in the domain name resolution request includes the hot domain name in the hot domain name set; The hotspot device resolution step includes: when the domain name contained in the domain name resolution request is the hotspot domain name in the hotspot domain name set, allocating the domain name resolution request to the hotspot device for resolution.
2. The domain name resolution method according to claim 1, wherein: Also includes: The non-hotspot device resolution step allocates the domain name resolution to a non-hotspot device for resolution when the domain name included in the domain name resolution request is not the hotspot domain name in the hotspot domain name set.
3. A domain name resolution system, characterized in that: The domain name resolution system includes: A hotspot domain name determination module, configured to determine a preset hotspot domain name as a hotspot domain name set; A hotspot device and hotspot domain name set matching module, used to match and determine at least one hotspot device, and the hotspot device is used to resolve at least one hotspot domain name in the hotspot domain name set; The service offloading gateway module is used to determine whether the domain name included in the domain name resolution request is a hot domain name in the hot domain name set, The hotspot device is used to resolve the resolution request of the hotspot domain name in the hotspot domain name set.
4. The domain name resolution system according to claim 3, wherein: include: The non-hotspot device is used to resolve a resolution request for a domain name that is not included in the hotspot domain name set.
5. A server, characterized in that: include: A memory and one or more processors, wherein the memory is used to store instructions executed by the processor, and the processor is used to execute the domain name resolution method according to any one of claims 1 to 2.
6. A computer program product, characterized in that The method comprises a computer program / instruction, which, when executed by a processor, implements the domain name resolution method according to any one of claims 1 to 2.
7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and the instructions enable the computer to execute the domain name resolution method according to any one of claims 1 to 2.