Dual-stack domain name access experience evaluation method, device, equipment and storage medium

Abstract

The present invention belongs to the field of Internet communication technology and discloses a dual-stack domain name access experience evaluation method. The present invention parses DNS original logs to obtain a resolved IP address of a first DNS record and a resolved IP address of a second DNS record, determines the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record according to an IP address classification standard, compares the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record, and when the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record are aggregated and output to obtain a domain name list, obtain access evaluation results based on the domain name list, and screen out a list of poor-quality domain names and evaluation results from a large number of domain names at a low cost.

Description

Technical Field

[0001] The present invention relates to the field of Internet communication technology, and in particular to a dual-stack domain name access experience evaluation method, device, equipment and storage medium. Background Art

[0002] With the development of IPv6 services, ensuring user internet access quality has become a key criterion for the value of DNS systems. However, the quality of service between IPv4 and IPv6 resources varies. This is primarily due to differences in network latency between IPv4 and IPv6 resource nodes and user endpoints, as well as differences in service capabilities within IPv4 and IPv6 resource nodes. Currently, there are two primary methods for detecting poor quality in dual-stack domain names: one based on DPI detection technology, and the other using probes to analyze and track dual-stack resolution results for specific domain names. The first approach is costly and, to save on construction costs, is typically deployed only on the uplink of core equipment, making it difficult to extend to the access layer and creating monitoring blind spots. The second approach, on the other hand, relies on intelligent testing after identifying specific observation targets, making it impossible to conduct large-scale investigations and demonstrations. Consequently, current technologies suffer from high deployment costs, monitoring blind spots, and the inability to conduct large-scale investigations. Summary of the Invention

[0003] The main purpose of the present invention is to provide a dual-stack domain name access experience evaluation method, device, equipment and storage medium, aiming to solve the technical problem that the existing technology cannot comprehensively and extensively check the poor quality of dual-stack domain names.

[0004] To achieve the above objectives, the present invention provides a method for evaluating dual-stack domain name access experience, the method comprising the following steps:

[0005] Parse the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record;

[0006] Determining, according to an IP address classification standard, a home location priority corresponding to the resolved IP address of the first DNS record and a home location priority corresponding to the resolved IP address of the second DNS record;

[0007] comparing the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record; and if the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list;

[0008] An access evaluation result is obtained according to the domain name list.

[0009] Optionally, parsing the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record includes:

[0010] Copy the DNS original log by mirroring or splitting;

[0011] Parsing the DNS original log to obtain the domain name, request type and resolved IP address;

[0012] Filtering the DNS original log according to the request type to obtain response log information of a first DNS record request type and response log information of a second DNS record request type;

[0013] The resolved IP address of the first DNS record and the resolved IP address of the second DNS record are obtained according to the response log information of the first DNS record and the response log information of the second DNS record.

[0014] Optionally, determining, according to an IP address classification standard, a home location priority corresponding to the resolved IP address of the first DNS record and a home location priority corresponding to the resolved IP address of the second DNS record includes:

[0015] Matching the resolved IP address of the first DNS record and the resolved IP address of the second DNS record with the IP address classification standard, and determining the home locations corresponding to the resolved IP address of the first DNS record and the resolved IP address of the second DNS record according to the matching result;

[0016] The home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are determined according to the home location.

[0017] Optionally, the comparing the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record, when the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list, including:

[0018] Determine, according to the domain name, the corresponding resolved IP address of the first DNS record and the resolved IP address of the second DNS record;

[0019] Comparing the home location priority corresponding to the resolved IP address of the first DNS record with the home location priority corresponding to the resolved IP address of the second DNS record to obtain a comparison result;

[0020] When the comparison result shows that the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, updating the current domain name to the abnormal domain name list;

[0021] Repeat the step of determining the corresponding resolved IP address of the first DNS record and the resolved IP address of the second DNS record according to the domain name until all domain names are traversed.

[0022] Optionally, when the comparison result shows that the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, updating the current domain name to the abnormal domain name list includes:

