A method, system, device and medium for testing domain name resolution services

By automating the testing of domain name resolution services, generating request traffic and calculating metric data, the problems of low testing efficiency and insufficient accuracy in existing technologies are solved, and a highly efficient automated testing process is achieved.

CN117675651BActive Publication Date: 2026-11-10PENG CHENG LAB
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311792657.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-12-22
Publication Date
2026-11-10
Estimated Expiration
2043-12-22

AI Technical Summary

Technical Problem

Existing domain name resolution service testing methods have a low degree of automation, resulting in a large amount of manual labor and time spent on baseline data collection before testing. During the testing process, traffic generation and data processing rely on manual labor, resulting in little feedback on test results and difficulties in data processing, leading to low testing efficiency and accuracy.

Method used

By acquiring test requests, generating request traffic and sending it to the target object, obtaining response traffic, calculating metric data using benchmark data, and generating test result reports, automated processing and real-time updates are achieved.

Benefits of technology

The automation level of domain name resolution service testing has been improved, the amount of manual operation has been reduced, the testing efficiency and accuracy have been improved, and the authority and timeliness of the benchmark data have been ensured.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117675651B_ABST
    Figure CN117675651B_ABST
Patent Text Reader

Abstract

This application provides a domain name resolution service testing method, system, apparatus, and medium, belonging to the field of network testing technology. The method includes: obtaining a test request and extracting a test domain name set from benchmark data based on the test request; generating request traffic based on the test request and the test domain name set, and sending the request traffic to a target object; obtaining response traffic returned from the target object, then obtaining indicator data based on the benchmark data, request traffic, and response traffic, and determining a test result report for the target object based on the test request and indicator data; wherein the benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to a test request; the target object is determined by the test request. The domain name resolution service testing method of this application can improve the automation level of domain name resolution service testing, and improve testing efficiency and accuracy.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of network testing technology, and in particular to a method, system, device and medium for testing domain name resolution services. Background Technology

[0002] Domain Name System (DNS), as a critical piece of internet infrastructure, plays a crucial role in the operation of most internet and cloud applications. Its main function is to translate user-friendly domain names into machine-understandable IP addresses. DNS not only allows people to access websites using easy-to-remember domain names instead of complex IP addresses, but it also provides vital support for the scalability and stability of the internet.

[0003] In existing DNS testing methods, the collection, classification, analysis, and processing of relevant data before and after testing are poorly automated, lacking real-time updates and automatic classification capabilities. This results in significant manual and time costs during the baseline data collection phase before testing. Similarly, during testing, existing DNS testing methods require substantial manual processing for generating and sending test traffic and collecting and processing response traffic. Furthermore, the resulting data metrics are limited and lack further analysis, necessitating significant manual labor for data analysis. In addition, the functionality of DNS testing systems and methods in these technologies is incomplete, with limited feedback during testing, difficulties in processing test results, and a lack of open interfaces, further reducing testing efficiency and accuracy. Summary of the Invention

[0004] The main objective of this application is to propose a domain name resolution service testing method, system, device, and medium that can improve the automation level of domain name resolution service testing, thereby improving testing efficiency and accuracy.

[0005] To achieve the above objectives, a first aspect of this application proposes a domain name resolution service testing method, comprising: obtaining a test request and extracting a test domain name set from benchmark data according to the test request; generating request traffic according to the test request and the test domain name set, and sending the request traffic to a target object; obtaining response traffic returned from the target object, obtaining indicator data according to the benchmark data, the request traffic, and the response traffic, and determining a test result report for the target object according to the test request and the indicator data; wherein the benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to the test request; and the target object is determined by the test request.

[0006] In some embodiments, before extracting the test domain name set from the benchmark data according to the test request, the method includes: periodically or in response to the test request, synchronizing an original dataset from a target server to a local machine, the original dataset including domain name information, Internet Protocol address information corresponding to the domain name information, and domain name record type information; classifying the original dataset according to the domain name information and the domain name record type information to obtain benchmark data of different categories; wherein, the benchmark data includes the domain name information and the corresponding Internet Protocol address information and domain name record type information.

[0007] In some embodiments, the test request includes test category information, which is used to associate the benchmark data of a preset category; the step of obtaining the test request and extracting a test domain set from the benchmark data according to the test request includes: obtaining the test request and extracting the test category information from the test request; selecting the benchmark data of the corresponding category according to the test category information and extracting the test domain set from the selected benchmark data.

[0008] In some embodiments, the request traffic includes one or more request packets; generating request traffic based on the test request and the test domain set, and sending the request traffic to the target object includes: obtaining packet configuration parameters and sending configuration parameters based on the test request and preset pre-configuration information; generating request packets based on the packet configuration parameters and the test domain set; generating the request traffic based on the request packets, and sending the request traffic to the target object based on the sending configuration parameters; wherein, the sending configuration parameters are configured as static parameters or dynamic parameters that are adjusted according to changes in network conditions or test phases.

[0009] In some embodiments, the sending configuration parameters include the number of tests, the packet sending rate, and the test step size; the step of generating the request traffic based on the request message and sending the request traffic to the target object according to the sending configuration parameters includes: assembling the request message into request traffic; confirming the number of tests, the packet sending rate, and the test step size according to the sending configuration parameters; and sending the request traffic to the target object based on the confirmed number of tests, the packet sending rate, and the test step size.

[0010] In some embodiments, the step of generating the request traffic based on the request message and sending the request traffic to the target object according to the sending configuration parameters further includes: when the sending configuration parameters are configured as dynamic parameters, determining the packet sending rate and test step size for this round of testing based on the current network conditions or the current number of tests according to the sending configuration parameters; and sending the request traffic to the target object based on the confirmed packet sending rate and test step size.

[0011] In some embodiments, the step of acquiring response traffic returned from the target object, obtaining indicator data based on the baseline data, the request traffic, and the response traffic, and determining a test result report for the target object based on the test request and the indicator data includes: acquiring response traffic returned from the target object, processing the response traffic according to the traffic acquisition type to obtain acquisition results, and saving the acquisition results according to the storage type; extracting key information from the acquisition results, and calculating the indicator data based on the baseline data, the request traffic, and the key information; and determining the test result report for the target object based on the test request and the indicator data; wherein the traffic acquisition type and the storage type are preset or confirmed according to the test request.