[0023] The domain name, the resolved IP address of the first DNS record corresponding to the domain name, and the resolved IP address of the second DNS record are updated to the abnormal domain name list.

[0024] Optionally, after obtaining the access evaluation result according to the domain name list, the method further includes:

[0025] Counting traffic behaviors corresponding to the domain names according to the domain name list;

[0026] Identifying the traffic behavior and obtaining an IPv6 address segment where the traffic behavior is greater than a threshold;

[0027] Perform DNS reverse analysis on the domain name to obtain the IPv4 address segment;

[0028] Detecting data packets corresponding to the IPv6 address segment and data packets corresponding to the IPv4 address segment to obtain distribution differences between IPv4 and IPv6;

[0029] The quality of service is verified based on the distribution difference.

[0030] Optionally, after obtaining the access evaluation result according to the domain name list, the method further includes:

[0031] The domain name is tested using a deployed probe to obtain the quality differences and fluctuations of the domain name in IPv4 and IPv6;

[0032] The service quality of the domain name is verified according to the difference and the fluctuation.

[0033] In addition, to achieve the above-mentioned purpose, the present invention further proposes a dual-stack domain name access experience evaluation device, the dual-stack domain name access experience evaluation device comprising:

[0034] A log parsing module, configured to parse the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record;

[0035] An address resolution module, configured to determine, according to an IP address classification standard, a home location priority corresponding to the resolved IP address of the first DNS record and a home location priority corresponding to the resolved IP address of the second DNS record;

[0036] a priority comparison module, configured to compare the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record, and, when the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list;

[0037] The access evaluation module is used to obtain an access evaluation result according to the domain name list.

[0038] In addition, to achieve the above-mentioned purpose, the present invention also proposes a dual-stack domain name access experience evaluation device, which includes: a memory, a processor, and a dual-stack domain name access experience evaluation program stored on the memory and runnable on the processor, and the dual-stack domain name access experience evaluation program is configured to implement the steps of the dual-stack domain name access experience evaluation method described above.

[0039] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which a dual-stack domain name access experience evaluation program is stored. When the dual-stack domain name access experience evaluation program is executed by a processor, the steps of the dual-stack domain name access experience evaluation method described above are implemented.

[0040] The present invention parses the DNS original log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record, determines the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record according to the IP address classification standard, compares the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record, and when the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, summarizes and outputs the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list, obtains an access evaluation result based on the domain name list, screens out a list of domain names suspected of poor quality from a large number of domain names at a minimum cost, and obtains an evaluation result. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a structural diagram of a dual-stack domain name access experience evaluation device in a hardware operating environment involved in an embodiment of the present invention;

[0042] Figure 2 This is a flow chart of a first embodiment of a dual-stack domain name access experience evaluation method according to the present invention;

[0043] Figure 3 This is a flow chart of a second embodiment of the dual-stack domain name access experience evaluation method of the present invention;

[0044] Figure 4 This is a business flow chart of an embodiment of a dual-stack domain name access experience evaluation method of the present invention;

[0045] Figure 5 This is a structural block diagram of the first embodiment of the dual-stack domain name access experience evaluation device of the present invention.

[0046] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings and in conjunction with the embodiments. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0048] Reference Figure 1 , Figure 1 This is a schematic diagram of the structure of a dual-stack domain name access experience evaluation device in a hardware operating environment according to an embodiment of the present invention.

[0049] like Figure 1As shown, the dual-stack domain name access experience evaluation device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the user interface 1003 may optionally include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0050] Those skilled in the art will understand that Figure 1 The structure shown in the figure does not constitute a limitation on the dual-stack domain name access experience evaluation device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0051] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a dual-stack domain name access experience evaluation program.

[0052] exist Figure 1 In the dual-stack domain name access experience evaluation device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the dual-stack domain name access experience evaluation device of the present invention can be set in the dual-stack domain name access experience evaluation device, and the dual-stack domain name access experience evaluation device calls the dual-stack domain name access experience evaluation program stored in the memory 1005 through the processor 1001, and executes the dual-stack domain name access experience evaluation method provided in the embodiment of the present invention.