[0012] In some embodiments, the traffic acquisition type includes log type and raw traffic type. The process of acquiring the response traffic returned from the target object, processing the response traffic according to the traffic acquisition type to obtain acquisition results, and then saving the acquisition results according to the storage type includes: when the traffic acquisition type is configured as log type, acquiring the response traffic and performing real-time decoding processing on the response traffic to obtain log type acquisition results; when the traffic acquisition type is configured as raw traffic type, acquiring the response traffic and obtaining raw traffic type acquisition results based on the response traffic; and storing the acquisition results locally or externally according to the storage type. The raw traffic type acquisition results are stored in the form of raw packets or compressed packets, and the storage type is used to select whether to store the acquisition results locally or externally, or the storage type is further configured to automatically select local storage or external storage based on the current storage usage.

[0013] In some embodiments, the step of extracting key information from the collection results and then calculating the indicator data based on the baseline data, the request traffic, and the key information includes: extracting the key information directly from the log-type collection results when the traffic collection type is configured as log-type; decoding the raw traffic-type collection results and extracting the key information from the decoding results when the traffic collection type is configured as raw traffic-type; and calculating the indicator data based on the key information.

[0014] In some embodiments, the metric data is calculated from the baseline data, the request traffic, the key information, and the sending record, wherein the sending record is generated when the request traffic is sent and is used to record the sending situation including the sending time; the key information includes the receiving time of the response traffic; the metric data includes packet sending rate, test time, number of requests, number of responses, maximum number of requests responded per unit time, number of valid responses, valid response rate, number of correct responses, accuracy rate, and latency.

[0015] In some embodiments, determining the test result report of the target object based on the test request and the indicator data includes: determining a result template based on the test request and a preset report template, wherein the result template is used to determine the type and display format of the indicator data displayed in the test result report; and generating the test result report based on the indicator data and the result template.

[0016] To achieve the above objectives, a second aspect of this application proposes a domain name resolution service testing system, comprising: a domain name acquisition module, configured to acquire a test request and extract a test domain name set from benchmark data according to the test request; a traffic behavior module, configured to generate request traffic according to the test request and the test domain name set, and send the request traffic to a target object; and a data processing module, configured to acquire response traffic returned from the target object, obtain indicator data according to the benchmark data, the request traffic, and the response traffic, and determine a test result report for the target object according to the test request and the indicator data; wherein the benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to the test request; and the target object is determined by the test request.

[0017] To achieve the above objectives, a third aspect of this application provides a domain name resolution service testing apparatus, the testing apparatus including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the domain name resolution service testing method described in the first aspect of the embodiment.

[0018] To achieve the above objectives, a fourth aspect of this application provides a storage medium, which is a computer-readable storage medium storing a computer program that, when executed by a processor, implements the domain name resolution service testing method described in the first aspect of the embodiment.

[0019] The domain name resolution service testing method, system, apparatus, and medium proposed in this application have the following beneficial effects:

[0020] In this embodiment, the baseline data used for domain name resolution service testing is synchronized in real time from the target server periodically or at the start of the test in response to the test request. This avoids the time and labor costs of manually updating the baseline data before each test and ensures the authority and timeliness of the information synchronized locally. Furthermore, the request traffic is generated based on the test request and the test domain set extracted from the baseline data. The test domain set is extracted from the baseline data based on the test request. Therefore, the test domain set used to generate the request traffic can be directly included in the test request or extracted from the baseline data based on the test request. The test traffic can also be generated based on the test request and the test domain set, further reducing the workload of testers in manipulating the test traffic. Obtaining the response traffic returned from the target object, then obtaining indicator data based on the baseline data, request traffic, and response traffic, and determining the test result report of the target object based on the test request and indicator data, means that after determining the test request, the acquisition of response traffic, related processing and analysis, and even the automatic calculation of key indicators and the generation of a test result report with key indicators can all be performed automatically. Moreover, the test result report can include various indicator data of the target object. Therefore, the domain name resolution service testing method in this application embodiment can improve the automation level of domain name resolution service testing, and improve testing efficiency and accuracy. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the implementation environment of the domain name resolution service testing system provided in this application embodiment;

[0022] Figure 2 This is a flowchart illustrating the domain name resolution service testing method provided in the embodiments of this application;

[0023] Figure 3 This is another flowchart illustrating the domain name resolution service testing method provided in this application embodiment;

[0024] Figure 4 yes Figure 1 The flowchart in step S101 is shown below;

[0025] Figure 5 This is another flowchart illustrating the domain name resolution service testing method provided in this application embodiment;

[0026] Figure 6 yes Figure 1 The flowchart in step S102 is shown below;

[0027] Figure 7 yes Figure 6 The flowchart in step S502 is shown below;

[0028] Figure 8 yes Figure 6 Another flowchart in step S502;

[0029] Figure 9 yes Figure 1 The flowchart in step S103 is shown below;

[0030] Figure 10 yes Figure 9 The flowchart in step S801 is shown below;

[0031] Figure 11 yes Figure 9 The flowchart in step S802 is shown below;

[0032] Figure 12 yes Figure 9 The flowchart in step S803 is shown below;

[0033] Figure 13 This is a schematic diagram of the domain name service detection system architecture provided in the embodiments of this application.

[0034] Figure 14 This is a schematic diagram of the hardware structure of the domain name service detection device provided in the embodiments of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0036] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0037] First, let's analyze some of the terms used in this application:

[0038] An Internet Protocol (IP) address is a digital tag defined in the Internet Protocol (IP) protocol used to identify and locate various devices within a network. It allows devices to send and receive data, ensuring that data is correctly transmitted from source to destination. Each IP address must be unique throughout its network.

[0039] A Media Access Control (MAC) address is a unique identifier for a network device at the physical network layer. It is typically represented by six sets of two-digit hexadecimal numbers. Every network device, whether it's a computer's network card, a router, a wireless access point, or even a smartphone, has a unique MAC address. The MAC address is hard-coded into the device's hardware during manufacturing and usually remains unchanged. MAC addresses play a crucial role in network communication. When a data packet is sent from one device to another, the source and destination MAC addresses are added to the packet header. This allows network devices to identify the source and destination of the data packet.

[0040] Packet Capture (PCAP) messages are a format for capturing and storing network packets. PCAP files can save data streams on a network for later analysis and debugging. A PCAP file contains detailed information about the network packets, including the timestamp of each packet, packet length, and the actual content of the packet. PCAP files can be used by network administrators or network security experts to analyze network behavior, find problems, or debug network applications. For example, they can use PCAP files to view data streams on the network, analyze network performance issues, or detect potential security threats.

[0041] Domain name resolution service is provided by the Domain Name System (DNS), an internet service. As a distributed database that maps domain names to IP addresses, it makes it easier for people to access the internet without having to remember the IP address strings that allow direct internet access. The process of obtaining the IP address corresponding to a hostname is called domain name resolution (or hostname resolution). The Domain Name System is a distributed database that contains internet hostnames and domain names.

[0042] Domain name resolution service testing is the process of checking and verifying the performance and correctness of DNS servers. This includes verifying whether the DNS server can correctly resolve domain names and whether its response time (the time required to resolve a domain name) is within an acceptable range. DNS testing can help identify network problems, such as slow webpage loading or inability to access certain websites, which may be due to DNS resolution issues.

[0043] In existing DNS service testing, the processes for collecting, classifying, analyzing, and processing relevant data before and after the test are poorly automated and lack real-time updates and automatic classification capabilities. This results in significant manual and time costs being incurred during the baseline data collection phase before the test. Similarly, during the test, existing DNS service testing requires substantial manual processing in generating and sending test traffic and collecting and processing response traffic. Furthermore, the types of data metrics obtained are limited, and no further analysis is performed, making data analysis and processing also labor-intensive. In addition, the functionality of related DNS testing systems and methods is incomplete, with limited feedback during the testing process, difficulties in processing test results, and a lack of open interfaces, further complicating and inefficient DNS service testing.

[0044] Based on this, embodiments of this application provide a domain name resolution service testing method, system, device, and medium, which can improve the automation level of domain name resolution service testing, thereby improving testing efficiency and accuracy.

[0045] The domain name resolution service testing method, system, device, and medium provided in this application are specifically described through the following embodiments. First, the domain name resolution service testing system in this application embodiment is described.

[0046] Reference Figure 1 , Figure 1 This is a schematic diagram of the implementation environment of the domain name resolution service testing system provided in this application embodiment. The implementation environment includes a test server 101, a DNS server 102, and a target server 103, wherein the test server 101, the DNS server 102, and the target server 103 are connected through a communication network.

[0047] For example, test server 101 can periodically synchronize baseline data from target server 103 to its local machine, or synchronize baseline data from target server 103 to its local machine in response to a test request; test server 101 can also obtain test requests, extract test domain name sets from the baseline data according to the test requests, generate request traffic according to the test requests and test domain name sets, and send the request traffic to the target object, i.e., DNS server 102; after receiving the request traffic, DNS server 102 will generate response traffic and send the response traffic back to test server 101. Test server 101 obtains the response traffic returned from DNS server 102, obtains indicator data according to the baseline data, request traffic and response traffic, and determines the test result report of the target object according to the test requests and indicator data;

[0048] Test server 101, DNS server 102 and target server 103 can be independent physical servers, or server clusters or distributed systems composed of multiple physical servers. They can also be cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0049] The test server 101, DNS server 102, and target server 103 can be directly or indirectly connected via wired or wireless communication, and this embodiment of the application does not impose any limitations on this.

[0050] The testing method for domain name resolution services can be illustrated through the following examples.

[0051] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0052] It should be noted that in all specific embodiments of this application, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent will be obtained first. Furthermore, the collection, use, and processing of this data will comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require access to sensitive personal information of users, separate permission or consent from the user will be obtained through pop-ups or redirects to confirmation pages. Only after obtaining the user's separate permission or consent will the necessary user-related data for the normal operation of the embodiments of this application be obtained.

[0053] Figure 2 This is an optional flowchart of the domain name resolution service testing method provided in the embodiments of this application. Figure 2 The method may include, but is not limited to, steps S101 to S103.

[0054] Step S101: Obtain the test request and extract the test domain name set from the benchmark data according to the test request.

[0055] The benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to a test request. In this embodiment, the benchmark data refers to data including domain names, their corresponding IP addresses, and domain name record types. The benchmark data, synchronized from the target server to the local machine, serves as a partial option for testers to select domain names for domain name resolution service testing and as a reference for calculating some key indicators in the final test results. The target server refers to an organization capable of providing accurate and comprehensive benchmark data. The test domain set is the set of domain names to be tested provided based on the test request or the set of domain names to be tested selected from the benchmark data based on the test request.

[0056] For example, in order to ensure the authority and correctness of domain name information in this application embodiment, information is not queried and collected from some independent DNS servers, nor is the domain name manually assembled by designing functions or programs. Instead, the domain name information and the IP information corresponding to the domain name are synchronized to the local machine from the target server in real time or in response to test requests through automated script programs, so as to ensure the authority, timeliness and accuracy of the domain name information synchronized to the local machine, that is, the benchmark data.

[0057] For example, the target server is the server of an authoritative organization. To ensure the authority and accuracy of the domain name information, this embodiment differs from related technologies in that it does not query and collect information from independent DNS servers, nor does it manually simulate the assembly of domain names using functions or programs. Instead, it synchronizes this domain name information and the corresponding IP information from authoritative organizations such as Alexa and IANA to the local machine periodically or in real-time via automated scripts. This not only ensures the authority, timeliness, and usability of the domain name information but also takes into account the historical information that some domain names may have, such as the same domain name having different corresponding IP addresses at different times.

[0058] Step S102: Generate request traffic based on the test request and the test domain set, and send the request traffic to the target object.

[0059] The target object is the DNS server to be tested, as determined by the test request. Request traffic refers to the number and size of domain name resolution requests sent to the DNS server. This traffic includes all requests sent to the DNS server, such as querying the IP address corresponding to a domain name, querying mail exchange records, and querying domain aliases.

[0060] Furthermore, the traffic generation program generates standard domain name resolution service request traffic based on the test domain name set selected by the tester and the basic parameters set. The basic components of the request traffic are individual domain name resolution service request messages. These messages have a standard, fixed format, and their main information includes the source and destination IP addresses, source and destination MAC addresses, the requested domain name information, and other control fields. After the tester selects the set of domain names to be tested and configures the domain name resolution service to be tested, the self-developed supporting program assembles the standard request messages based on this information and combines all the request messages into the request traffic.

[0061] Furthermore, the request traffic is sent through a traffic generation program, which then sends the generated request traffic to the target network, namely the DNS server to be tested, through a hardware packet sending port.

[0062] It should be noted that since the test initiator and the test target may not be directly connected, but separated by other network devices, the sending program needs to identify network conditions and adjust its sending behavior accordingly, such as network connectivity, gateway configuration, and firewall restrictions. Furthermore, to meet different testing needs, parameters such as the packet sending rate and the number of tests need to be set before sending packets. In some testing methods, the packet sending parameters also need to be gradually increased or decreased multiple times during the test.