[0053] The embodiment of the present invention provides a dual-stack domain name access experience evaluation method, referring to Figure 2 , Figure 2 This is a flow chart of a first embodiment of a dual-stack domain name access experience evaluation method according to the present invention.

[0054] In this embodiment, the dual-stack domain name access experience evaluation method includes the following steps:

[0055] Step S10: Parse the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record.

[0056] It should be noted that the executor of this embodiment is a dual-stack domain name access experience evaluation device, wherein the dual-stack domain name access experience evaluation device has functions such as data processing, data communication and program running. The dual-stack domain name access experience evaluation device can be an integrated controller, a control computer and other devices. Of course, it can also be other devices with similar functions. This embodiment does not limit this.

[0057] It should be understood that the first DNS record refers to the DNS record type obtained after parsing the DNS raw log, which is an A record type, and the second DNS record refers to the AAAA record type of the DNS record. The A record type is the DNS type in the DNS corresponding to the IPv4 domain name, and the AAAA record type is the DNS type in the DNS corresponding to the IPv6 domain name. With the advancement of IPv6 networks, more and more website resources and user terminals support IPv6 access. Terminals that support dual stack will simultaneously initiate A and AAAA requests when initiating DNS query requests. If a second DNS record is returned, the terminal will prefer AAAA for access.

[0058] In a specific implementation, the DNS log fields are composed of: user IP | requested domain name | resolution time | A record resolution address | resolution result code | requested DNS record type | cname | AAAA record resolution address | business IP. When parsing the original DNS log, you need to first capture the original DNS log, obtain the original DNS log list, and parse the original DNS logs one by one to read the requested DNS record type in the original DNS log. The DNS record type can be an A record type or an AAAA record type. The A record type is the DNS type in the DNS corresponding to the IPv4 domain name, and the AAAA record type is the DNS type in the DNS corresponding to the IPv6 domain name. Based on the obtained DNS record type, determine the location of the resolution address that needs to be identified. If the current request type of the original DNS log is an A record type, then parse the location of the A record resolution address to obtain the resolution IP address corresponding to the A record. Similarly, if the current request type of the original DNS log is an AAAA record type, then parse the location of the AAAA record resolution address to obtain the resolution IP address corresponding to the AAAA record.

[0059] Step S20: Determine the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record according to the IP address classification standard.

[0060] It should be noted that the IP address classification standard is a distribution list for classifying IP addresses. In order to facilitate IP address management, IP addresses of different affiliations are assigned a range of IP addresses. For example, 1.1.1.1 / 16 is assigned to A affiliation and 1.2.0.1 / 16 is assigned to B affiliation. At this time, the location corresponding to the current IP address can be determined based on the IP address.

[0061] In the specific implementation, the currently resolved IP address is matched according to the preset address segment information transmitted externally, so as to determine the current address ownership, and determine the priority according to the current address ownership. When determining the current address ownership, the address ownership can be classified into three types of address ownership: within the province, outside the province, and outside the network, and the priority is set to the highest priority within the province and the lowest priority outside the network according to the address ownership.

[0062] Step S30: Compare the place priority corresponding to the resolved IP address of the first DNS record and the place priority corresponding to the resolved IP address of the second DNS record. When the place priority corresponding to the resolved IP address of the first DNS record and the place priority corresponding to the resolved IP address of the second DNS record are inconsistent, summarize and output the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list.

[0063] In a specific implementation, for the same domain name, there are differences in the IP addresses corresponding to IPv4 and IPv6, and different IP addresses may have different content sources. Therefore, for a better access experience, users need to give priority to accessing the content source that is closest. When comparing the location priority corresponding to the resolved IP address of the first DNS record of the same domain name with the location priority corresponding to the resolved IP address of the second DNS record, if the location priority corresponding to the resolved IP address of the first DNS record and the location priority corresponding to the resolved IP address of the second DNS record are inconsistent, the current domain name is filtered out, and all filtered domain names are summarized to obtain a domain name list, wherein the domain names included in the domain name list are all domain names whose location priority corresponding to the resolved address corresponding to the first DNS record and the location priority corresponding to the resolved address corresponding to the second DNS record are inconsistent.

[0064] Step S40: obtaining access evaluation results according to the domain name list.

[0065] It should be noted that the access evaluation result refers to the result of inconsistent resolution location priorities of IPv4 and IPv6 in the domain name list, which specifically includes the specific differences in the resolution location priorities of IPv4 and IPv6, for example, the resolution location priority of IPv4 is higher than that of IPv6.

[0066] Furthermore, after obtaining the access evaluation result according to the domain name list, the method further includes:

[0067] Counting traffic behaviors corresponding to the domain names according to the domain name list;

[0068] Identifying the traffic behavior and obtaining an IPv6 address segment where the traffic behavior is greater than a threshold;

[0069] Perform DNS reverse analysis on the domain name to obtain the IPv4 address segment;

[0070] Detecting data packets corresponding to the IPv6 address segment and data packets corresponding to the IPv4 address segment to obtain distribution differences between IPv4 and IPv6;

[0071] The quality of service is verified based on the distribution difference.

[0072] In the specific implementation, the domain names counted in the domain name list are detected through DPI detection technology. DPI detection technology, namely deep data packet inspection technology, is different from ordinary message detection which only analyzes the IP five-tuple (source address, destination address, source port, destination port and protocol type) of the data message. In addition to supporting the above-mentioned message parsing, DPI can also identify various application types and their contents and perform business statistics, as well as statistics on traffic behavior within a certain period of time, including traffic flow direction, business proportion, hot visited websites, etc. It is necessary to count the IPv6 address segments with larger traffic, and then use other means to reversely check their domain names, such as using DNS reverse solution, and then deduce them to the IPv4 address segment. Then, after obtaining the difference in the IPv4 and IPv6 distribution of the destination domain name, the delay data in DPI is used to analyze the resolution quality of the domain name.

[0073] Furthermore, after obtaining the access evaluation result according to the domain name list, the method further includes:

[0074] The domain name is tested using the deployed probe to obtain the quality difference and fluctuation of the domain name in IPv4 and IPv6;

[0075] The service quality of the domain name is verified according to the difference and the fluctuation.

[0076] In the specific implementation, the dual-stack resolution results of specific domain names are analyzed and tracked based on probes. That is, the Internet probes are first deployed, and then the domain names in the domain name list are centrally dialed to accurately record the quality differences and fluctuations of the domain names in the IPv4 and IPv6 environments, and the service quality of the domain names is determined based on the quality differences and fluctuations.

[0077] This embodiment parses the DNS original log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record, and determines the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record according to the IP address classification standard, and compares the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record. When the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record are summarized and output to obtain a domain name list, and an access evaluation result is obtained based on the domain name list. A list of domain names suspected of poor quality is screened out from a large number of domain names at a minimum cost, and an evaluation result is obtained.

[0078] refer to Figure 3 , Figure 3 This is a flow chart of a second embodiment of a dual-stack domain name access experience evaluation method according to the present invention.

[0079] Based on the first embodiment described above, step S10 of the dual-stack domain name access experience evaluation method of this embodiment includes:

[0080] Step S101: copying the DNS original log by mirroring or splitting;

[0081] Step S102: Parse the DNS original log to obtain the domain name, request type, and resolved IP address;

[0082] Step S103: filtering the DNS original log according to the request type to obtain response log information of a request type of A record and response log information of a request type of AAAA record;

[0083] Step S104: Obtain the resolved IP address of the A record and the resolved IP address of the AAAA record according to the response log information of the A record and the response log information of the AAAA record.

[0084] In the specific implementation, refer to Figure 4 , Figure 4This is a business process diagram. Receive DNS traffic copied by mirroring or splitting, parse the user request domain name, request type Rdata, resolution IP and other field information from the DNS response message, and filter the response message based on the request type, filtering out response log information with a request type of A (type=1) and a non-empty result field; filter out response logs with a request type of 4A (type=28) and a non-empty result field, that is, filter out log information with A and 4A resolution records. And obtain the resolution IP address of the A record and the resolution IP address of the AAAA record based on the response log information of the A record and the response log information of the AAAA record.