[0063] For example, when sending request traffic, the test step size is set to 10000, and the packet sending rate is from 10000 / s to 50000 / s. The test is executed 3 times at each rate, and each test lasts for 5 minutes.

[0064] Step S103: Obtain the response traffic returned from the target object, then obtain the indicator data based on the baseline data, request traffic and response traffic, and determine the test result report of the target object based on the test request and indicator data.

[0065] The response traffic is the data stream returned by the DNS server (the target) after receiving request traffic from the test initiator. The metric data is an indicator used to evaluate the DNS server's domain name address service quality, calculated based on key information such as the timestamps of traffic collection, source and destination information, domain name request and response information obtained from the response traffic, combined with the test domain name set and the corresponding IP addresses and request traffic timestamps in the baseline data. The test result report is a report generated based on the metric type and display format specified in the test request, combined with some or all of the metric data.

[0066] It is understood that the benchmark data used for domain name resolution service testing in this embodiment is synchronized in real time from the target server periodically or at the start of the test in response to the test request. This avoids the time and labor costs of manually updating the benchmark data before each test and ensures the authority and timeliness of the information synchronized locally. Furthermore, the request traffic is generated based on the test request and the test domain set extracted from the benchmark data. The test domain set is extracted from the benchmark data based on the test request. Therefore, the test domain set used to generate the request traffic can be directly included in the test request or extracted from the benchmark data based on the test request. The test traffic can also be generated based on the test request and the test domain set, further reducing the workload of testers in manipulating the test traffic. Obtaining the response traffic returned from the target object, then obtaining indicator data based on the benchmark data, request traffic, and response traffic, and determining the test result report of the target object based on the test request and indicator data, means that after determining the test request, the acquisition of response traffic, related processing and analysis, and even the automatic calculation of key indicators and the generation of a test result report with key indicators can all be performed automatically. Moreover, the test result report can include various indicator data of the target object. Therefore, the domain name resolution service testing method in this application embodiment can improve the automation level of domain name resolution service testing, and improve testing efficiency and accuracy.

[0067] Please see Figure 3 In some embodiments, before extracting the test domain name set from the benchmark data according to the test request in step S101, the above-described domain name resolution service testing method may further include steps S201 to S202:

[0068] Step S201: Periodically or in response to a test request, synchronize the original dataset from the target server to the local machine. The original dataset includes domain name information, Internet Protocol address information corresponding to the domain name information, and domain name record type information.

[0069] Step S202: Classify the original dataset according to the domain name information and domain name record type information to obtain benchmark data for different categories;

[0070] The baseline data includes domain name information, as well as corresponding Internet Protocol address information and domain name record type information.

[0071] Specifically, the benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to a test request. In this embodiment, the benchmark data refers to data including domain names, their corresponding IP addresses, and domain name record types. The benchmark data, synchronized from the target server to the local machine, serves as a partial option for testers to select domain names for domain name resolution service testing and as a reference for calculating some key indicators in the final test results. The target server refers to an organization capable of providing accurate and comprehensive benchmark data. The test domain set is the set of domain names to be tested provided based on the test request or the set of domain names to be tested selected from the benchmark data based on the test request.

[0072] Specifically, in this embodiment, to ensure the authority and correctness of domain name information, information is not queried and collected from independent DNS servers, nor is the domain name manually assembled using functions or programs. Instead, the domain name information and its corresponding IP address are synchronized locally from the target server in real time, periodically or in response to test requests, through automated scripts. This ensures the authority, timeliness, and accuracy of the synchronized domain name information, i.e., the baseline data. The IP address information corresponding to the domain name serves as the baseline data for comparing test results, primarily as reference data for testing the correctness and consistency of the domain name resolution service. When a domain name resolution service under test returns a response to a domain name request, if the response matches the response in the baseline data, the IP address corresponding to the domain name in the response traffic returned by the DNS server is considered correct. Furthermore, the IP address information corresponding to the domain name may change over time, so the IP address information in the database, i.e., the baseline data, is a constantly updated and supplemented set. If the target server cannot directly provide all the corresponding IP address information, the collection module initiates domain name requests to multiple standard public domain name resolution services and collects the responding IP addresses. Through frequent access and updates, the set of IP address information is continuously expanded.

[0073] Please see Figure 4 In some embodiments, step S101 may include steps S301 to S302.

[0074] Step S301: Obtain the test request and extract the test category information from the test request;

[0075] Step S302: Select the benchmark data for the corresponding category based on the information of the category to be tested, and extract the test domain name set from the selected benchmark data.

[0076] The test request includes information about the category to be tested, which is used to associate the benchmark data of the preset category; the test request is obtained, and the test domain name set is extracted from the benchmark data according to the test request.

[0077] Furthermore, once the domain name service testing system completes information synchronization from the target server, the classification program, based on the domain name information in the obtained benchmark data, assigns corresponding type tags according to the domain name record type or the different top-level domains to which the domain name belongs, and records them in the database for easy retrieval by testers.

[0078] For example, before the test begins, the tester can select the domain names they want to test, that is, they can select a preset category of benchmark data through the test request. For example, they can select a specific type of domain names for testing in batches based on the type of domain name or the top-level domain to which the domain name belongs.

[0079] Please see Figure 5 In some embodiments, the domain name resolution service testing method of this application may further include steps S401 to S402 before step S101:

[0080] Step S401: After synchronizing the original dataset from the target server to the local machine, compare the baseline data with the original dataset synchronized to the local machine;

[0081] Step S402: If the Internet Protocol address information corresponding to the same domain name information in the original dataset is different from that in the baseline data, update the baseline data to add the different Internet Protocol address information to the baseline data and associate it with the domain name information in the baseline data.

[0082] Among them, the domain name information in the benchmark data can be associated with multiple Internet Protocol address information.

[0083] Furthermore, the test results report includes an accuracy rate, which is calculated by confirming whether the Internet Protocol address information corresponding to the same domain name information in the response traffic is included in the Internet Protocol address information associated with the same domain name information in the baseline data.

[0084] Furthermore, in this embodiment, to ensure the authority and correctness of domain name information, information is not queried and collected from independent DNS servers, nor is the domain name manually assembled using functions or programs. Instead, the domain name information and its corresponding IP address are synchronized locally from the target server in real time, periodically or in response to test requests, through automated scripts. This ensures the authority, timeliness, and accuracy of the synchronized domain name information, i.e., the benchmark data. The IP address information corresponding to the domain name serves as the benchmark data for comparing test results, primarily as reference data for testing the correctness and consistency of the domain name resolution service. When a domain name resolution service under test returns a response to a domain name request, if the response matches the response in the benchmark data, the IP address corresponding to the domain name in the response traffic returned by the DNS server is considered correct. In addition, the IP address information corresponding to the domain name may change over time, so the IP address information in the database, i.e., the benchmark data, is a constantly updated and supplemented set. If the target server cannot directly provide all the corresponding IP address information, the collection module initiates domain name requests to multiple standard public domain name resolution services and collects the responding IP addresses. Through frequent access and updates, the set of IP address information is continuously expanded.

[0085] For example, a domain name in the baseline data may be associated with one or more IP addresses, while the domain name to which the response traffic is sent corresponds to only one IP address. If the IP address corresponding to the domain name in the response traffic is the same IP address associated with the same domain name in the baseline data, or is included in multiple IP addresses associated with the same domain name in the baseline data, it can be determined that the DNS server's resolution for the domain name is correct.

[0086] Please see Figure 6 In some embodiments, step S102 may include steps S501 to S503:

[0087] Step S501: Obtain message configuration parameters and sending configuration parameters based on the test request and preset pre-configuration information;

[0088] Step S502: Generate a request message based on the message configuration parameters and the test domain name set;

[0089] Step S503: Generate request traffic based on the request message, and send the request traffic to the target object according to the sending configuration parameters;

[0090] The request traffic includes one or more request messages, and the sending configuration parameters are configured as static parameters or as dynamic parameters that are adjusted according to changes in network conditions or the testing phase.

[0091] Furthermore, the request message includes field information, including a test source field, a destination network protocol address field, a source field, a destination hardware address field, a domain name information field, and a control field. The request message is generated based on the message configuration parameters and the test domain name set. This can be achieved by determining the test source field, destination network protocol address field, source field, destination hardware address field, and control field based on the message configuration parameters, and determining the domain name information field based on the test domain name set. The request message is generated according to a preset message format and field information.

[0092] Please see Figure 7 In some embodiments, step S502 may include steps S601 to S603:

[0093] Step S601: Assemble the request message into request traffic;

[0094] Step S602: Confirm the number of tests, packet sending rate, and test step size according to the sending configuration parameters;

[0095] Step S603: Send request traffic to the target object based on the confirmed number of tests, packet sending rate, and test step size.

[0096] Specifically, the sending configuration parameters include the number of tests, the packet sending rate, and the test step size.

[0097] Furthermore, the request traffic is sent through a traffic generation program, which then sends the generated request traffic to the target network, namely the DNS server to be tested, through a hardware packet sending port.

[0098] Please see Figure 8 In some embodiments, step S502 may further include steps S702 to S702:

[0099] Step S701: When the sending configuration parameters are configured as dynamic parameters, determine the packet sending rate and test step size for this round of testing based on the current network conditions or the current number of tests, according to the sending configuration parameters.

[0100] Step S702: Send request traffic to the target object based on the confirmed packet sending rate and test step size.

[0101] It should be noted that since the test initiator and the test target may not be directly connected, but rather separated by other network devices, the sending program needs to identify network conditions and adjust its sending behavior accordingly. This includes considering factors such as network connectivity, gateway configuration, and firewall restrictions. Therefore, configuration parameters can be configured dynamically, changing based on network conditions or the testing process.

[0102] Meanwhile, in order to meet different testing needs, before sending packets, it is necessary to set parameters such as the packet sending rate and the number of tests for each test. In addition, in some testing methods, the packet sending parameters need to be increased or decreased gradually multiple times during the test.

[0103] For example, when sending request traffic, the test step size is set to 10000, and the packet sending rate is from 10000 / s to 50000 / s. The test is executed 3 times at each rate, and each test lasts for 5 minutes.

[0104] Please see Figure 9 In some embodiments, step S103 may include steps S801 to S803:

[0105] Step S801: Obtain the response traffic returned from the target object, process the response traffic according to the traffic collection type to obtain the collection result, and then save the collection result according to the storage type.

[0106] Step S802: Extract key information from the collection results, and then calculate indicator data based on the baseline data, request traffic, and key information;

[0107] Step S803: Determine the test result report for the target object based on the test request and indicator data.

[0108] The traffic collection type and storage type are either preset or confirmed based on the test request.

[0109] Furthermore, response traffic is the data stream returned by the DNS server (the target object) after receiving request traffic from the test initiator. Metric data is calculated based on key information obtained from the response traffic, such as the timestamp of traffic collection, source and destination information, domain name request and response information, combined with the test domain name set and the corresponding IP addresses and request traffic timestamps in the baseline data. This data is used to evaluate the quality of DNS server domain name address services. The test result report is a report generated based on the metric type and display format specified in the test request, combined with some or all of the metric data.

[0110] It is understandable that by acquiring the response traffic returned from the target object, obtaining indicator data based on baseline data, request traffic, and response traffic, and determining the test result report for the target object based on the test request and indicator data, it means that once the test request is determined, the acquisition of response traffic, related processing and analysis, and even the automatic calculation of key indicators and the generation of a test result report containing key indicators can all be performed automatically, and the test result report can include various indicator data of the target object. Therefore, the domain name resolution service testing method in this application embodiment can improve the automation level of domain name resolution service testing, and improve testing efficiency and accuracy.

[0111] Please see Figure 10 In some embodiments, the traffic collection type includes log type and raw traffic type, and the above step S801 may include steps S901 to S903:

[0112] Step S901: When the traffic collection type is configured as log type, acquire the response traffic and perform real-time decoding processing on the response traffic to obtain the log type collection result.

[0113] Step S902: When the traffic collection type is configured as raw traffic type, obtain the response traffic and obtain the raw traffic type collection result based on the response traffic;

[0114] Step S903: Based on the storage type, store the collected results locally or transfer them externally.

[0115] The raw traffic-type collection results are stored in the form of raw messages or compressed message packages. The storage type is used to select whether to store the collection results locally or externally. Alternatively, the storage type can be configured to automatically select local storage or external storage based on the current storage usage.