[0085] Furthermore, determining the home location priority corresponding to the resolved IP address of the A record and the home location priority corresponding to the resolved IP address of the AAAA record according to the IP address classification standard includes:

[0086] Matching the resolved IP address of the A record and the resolved IP address of the AAAA record with the IP address classification standard, and determining the home locations corresponding to the resolved IP address of the A record and the resolved IP address of the AAAA record according to the matching result;

[0087] The priority of the home location corresponding to the resolved IP address of the A record and the priority of the home location corresponding to the resolved IP address of the AAAA record are determined according to the home location.

[0088] In the specific implementation, the resolved IP corresponding to the A and AAAA records is matched with the pre-configured address segment information. Finally, the attribution priority of the resolved IP is divided into three types of groups: within the network and within the province, within the network and outside the province, and outside the network. The preset address segment information is shown in Table 1:

[0089] Table 1:

[0090]

[0091]

[0092] After comparing the domain name resolution results with the pre-configured IP address segments, the IP addresses that fall into the specified IP address segment are sorted first, while other IP addresses are retained and sorted after the IP addresses that fall into the specified IP address segment. The specific requirements are as follows:

[0093] (1) Compare the resolution result with the specified IP address segment. When returning the resolution result to the user, encapsulate the IP addresses that fall into the specified IP address segment at the front of the address list in the reply message, and the IP addresses that do not fall into the specified IP address segment are placed at the back.

[0094] (2) If there is no IP address corresponding to the specified IP address segment in the resolution result, a direct reply is given to the requesting user.

[0095] (3) Support the configurability of corresponding IP address segments to adapt to changes in user network segments.

[0096] The mainstream DNS software on the current network implements the above sorting method through the sortlist statement.

[0097] Distance can be reflected through network latency. Based on empirical data, ping latency for resources within the same carrier within the same province (hereinafter referred to as "intra-province") is generally less than 20 milliseconds, and for resources within the same carrier between provinces (hereinafter referred to as "intra-network"), the ping latency is less than 40 milliseconds. However, ping latency for resources outside of a carrier's network (hereinafter referred to as "extra-network") often exceeds 60 milliseconds, not considering the impact of local interconnection points. In theory, lower latency improves user experience. Based on this, domain name resolution location priority is typically categorized into three categories: intra-province, intra-network (extra-province), and extra-network. DNS sortlist policies are configured to prioritize resolved IP addresses in the order of "intra-province first, intra-network second, and extra-network last" before returning them to users. DNS sortlist policies apply not only to IPv4 but also to IPv6. If the resolution location priority for IPv4 and IPv6 is the same, and given that there are generally no service bottlenecks within resource nodes, the quality of service for dual-stack domain name resources can be considered equal.

[0098] When expressing the priority of the place of origin, it can be represented by the numerical values ​​3, 2, and 1 respectively. The larger the value, the higher the priority. If the A record set of a domain name corresponds to multiple priorities, only the highest priority is taken. Similarly, if the AAAA record set of a domain name corresponds to multiple priorities, only the highest priority is taken. The determination of the priority of the address resolution of the domain name A record and 4A record is shown in Table 2:

[0099] Table 2:

[0100]

[0101]

[0102] Furthermore, the attribution priority corresponding to the resolved IP address of the A record and the attribution priority corresponding to the resolved IP address of the AAAA record are compared. When the attribution priority corresponding to the resolved IP address of the A record and the attribution priority corresponding to the resolved IP address of the AAAA record are inconsistent, the domain names corresponding to the resolved IP address of the A record or the resolved IP address of the AAAA record are summarized and output to obtain a domain name list, including:

[0103] Determine the corresponding resolved IP address of the A record and the resolved IP address of the AAAA record according to the domain name;

[0104] Compare the priority of the home location corresponding to the resolved IP address of the A record with the priority of the home location corresponding to the resolved IP address of the AAAA record to obtain a comparison result;

[0105] When the comparison result shows that the priority of the home location corresponding to the resolved IP address of the A record is inconsistent with the priority of the home location corresponding to the resolved IP address of the AAAA record, updating the current domain name to the abnormal domain name list;

[0106] Repeat the steps of determining the corresponding resolved IP address of the A record and the resolved IP address of the AAAA record according to the domain name until all domain names are traversed.

[0107] In the specific implementation, it is determined whether the attribution priorities of the A record and the AAAA record are consistent. If they are consistent, no analysis is performed; if they are inconsistent, the data is analyzed in the next step. When comparing the attribution priorities, the attribution priorities of the A record and the AAAA record of the same domain name are used to determine if the two priorities are the same. Otherwise, the comparison result is consistent. The comparison content is shown in Table 3:

[0108] Table 3:

[0109] domain name A record attribution priority 4A Record Attribution Priority Is it consistent www.test.com within the province within the province Consistency www.testl.com within the province Out of province Inconsistency www.test2.com Out of province Off-net Inconsistency

[0110] Furthermore, when the comparison result shows that the priority of the home location corresponding to the resolved IP address of the A record is inconsistent with the priority of the home location corresponding to the resolved IP address of the AAAA record, updating the current domain name to the abnormal domain name list includes:

[0111] The domain name, the resolved IP address of the A record corresponding to the domain name, and the resolved IP address of the AAAA record are updated to the abnormal domain name list.

[0112] In the specific implementation, the inconsistent attribution priority data is summarized and output according to the precise domain name dimension. If the resolution attribution priority of A and AAAA is "inconsistent", the following four scenarios exist. Among them, it is particularly found that the resolution attribution priority of the AAAA record is lower than the domain name of the A record, that is, "Scenario 1" and "Scenario 2". The three types of within the network and province, within the network and province, and outside the network are represented by the numerical values ​​3, 2, and 1 in the table below. The higher the value, the higher the priority. If the resolution attribution priority of IPv4 and IPv6 is different, there may be a quality difference. The quality difference can be divided into two scenarios: IPv4 is inferior to IPv6 or IPv6 is inferior to IPv4.

[0113] Taking into account

[0114] (1) Content resource providers have been operating IPv4 for many years, and their layout is in place and stable, while the layout of IPv6 resource nodes is still being actively promoted, and scheduling changes frequently.

[0115] (2) When a domain name resource has dual-stack resolution results, the business layer often gives priority to accessing IPv6 resources in accordance with RFC standard recommendations.

[0116] In summary, we should pay more attention to the problem that the resolution priority of AAAA records is lower than that of A records. The results of the comparison of the resolution priority are shown in Table 4:

[0117] Table 4:

[0118]

[0119] And output the inconsistent domain name information, including domain name, A record resolution IP address, AAAA record resolution IP address. The specific output content is shown in 5:

[0120] Table 5:

[0121]

[0122]

[0123] Furthermore, when outputting dual-stack domain name resolution quality information, you can also associate it with ICP filing information to output a richer field display. An example of outputting the primary domain name display is shown in Table 6:

[0124] Table 6:

[0125]

[0126] This embodiment classifies IP addresses by referring to empirical data on network delays, and configures corresponding optimization strategies in LDNS. For example, IP addresses are classified into three priorities of "within the province, outside the province, and outside the network", and the optimization strategy configured in LDNS is "within the province first, within the network second, and outside the network last". Secondly, the resolution attribution priorities of the dual-stack domain name A and AAAA records are calculated separately based on the DNS resolution log. If the two are inconsistent, there may be poor quality. Focus on domain names where the resolution attribution priority of the AAAA record is lower than that of the A record. Finally, the home broadband DPI is linked to retrieve the URL, the dialing test system is linked to perform probe dialing, and the signaling analysis system is linked to verify the domain name service quality, thereby achieving tracking and verification of suspected poor quality domain names.