[0116] Furthermore, the domain name resolution service testing system in this application includes a traffic collection program. This program collects the response traffic returned by the DNS server under test through a packet receiving port. The collection method, or traffic collection type, is divided into log-type and raw traffic-type. Log-type requires real-time decoding of the response traffic and extracting key information to save as a fixed-format log. This method consumes more computing resources but less storage resources, and subsequent processing is simpler. Raw traffic-type does not require decoding; it directly stores the traffic as raw PCAP packets or compressed PCAP packets. This method consumes less computing resources but more storage resources, and subsequent decoding of the traffic packets is required, making processing more complex. Typically, the traffic is stored locally during testing. After the test data analysis is completed, the traffic stored locally is transferred to other external storage devices for a period of time, with multiple backups for redundancy, facilitating later review and retrieval.

[0117] For example, the domain name resolution service testing system in this application has a traffic saving program. The traffic saving program locally saves the collected response traffic and the issued request traffic. The saving format can be determined by the traffic collection type, and can include log format, raw traffic format, and other formats. In addition to periodically transferring traffic data to other storage devices, the program also needs to monitor the utilization rate of local storage space in real time. When the utilization rate reaches a threshold, it will immediately start the transfer function to transfer the stored data to external storage.

[0118] Please see Figure 11 In some embodiments, step S802 may include steps S1001 to S1003:

[0119] Step S1001: When the traffic collection type is configured as log type, extract key information directly from the log type collection results;

[0120] Step S1002: When the traffic collection type is configured as raw traffic type, decode the raw traffic type collection result and extract key information from the decoding result.

[0121] Step S1003: Calculate indicator data based on key information.

[0122] Furthermore, the metric data can also be calculated from baseline data, request traffic, key information, and sending records. The sending records are generated when request traffic is sent and are used to record the sending situation, including the sending time. The key information includes the receiving time of response traffic. The metric data includes packet sending rate, test time, number of requests, number of responses, maximum number of requests responded per unit time, number of valid responses, valid response rate, number of correct responses, accuracy rate, and latency.

[0123] Furthermore, the domain name resolution service testing system in this application includes a log data processing program, a traffic data processing program, and a result output program. If, during testing, data is selected to be collected and saved as a log, i.e., the traffic collection type is configured as log-based, then the log data processing program is used to process the log information. Since preliminary processing has already been performed in the collection program, the data processing program only needs to extract the log information to obtain key information such as the traffic collection timestamp, source and destination information, and domain name request and response information.

[0124] Furthermore, if the test selects to collect and save raw traffic (i.e., the traffic collection type is configured as raw traffic), then the traffic data processing program first decodes the traffic and extracts key information. After information extraction, relevant metrics need to be calculated.

[0125] It is understandable that both the traffic collection type and storage type can be determined by the test request, meaning that testers can select the traffic collection type and storage type before the test begins.

[0126] For example, the key metrics include: packet sending rate, test time, number of requests, number of requests per unit time, number of responses, maximum number of responses per unit time, number of valid responses, valid response rate, number of correct responses, accuracy rate, and latency.

[0127] The specific definitions of each calculation indicator are as follows:

[0128] The number of requests, which is the total number of all requests calculated statistically, is denoted as Q;

[0129] The number of responses, which is the total number of all responses calculated statistically, is denoted as R;

[0130] Response rate, which reflects the responsiveness of a domain name resolution service, is denoted as RR and is calculated using the formula: RR = R / Q;

[0131] Valid response count: When the number of responses exceeds the number of requests in the test data, it is necessary to use the requests as a benchmark to count the valid responses corresponding to the requests and calculate the valid response count, which is denoted as VR. Under normal circumstances, the calculation formula is VR = R.

[0132] The effective response rate, denoted as VRR, is calculated using the formula: VRR = VR / Q. Under normal circumstances, VRR = RR.

[0133] Requests per unit time (requests per second) is the maximum number of requests that the domain name resolution service can respond to per second, denoted as QPS. This data is a key indicator in performance testing, indicating the maximum service capacity of the domain name resolution service under certain response rate conditions. The calculation formula is: QPS = Q / T, where T is the test time. Multiple tests are required to determine the actual maximum QPS capacity based on the response rate.

[0134] Accuracy rate, also known as consistency rate, is the proportion of the number of records that match or are correct after comparing the content of the response with the standard records of the domain name collection module. It is denoted as A and is calculated by the formula: A = CR / BR, where CR is the number of records that match and BR is the total number of records that are compared. Generally, BR = VR. When the content of the response is a subset of the standard response content or is completely the same, it is considered to be consistent.

[0135] Latency, denoted as t, is the time difference between each request and its corresponding response. The formula for calculating latency is:

[0136]

[0137] TQi is the timestamp of a single request, and TRi is the timestamp of the corresponding single response. The latency data can be obtained by first calculating the sum of the time differences of all valid responses and then dividing by the total number of valid requests.

[0138] Furthermore, in addition to using the request traffic sending time from the transmission record, metric data, including latency, can also be calculated based solely on baseline data, request traffic, and key information. The sending time of the request traffic and the receiving time of the response traffic required to calculate the metric data can be determined by the sending timestamp in the request traffic and the receiving timestamp in the response traffic.

[0139] Please see Figure 12 In some embodiments, step S803 may include steps S1101 to S1102:

[0140] Step S1101: Determine the result template based on the test request and the preset report template. The result template is used to determine the type and format of the indicator data displayed in the test result report.

[0141] Step S1102: Generate a test result report based on the indicator data and result template.

[0142] For example, the test result report can be presented in a data processing table format according to the test request or report template, and the data table includes one or more of the above-mentioned indicator data.

[0143] For example, after the test is completed, the result output program of the domain name resolution service testing system generates a test result report based on the report template and sends it to the front-end display page for testers to view and download. The report template supports customization, allowing for the addition or removal of report items, or the addition of custom templates according to certain format requirements. Therefore, once the test request is determined, the acquisition of response traffic, related processing and analysis, and even the automatic calculation of key indicators and the generation of test result reports with key indicators can all be performed automatically. Furthermore, the test result report can include various indicator data of the target object. Therefore, the domain name resolution service testing method in this embodiment can improve the automation level of domain name resolution service testing, and improve testing efficiency and accuracy.

[0144] Understandably, the diverse evaluation metrics, i.e., various types of indicator data, fully meet the different needs of testers, enabling the evaluation of service capabilities from different perspectives. This demonstrates strong professionalism and a more comprehensive evaluation approach. These metrics accurately reflect the operational status of the target under test, providing users or administrators with an intuitive understanding of the overall state of the service under test, rather than simply using stress testing to assess whether it meets performance standards. The metrics listed in this application embodiment serve as a standardized feasibility testing benchmark, providing guidance to a certain extent for the evaluation and testing direction of domain name resolution services.