[0127] In addition, an embodiment of the present invention further proposes a storage medium, on which a dual-stack domain name access experience evaluation program is stored. When the dual-stack domain name access experience evaluation program is executed by a processor, the steps of the dual-stack domain name access experience evaluation method described above are implemented.

[0128] Reference Figure 5 , Figure 5 This is a structural block diagram of the first embodiment of the dual-stack domain name access experience evaluation device of the present invention.

[0129] like Figure 5 As shown, the dual-stack domain name access experience evaluation device proposed in an embodiment of the present invention includes:

[0130] The log parsing module 10 is used to parse the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record;

[0131] An address resolution module 20 is configured to determine, according to an IP address classification standard, a home location priority corresponding to the resolved IP address of the first DNS record and a home location priority corresponding to the resolved IP address of the second DNS record;

[0132] a priority comparison module 30 configured to compare the home location priority corresponding to the resolved IP address of the first DNS record with the home location priority corresponding to the resolved IP address of the second DNS record, and, if the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list;

[0133] The access evaluation module 40 is configured to obtain an access evaluation result according to the domain name list.

[0134] This embodiment parses the DNS original log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record, and determines the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record according to the IP address classification standard, and compares the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record. When the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record are summarized and output to obtain a domain name list, and an access evaluation result is obtained based on the domain name list. A list of domain names suspected of poor quality is screened out from a large number of domain names at a minimum cost, and an evaluation result is obtained.

[0135] In one embodiment, the log parsing module 10 is further used to copy the DNS original log by mirroring or splitting; parse the DNS original log to obtain a domain name, a request type, and a resolved IP address; filter the DNS original log according to the request type to obtain response log information of a request type of the first DNS record and response log information of a request type of the second DNS record; obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record based on the response log information of the first DNS record and the response log information of the second DNS record.

[0136] In one embodiment, the address resolution module 20 is further used to match the resolved IP address of the first DNS record and the resolved IP address of the second DNS record with the IP address classification standard, and determine the home locations corresponding to the resolved IP address of the first DNS record and the resolved IP address of the second DNS record based on the matching results; and determine the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record based on the home locations.

[0137] In one embodiment, the priority comparison module 30 is further used to determine the corresponding resolved IP address of the first DNS record and the resolved IP address of the second DNS record based on the domain name; compare the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record to obtain a comparison result; when the comparison result is that the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, update the current domain name to the abnormal domain name list; repeat the steps of determining the corresponding resolved IP address of the first DNS record and the resolved IP address of the second DNS record based on the domain name until all domain names are traversed.

[0138] In one embodiment, the priority comparison module 30 is further configured to update the domain name and the resolved IP address of the first DNS record and the resolved IP address of the second DNS record corresponding to the domain name to the abnormal domain name list.

[0139] In one embodiment, the access evaluation module 40 is further used to count the traffic behavior corresponding to the domain name based on the domain name list; identify the traffic behavior to obtain the IPv6 address segment where the traffic behavior is greater than a threshold; perform DNS reverse decoding on the domain name to obtain the IPv4 address segment; detect the data packets corresponding to the IPv6 address segment and the data packets corresponding to the IPv4 address segment to obtain the distribution difference between IPv4 and IPv6; and verify the service quality based on the distribution difference.

[0140] In one embodiment, the access evaluation module 40 is further configured to perform a test on the domain name through a deployed probe to obtain quality differences and fluctuations of the domain name in IPv4 and IPv6; and verify the service quality of the domain name based on the differences and fluctuations.

[0141] It should be understood that the above is only an example and does not constitute any limitation to the technical solution of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any limitation on this.

[0142] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0143] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of the present invention. In practical applications, technicians in this field can select part or all of it according to actual needs to achieve the purpose of the embodiment scheme, and no limitation is made here.

[0144] In addition, it should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0145] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0146] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, or of course by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as a read-only memory (ROM) / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0147] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention description and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A dual-stack domain name access experience evaluation method, characterized in that: The dual-stack domain name access experience evaluation method includes: Parse the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record; Determining, according to an IP address classification standard, a home location priority corresponding to the resolved IP address of the first DNS record and a home location priority corresponding to the resolved IP address of the second DNS record; comparing the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record; and if the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list; An access evaluation result is obtained according to the domain name list.