[0145] Please see Figure 13 This application also provides a domain name resolution service testing system, which can implement the above-described domain name resolution service testing method. The domain name resolution service testing system includes:

[0146] The domain name acquisition module 1301 is used to acquire test requests and extract a set of test domain names from the benchmark data based on the test requests;

[0147] The traffic behavior module 1302 is used to generate request traffic based on the test request and the test domain set, and send the request traffic to the target object;

[0148] The data processing module 1303 is used to obtain the response traffic returned from the target object, then obtain the indicator data based on the baseline data, request traffic and response traffic, and determine the test result report of the target object based on the test request and indicator data.

[0149] The baseline data is periodically synchronized from the target server to the local machine, or in response to a test request; the target object is determined by the test request.

[0150] It is understood that the benchmark data used for domain name resolution service testing in this embodiment is synchronized in real time from the target server periodically or at the start of the test in response to the test request. This avoids the time and labor costs of manually updating the benchmark data before each test and ensures the authority and timeliness of the information synchronized locally. Furthermore, the request traffic is generated based on the test request and the test domain set extracted from the benchmark data. The test domain set is extracted from the benchmark data based on the test request. Therefore, the test domain set used to generate the request traffic can be directly included in the test request or extracted from the benchmark data based on the test request. The test traffic can also be generated based on the test request and the test domain set, further reducing the workload of testers in manipulating the test traffic. Obtaining the response traffic returned from the target object, then obtaining indicator data based on the benchmark data, request traffic, and response traffic, and determining the test result report of the target object based on the test request and indicator data, means that after determining the test request, the acquisition of response traffic, related processing and analysis, and even the automatic calculation of key indicators and the generation of a test result report with key indicators can all be performed automatically. Moreover, the test result report can include various indicator data of the target object. Therefore, the domain name resolution service testing method in this application embodiment can improve the automation level of domain name resolution service testing, and improve testing efficiency and accuracy.

[0151] Furthermore, the baseline data is periodically synchronized from the target server to the local machine, or in response to a test request; the target object is determined by the test request; the domain name acquisition module 1301, the traffic behavior module 1302, and the data processing module 1303 can be deployed individually or together, and can be called via an interface.

[0152] Furthermore, the domain name acquisition module 1301 is primarily responsible for collecting, classifying, and storing internet domain name information and the corresponding IP address information. Domain name resolution service testing mainly involves access testing of various existing internet domain names. Through automation, it can update domain name information data in real-time or on a scheduled basis and store it in categories. The acquisition work of the domain name acquisition module 1301 mainly relies on a crawling program and a classification program. The crawling program is used to crawl domain name information, i.e., baseline data, from the target server. When the domain name service testing system completes information synchronization from the target server, the classification program, based on the domain name information in the obtained baseline data, tags it with corresponding type labels according to the domain name record type or the different top-level domains to which the domain name belongs, and records it in the database for easy retrieval by testers.

[0153] Furthermore, the traffic behavior module 1302 is primarily responsible for executing various operations related to test traffic. These operations include traffic generation, traffic transmission, traffic acquisition, and traffic storage, which are implemented by the traffic generation program, traffic transmission program, traffic acquisition program, and traffic storage program, respectively.

[0154] Furthermore, the data processing module 1303 is primarily responsible for processing and analyzing the test result data obtained during the test, and outputting a test report. This module includes a log data processing program, a traffic data processing program, and a result output program.

[0155] Furthermore, the domain name resolution service testing system also includes a front-end operation page: this module is mainly responsible for connecting various functional modules and displaying them through a graphical interface, making it convenient for testers to execute testing tasks. Testers can use this interface to query and select the set of domain names to be tested, configure test parameters, observe the testing process, and obtain test results.

[0156] For example, because modules can be set up independently or combined, and the functionality within a module can be divided into sub-modules, they can be customized for use, such as:

[0157] If testers only need the test domain set, they can log in to the system directly through the page and enter the domain collection module to download the domain set in common formats such as Excel or CSV for other research trials. If testers only need some simulated requests for other testing purposes, they can log in to the system directly through the page, enter the traffic behavior module, fill in the basic information to be assembled, and command the module to output simulated traffic packets for download for other research trials. If testers need to further study the parsing results of the service under test, they can log in to the system directly through the page, enter the data processing module, obtain the saved raw traffic data, and download it locally for further analysis and research. If testers do not need all the test data or need to update the report template, they can upload the template and add or remove test report content items through the data processing module. Each module can be used with automated programs through open interfaces, without necessarily requiring graphical interface operations. Modules can also meet special usage requirements such as cyclic testing or continuous monitoring. For example, by calling the module interface through the program, the traffic collection module and data processing module can be configured to work in a cycle, thus realizing iterative testing of the node under test.

[0158] It should be noted that each module of the domain name resolution service testing system in this application can be deployed individually or together, and can also be called individually or together through API. Therefore, testers' test-related operations can be implemented through front-end pages or API interfaces to achieve fully automated and smooth work. In summary, the domain name resolution service testing system in this application has a complete process and detailed task division, good openness, and can achieve one-stop full-process support for testing functions, and has high testing efficiency.

[0159] Please see Figure 14 , Figure 14 The hardware structure of a domain name resolution service testing apparatus according to another embodiment of this application is illustrated, including:

[0160] The processor 1401 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0161] The memory 1402 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1402 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1402 and is called and executed by the processor 1401 to execute the domain name resolution service testing method of the embodiments of this application.

[0162] The input / output interface 1403 is used to implement information input and output;

[0163] The communication interface 1404 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0164] Bus 1405 transmits information between various components of the device (e.g., processor 1401, memory 1402, input / output interface 1403, and communication interface 1404);

[0165] The processor 1401, memory 1402, input / output interface 1403 and communication interface 1404 are connected to each other within the device via bus 1405.

[0166] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described domain name resolution service testing method.

[0167] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0168] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0169] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0170] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0171] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0172] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0173] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0174] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0175] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0176] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0177] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0178] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method for testing domain name resolution services, characterized in that, include: Obtain the test request, and extract the test domain name set from the benchmark data according to the test request; Request traffic is generated based on the test request and the test domain set, and the request traffic is sent to the target object; Obtain the response traffic returned from the target object, then obtain the indicator data based on the baseline data, the request traffic, and the response traffic, and determine the test result report of the target object based on the test request and the indicator data; The benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to the test request; the target object is determined by the test request. Before extracting the test domain name set from the benchmark data according to the test request, the method further includes: Periodically or in response to the test request, the original dataset is synchronized from the target server to the local machine. The original dataset includes domain name information, Internet Protocol address information corresponding to the domain name information, and domain name record type information. After synchronizing the original dataset from the target server to the local machine, the benchmark data is compared with the original dataset synchronized to the local machine; If the Internet Protocol address information corresponding to the same domain name information in the original dataset is different from that in the benchmark data, the benchmark data is updated to add the different Internet Protocol address information to the benchmark data and associate it with the domain name information in the benchmark data; The domain name information in the benchmark data is associated with multiple Internet Protocol address information. The test result report includes an accuracy rate, which is calculated by confirming whether the Internet Protocol address information corresponding to the same domain name information in the response traffic is included in the Internet Protocol address information associated with the same domain name information in the benchmark data.

2. The domain name resolution service testing method according to claim 1, characterized in that, Before extracting the test domain name set from the benchmark data according to the test request, the method further includes: The original dataset is classified according to the domain name information and the domain name record type information to obtain the baseline data of different categories; The baseline data includes the domain name information, the corresponding Internet Protocol address information, and the domain name record type information.

3. The domain name resolution service testing method according to claim 2, characterized in that, The test request includes information about the category to be tested, which is used to associate the baseline data of the preset category; The step of obtaining the test request and extracting the test domain name set from the benchmark data according to the test request includes: Obtain the test request and extract the test category information from the test request; The benchmark data corresponding to the category to be tested is selected based on the category information to be tested, and the test domain name set is extracted from the selected benchmark data.

4. The domain name resolution service testing method according to claim 1, characterized in that, The request traffic includes one or more request messages; The step of generating request traffic based on the test request and the test domain name set, and sending the request traffic to the target object, includes: The message configuration parameters and sending configuration parameters are obtained based on the test request and the preset pre-configuration information; Generate a request message based on the message configuration parameters and the test domain name set; The request traffic is generated based on the request message, and the request traffic is sent to the target object according to the sending configuration parameters; The sending configuration parameters are configured as static parameters or as dynamic parameters that are adjusted according to changes in network conditions or testing phases.

5. The domain name resolution service testing method according to claim 4, characterized in that, The sending configuration parameters include the number of tests, packet sending rate, and test step size; the step of generating the request traffic based on the request message and sending the request traffic to the target object according to the sending configuration parameters includes: The request message is assembled into a request flow; Confirm the number of tests, packet sending rate, and test step size based on the aforementioned sending configuration parameters; The request traffic is sent to the target object based on the confirmed number of tests, packet sending rate, and test step size.

6. The domain name resolution service testing method according to claim 5, characterized in that, The step of generating the request traffic based on the request message and sending the request traffic to the target object according to the sending configuration parameters further includes: When the sending configuration parameters are configured as dynamic parameters, the packet sending rate and test step size for this round of testing are determined based on the current network conditions or the current number of tests, according to the sending configuration parameters. The request traffic is sent to the target object based on the confirmed packet sending rate and test step size.

7. The domain name resolution service testing method according to claim 1, characterized in that, The process of obtaining the response traffic returned from the target object, obtaining indicator data based on the baseline data, the request traffic, and the response traffic, and determining the test result report of the target object based on the test request and the indicator data includes: The system acquires the response traffic returned from the target object, processes the response traffic according to the traffic acquisition type to obtain the acquisition result, and then saves the acquisition result according to the storage type. Key information is extracted from the collected results, and then the indicator data is calculated based on the benchmark data, the request traffic, and the key information. The test result report for the target object is determined based on the test request and the indicator data; The traffic collection type and the storage type are either preset or confirmed based on the test request.

8. The domain name resolution service testing method according to claim 7, characterized in that, The traffic collection types include log type and raw traffic type. The process involves acquiring the response traffic returned from the target object, processing the response traffic according to the traffic collection type to obtain the collection result, and then saving the collection result according to the storage type. This includes: When the traffic collection type is configured as log type, the response traffic is acquired and the response traffic is decoded in real time to obtain the log type collection result; When the traffic acquisition type is configured as raw traffic type, the response traffic is acquired, and the raw traffic type acquisition result is obtained based on the response traffic; The collected results will be stored locally or transferred externally according to the storage type. The original traffic-type collection results are stored in the form of original packets or packet compression packages. The storage type is used to select whether to store the collection results locally or externally. Alternatively, the storage type can be configured to automatically select local storage or external storage based on the current storage usage.

9. The domain name resolution service testing method according to claim 8, characterized in that, The step of extracting key information from the collected results and then calculating the indicator data based on the baseline data, the request traffic, and the key information includes: When the traffic collection type is configured as log type, the key information is directly extracted from the log type collection results; When the traffic collection type is configured as raw traffic type, the raw traffic type collection result is decoded, and the key information is extracted from the decoding result; The indicator data is calculated based on the key information.

10. The domain name resolution service testing method according to claim 7, characterized in that, The indicator data is calculated from the baseline data, the request traffic, the key information, and the sending record. The sending record is generated when the request traffic is sent and is used to record the sending situation, including the sending time. The key information includes the receiving time of the response traffic. The indicator data includes packet sending rate, test time, number of requests, number of responses, maximum number of requests responded per unit time, number of valid responses, valid response rate, number of correct responses, accuracy rate, and latency.

11. The domain name resolution service testing method according to claim 10, characterized in that, The step of determining the test result report of the target object based on the test request and the indicator data includes: The result template is determined based on the test request and the preset report template. The result template is used to determine the type and display format of the indicator data displayed in the test result report. The test result report is generated based on the indicator data and the result template.

12. A domain name resolution service testing system, characterized in that, include: The domain name acquisition module is used to obtain test requests and extract a set of test domain names from the benchmark data based on the test requests; The traffic behavior module is used to generate request traffic based on the test request and the test domain set, and send the request traffic to the target object; The data processing module is used to acquire the response traffic returned from the target object, obtain indicator data based on the baseline data, the request traffic and the response traffic, and determine the test result report of the target object based on the test request and the indicator data. The benchmark data is periodically synchronized from the target server to the local machine, or synchronized from the target server to the local machine in response to the test request; the target object is determined by the test request.

13. A domain name resolution service testing device, characterized in that, The testing apparatus includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the domain name resolution service testing method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, include: The storage medium stores a computer program, which, when executed by a processor, implements the domain name resolution service testing method according to any one of claims 1 to 11.

Citation Information

Patent Citations

  • Domain name resolution information management method, device and system

    CN108076165A

  • Domain name resolution method and system, and credit domain name system server

    CN109246256A