2. The method according to claim 1, wherein The parsing of the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record includes: Copy the DNS original log by mirroring or splitting; Parsing the DNS original log to obtain the domain name, request type and resolved IP address; Filtering the DNS original log according to the request type to obtain response log information of a first DNS record request type and response log information of a second DNS record request type; The resolved IP address of the first DNS record and the resolved IP address of the second DNS record are obtained according to the response log information of the first DNS record and the response log information of the second DNS record.

3. The method according to claim 1, wherein The determining, according to the IP address classification standard, the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record includes: Matching the resolved IP address of the first DNS record and the resolved IP address of the second DNS record with the IP address classification standard, and determining the home locations corresponding to the resolved IP address of the first DNS record and the resolved IP address of the second DNS record according to the matching result; The home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are determined according to the home location.

4. The method according to claim 1, wherein The comparing the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record, and when the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting the domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list, including: Determine, according to the domain name, the corresponding resolved IP address of the first DNS record and the resolved IP address of the second DNS record; Comparing the home location priority corresponding to the resolved IP address of the first DNS record with the home location priority corresponding to the resolved IP address of the second DNS record to obtain a comparison result; When the comparison result shows that the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, updating the current domain name to the abnormal domain name list; Repeat the step of determining the corresponding resolved IP address of the first DNS record and the resolved IP address of the second DNS record according to the domain name until all domain names are traversed.

5. The method according to claim 4, wherein When the comparison result shows that the home priority corresponding to the resolved IP address of the first DNS record and the home priority corresponding to the resolved IP address of the second DNS record are inconsistent, updating the current domain name to the abnormal domain name list includes: The domain name, the resolved IP address of the first DNS record corresponding to the domain name, and the resolved IP address of the second DNS record are updated to the abnormal domain name list.

6. The method according to claim 1, wherein After obtaining the access evaluation result according to the domain name list, the method further includes: Counting traffic behaviors corresponding to the domain names according to the domain name list; Identifying the traffic behavior and obtaining an IPv6 address segment where the traffic behavior is greater than a threshold; Perform DNS reverse analysis on the domain name to obtain the IPv4 address segment; Detecting data packets corresponding to the IPv6 address segment and data packets corresponding to the IPv4 address segment to obtain distribution differences between IPv4 and IPv6; The quality of service is verified based on the distribution difference.

7. The method according to claim 1, wherein After obtaining the access evaluation result according to the domain name list, the method further includes: The domain name is tested using the deployed probe to obtain the quality difference and fluctuation of the domain name in IPv4 and IPv6; The service quality of the domain name is verified according to the difference and the fluctuation.

8. A dual-stack domain name access experience evaluation device, characterized in that: The dual-stack domain name access experience evaluation device includes: The log parsing module is used to parse the original DNS log to obtain the resolved IP address of the first DNS record and the resolved IP address of the second DNS record; An address resolution module, configured to determine, according to an IP address classification standard, a home location priority corresponding to the resolved IP address of the first DNS record and a home location priority corresponding to the resolved IP address of the second DNS record; a priority comparison module, configured to compare the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record, and, when the home location priority corresponding to the resolved IP address of the first DNS record and the home location priority corresponding to the resolved IP address of the second DNS record are inconsistent, aggregating and outputting domain names corresponding to the resolved IP address of the first DNS record or the resolved IP address of the second DNS record to obtain a domain name list; The access evaluation module is used to obtain an access evaluation result according to the domain name list.

9. A dual-stack domain name access experience evaluation device, characterized in that: The device includes: a memory, a processor, and a dual-stack domain name access experience evaluation program stored in the memory and executable on the processor, wherein the dual-stack domain name access experience evaluation program is configured to implement the steps of the dual-stack domain name access experience evaluation method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores a dual-stack domain name access experience evaluation program, which, when executed by a processor, implements the steps of the dual-stack domain name access experience evaluation method according to any one of claims 1 to 7.

Images