Reverse domain name resolution method, device, equipment, medium and product

Abstract

The invention provides a reverse domain name resolution method and device, equipment, a medium and a product, and the method comprises the steps: detecting the operation state of a local reverse domain name resolution link in response to a reverse domain name resolution request sent by a terminal; and determining whether to import a reverse domain name resolution record in the local Zone file according to the running state, wherein the reverse domain name resolution record is used for providing a reverse domain name resolution service for the terminal. According to the embodiment of the invention, the reliability of a reverse domain name resolution scheme can be improved, the reverse domain name resolution service can be provided for the terminal even under the extreme conditions that the domain name root, the top-level domain name and the authoritative service are interrupted, and the like, and the reverse domain name resolution service can be provided for the terminal on the premise that the Local DNS does not need to be configured by an administrator and does not need to be networked with a protection platform. And reverse domain name resolution protection can be realized adaptively based on the original resolution protection snapshot.

Description

Background Art

[0002] In the related art, reverse DNS domain name query is a process of resolving an IP address into the original corresponding domain name through reverse domain name resolution. Reverse domain name resolution and forward domain name resolution are opposite processes. Forward domain name resolution uses A record query, while reverse domain name resolution uses PTR record query.

[0003] Existing reverse DNS resolution solutions rely on manual configuration of PTR record updates to achieve reverse domain name resolution, and cannot reach a new height of operation and maintenance with non-cooperation in the process, no perception at the terminal, and adaptive switching.

[0004] It should be noted that the information disclosed in the above background art section is only used to strengthen the understanding of the background of the present disclosure, and thus may include information that does not constitute the prior art known to those of ordinary skill in the art. Summary of the Invention

[0005] The purpose of the present disclosure is to provide a reverse domain name resolution method, device, equipment, medium and product, which are used to overcome at least to a certain extent the problems such as poor reliability of the reverse domain name resolution solution caused by the limitations and defects of the related technology.

[0006] According to the first aspect of the embodiments of the present disclosure, a reverse domain name resolution method is provided, which is applicable to a Local DNS server that can interact with a reverse domain name resolution protection server. The reverse domain name resolution method includes: in response to a reverse domain name resolution request sent by a terminal, detecting the running state of the local reverse domain name resolution link; determining whether to import the reverse domain name resolution record in the local Zone file according to the running state, and the reverse domain name resolution record is used to provide reverse domain name resolution services for the terminal.

[0007] In an exemplary embodiment of the present disclosure, determining whether to import the reverse domain name resolution record in the local Zone file according to the running state, and the reverse domain name resolution record is used to provide reverse domain name resolution services for the terminal includes:

[0008] Detecting whether the reverse domain name authoritative server can be accessed;

[0009] In response to detecting that the reverse domain name authoritative server cannot be accessed, determining that the running state is a link failure state;

[0010] In response to the running state being a link failure state, importing the reverse domain name resolution record in the local Zone file.

[0011] In an exemplary embodiment of the present disclosure, it further includes:

[0012] In response to detecting that the reverse domain name authoritative server can be accessed, send the reverse domain name resolution request to the reverse domain name authoritative server for resolution;

[0013] Receive the resolution result corresponding to the reverse domain name resolution request feedback by the reverse domain name authoritative server.

[0014] In an exemplary embodiment of the present disclosure, it further includes:

[0015] In response to the acquisition request of the original resolution data record sent by the reverse domain name resolution protection server; send the local original resolution data record to the reverse domain name resolution protection server corresponding to the acquisition request.

[0016] In an exemplary embodiment of the present disclosure, it further includes:

[0017] Receive the Zone file sent by the reverse domain name resolution protection server and store it as the local Zone file, the Zone file is configured to be generated from the original resolution data record, and the Zone file includes PTR records.

[0018] According to the second aspect of the embodiments of the present disclosure, a reverse domain name resolution method is provided, which is applicable to a reverse domain name resolution protection server. The reverse domain name resolution protection server can perform data interaction with the Local DNS server. The reverse domain name resolution method includes:

[0019] Send an acquisition request for reverse original resolution data records to the Local DNS server;

[0020] Receive the original resolution data records sent by the Local DNS server;

[0021] Generate a Zone file according to the original resolution data record, and the Zone file includes PTR records;

[0022] Send the Zone file to the corresponding Local DNS server.

[0023] In an exemplary embodiment of the present disclosure, generating a Zone file according to the original resolution data record includes:

[0024] Perform data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record benchmark library;

[0025] Extract resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record benchmark library to generate a reverse domain name resolution dimension table for the Local DNS server;

[0026] Generate the Zone file according to the reverse domain name resolution dimension table.

[0027] In an exemplary embodiment of the present disclosure, data cleaning processing is performed on the received original resolution data record to generate a reverse domain name resolution record benchmark library, including:

[0028] Determine the data source information of the original resolution data record, where the data source information includes the identity identification information of the LocalDNS server;

[0029] Query the reverse domain name resolution dimension table corresponding to the Local DNS server pointed to by the identity identification information to determine whether the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table;

[0030] Based on the determination result of whether the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, determine whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library.

[0031] In an exemplary embodiment of the present disclosure, based on the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table, determine whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library, including:

[0032] In response to the domain name in the resolution result of the original resolution data record being stored in the reverse domain name resolution dimension table, perform forward resolution dial test verification on the original resolution data record;

[0033] In response to the original resolution data record passing the forward resolution dial test verification, parse whether the resolution result in the original resolution data record points to an existing FQDN;

[0034] In response to the resolution result of the original resolution data record pointing to an existing FQDN, perform merging processing on the resolution results pointing to the same existing FQDN;

[0035] In response to the resolution result of the original resolution data record not pointing to any existing FQDN, determine the corresponding FQDN according to the resolution result and store it;

[0036] In response to completing the merging processing of the resolution results pointing to the same existing FQDN or determining the corresponding FQDN according to the resolution result and storing it, perform data cleaning processing on the original resolution data record to generate a reverse domain name resolution record benchmark library.

[0037] In an exemplary embodiment of the present disclosure, determining whether to perform data cleaning processing on the received original resolution data record according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table to generate a reverse domain name resolution record benchmark library includes:

[0038] In response to the domain name in the resolution result of the original resolution data record being stored in the reverse domain name resolution dimension table, perform forward resolution dial test verification on the original resolution data record;

[0039] In response to the original resolution data record failing the forward resolution dial test verification, discard the original resolution data record.

[0040] In an exemplary embodiment of the present disclosure, determining whether to perform data cleaning processing on the received original resolution data record according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table to generate a reverse domain name resolution record benchmark library includes:

[0041] In response to the domain name in the resolution result of the original resolution data record not being stored in the reverse domain name resolution dimension table, determine whether the IP in the resolution result of the original resolution data record is a new IP;

[0042] In response to the IP in the resolution result of the original resolution data record being the new IP, perform forward resolution dial test verification on the original resolution data record;

[0043] In response to the IP in the resolution result of the original resolution data record not being the new IP, perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library.

[0044] In an exemplary embodiment of the present disclosure, the data cleaning processing includes at least one of cleaning, confidence, fusion, and merging.

[0045] In an exemplary embodiment of the present disclosure, extracting resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record benchmark library to generate a reverse domain name resolution dimension table of the Local DNS server includes:

[0046] Determine whether the original resolution data record in the reverse domain name resolution record benchmark library meets the data timeliness requirement;

[0047] In response to the original resolution data record meeting the data timeliness requirement, determine whether the domain name of the resolution result in the original resolution data record is the designated domain name of the Local DNS server;

[0048] In response to the domain name in the parsing result of the original parsing data record not being the designated domain name of the Local DNS server, determine whether the request volume of the parsing result reaches the request volume threshold;

[0049] In response to the request volume of the parsing result reaching the request volume threshold or in response to the domain name in the parsing result of the original parsing data record being the designated domain name of the Local DNS server, determine the identity identification information of the Local DNS server to which the original parsing data record belongs;

[0050] Perform a reverse domain name resolution dimension table query on the original parsing data record according to the identity identification;

[0051] In response to the reverse domain name resolution dimension table query determining that the original parsing data record includes a new parsing result, inject the original parsing data record including the new parsing result into the reverse domain name resolution dimension table;

[0052] In response to the original parsing data record not meeting the data timeliness requirement or the request volume of the parsing result not reaching the request volume threshold or the reverse domain name resolution dimension table query determining that the original parsing data record does not include a new parsing result, discard the original parsing data record.

[0053] In an exemplary embodiment of the present disclosure, the reverse domain name resolution record includes at least one of a PTR record, a parsing log, and associated metadata.

[0054] According to a third aspect of the embodiments of the present disclosure, a reverse domain name resolution device is provided, which is applicable to a Local DNS server, and the Local DNS server can perform data interaction with a reverse domain name resolution protection server. The reverse domain name resolution device includes:

[0055] A detection module, configured to detect the running state of the local reverse domain name resolution link in response to a reverse domain name resolution request sent by a terminal;

[0056] An import module, configured to determine whether to import the reverse domain name resolution record in the local Zone file according to the running state, and the reverse domain name resolution record is used to provide reverse domain name resolution services for the terminal.

[0057] According to a fourth aspect of the embodiments of the present disclosure, a reverse domain name resolution device is provided, which is applicable to a reverse domain name resolution protection server, and the reverse domain name resolution protection server can perform data interaction with a Local DNS server. The reverse domain name resolution device includes:

[0058] A sending module, configured to send a collection request for reverse original resolution data records to the Local DNS server;

[0059] A receiving module, configured to receive the original resolution data records sent by the Local DNS server;

[0060] A generating module, configured to generate a Zone file according to the original resolution data records, where the Zone file includes PTR records;

[0061] The sending module is further configured to send the Zone file to the corresponding Local DNS server.

[0062] According to a fifth aspect of the present disclosure, there is provided an electronic device, including: a memory; and a processor coupled to the memory, where the processor is configured to execute the method according to any one of the above based on instructions stored in the memory.

[0063] According to a sixth aspect of the present disclosure, there is provided a computer-readable storage medium, on which a program is stored, and when the program is executed by a processor, it implements the reverse domain name resolution method according to any one of the above.

[0064] According to a seventh aspect of the present disclosure, there is provided a computer program product, including a computer program, characterized in that when the computer program is executed by a processor, it implements the reverse domain name resolution method according to any one of the above.

[0065] In the embodiments of the present disclosure, by responding to a reverse domain name resolution request sent by a terminal, the running state of the local reverse domain name resolution link is detected, and then it is determined whether to import the reverse domain name resolution records in the local Zone file according to the running state. The reverse domain name resolution records are used to provide reverse domain name resolution services for the terminal, improving the reliability of the reverse domain name resolution solution. Even in extreme cases where the domain name root, top-level domain name, and authoritative service are all interrupted, reverse domain name resolution services can still be provided for the terminal. Without the need for administrator configuration in Local DNS and without the need to maintain a connection to the protection platform, reverse domain name resolution protection can be adaptively implemented based on the original resolution protection snapshot.

[0066] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. Description of the Drawings

[0067] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure. Obviously, the accompanying drawings in the following description are only some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0068] Figure 1 is a schematic diagram of a reverse domain name resolution solution in the related art;

[0069] Figure 2 is a flowchart of a reverse domain name resolution method in an exemplary embodiment of the present disclosure;

[0070] Figure 3 is a flowchart of another reverse domain name resolution method in an exemplary embodiment of the present disclosure;

[0071] Figure 4 is a flowchart of another reverse domain name resolution method in an exemplary embodiment of the present disclosure;

[0072] Figure 5 is a flowchart of another reverse domain name resolution method in an exemplary embodiment of the present disclosure;

[0073] Figure 6 is a flowchart of another reverse domain name resolution method in an exemplary embodiment of the present disclosure;

[0074] Figure 7 is a block diagram of a reverse domain name resolution device in an exemplary embodiment of the present disclosure;

[0075] Figure 8 is a block diagram of another reverse domain name resolution device in an exemplary embodiment of the present disclosure;

[0076] Figure 9 is a block diagram of a reverse domain name resolution architecture in an exemplary embodiment of the present disclosure;

[0077] Figure 10 is a block diagram of another reverse domain name resolution architecture in an exemplary embodiment of the present disclosure;

[0078] Figure 11 is a block diagram of an electronic device in an exemplary embodiment of the present disclosure. Detailed implementation manners

[0079] Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present disclosure. However, those skilled in the art will recognize that the technical solutions of the present disclosure may be practiced without one or more of the specific details, or may be implemented using other methods, components, devices, steps, etc. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring aspects of the present disclosure.

[0080] In addition, the accompanying drawings are only schematic illustrations of the present disclosure, and the same reference numerals in the drawings denote the same or similar parts, and thus repeated descriptions thereof will be omitted. Some of the block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0081] As Figure 1 shown, in the related art, the reverse DNS (Domain Name System) domain name query scheme is a process in which the LocalDNS 104 server resolves the IP address requested by the terminal 102 from the reverse domain name authoritative server 106 into the original corresponding domain name through reverse domain name resolution. Reverse domain name resolution and forward domain name resolution are opposite processes. Forward domain name resolution uses A record queries, while reverse domain name resolution uses PTR record (Pointer Record) queries. The most common TLDs for reverse domain name resolution are "in-addr.arpa" and "ip6.arpa", but are not limited thereto.

[0082] Among them, the TLD (Top-Level Domain) is the highest-level classification identifier in the domain name system, located on the far right of the domain name, and is used to classify the type of Internet resources or the country / region to which they belong, such as.com (commercial),.org (non-profit organization), or.cn (China), etc. 16. The most common TLDs for the reverse DNS (Reverse Domain Name System) scheme are not the general or country-code top-level domains in the traditional sense, but special structures dedicated to reverse resolution, as follows:

[0083] (1) For IPv4 reverse DNS resolution, the TLD used is.in-addr.arpa. For example, the reverse DNS record of 192.168.1.42 is located in the domain 42.1.168.192.in-addr.arpa.

[0084] (2) For IPv6 reverse DNS resolution, the TLD used is.ip6.arpa. For example, the reverse DNS record of 2001:db8::1 is located in the domain 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.

[0085] The existing reverse DNS resolution protection solutions have at least the following technical problems:

[0086] The existing DNS resolution protection solutions mainly protect the reverse DNS authoritative server 106, such as establishing a distributed authoritative server group (backup server 108), redundant network lines, and server anti-DDOS attack means, but fail to cope with the protection in extreme cases such as the interruption of the root domain name and top-level domain name services.

[0087] The existing reverse DNS resolution protection solutions require manual operation by the authoritative server administrator to change the configuration, and cannot reach the new height of operation and maintenance with non-cooperation in the process, no perception at the terminal, and adaptive switching.

[0088] Through in-depth research on the reverse DNS resolution service, and aiming at the characteristics of reverse DNS resolution data, the present disclosure example proposes a new reverse DNS resolution solution, that is, based on the data collection and fusion method, constructing a reverse DNS resolution data resource dimension table, and using the domain name protection system to cooperate with the Local DNS server to provide a non-cooperative and adaptive resolution protection technical solution for reverse DNS resolution.

[0089] The following will explain the implementation manner of the present disclosure example in detail with reference to the accompanying drawings.

[0090] Figure 2 is a flowchart of the reverse DNS resolution method in the exemplary embodiment of the present disclosure.

[0091] Referring to Figure 2 , the reverse DNS resolution method may include:

[0092] Step S202, in response to a reverse DNS resolution request sent by a terminal, detecting the running state of the local reverse DNS resolution link;

[0093] Step S204, determining whether to import the reverse DNS resolution records in the local Zone file according to the running state, where the reverse DNS resolution records are used to provide reverse DNS resolution services for the terminal.

[0094] In an embodiment of the present disclosure, by responding to a reverse domain name resolution request sent by a terminal, the operating state of the local reverse domain name resolution link is detected, and then whether to import the reverse domain name resolution records in the local Zone file is determined according to the operating state. The reverse domain name resolution records are used to provide reverse domain name resolution services for the terminal, improving the reliability of the reverse domain name resolution solution. Even in extreme cases such as the interruption of the domain name root, top-level domain name, and authoritative service, reverse domain name resolution services can be provided for the terminal. Without the need for administrator configuration in the Local DNS and without maintaining a connection to the protection platform, reverse domain name resolution protection can be adaptively implemented based on the original parsing protection snapshot.

[0095] Next, each step of the reverse domain name resolution method will be described in detail.

[0096] In an exemplary embodiment of the present disclosure, determining whether to import the reverse domain name resolution records in the local Zone file according to the operating state, where the reverse domain name resolution records are used to provide reverse domain name resolution services for the terminal includes:

[0097] Detect whether the reverse domain name authoritative server can be accessed;

[0098] In response to detecting that the reverse domain name authoritative server cannot be accessed, determine that the operating state is a link failure state;

[0099] In response to the operating state being a link failure state, import the reverse domain name resolution records in the local Zone file.

[0100] In the above embodiment, by sending the collection of original parsing data records to each Local DNS server, and then through processing processes such as data cleaning, fusion (complementation), confidence, and parsing dimension table construction, finally, each reverse domain name resolution protection domain Zone file is generated and sent back to each Local DNS respectively. Especially when the operating state is detected to be a link failure state, the original reverse domain name resolution link is interrupted, and the Local DNS server enables the emergency protection function, imports the data in the Zone file prepared in advance for parsing protection, and continues to provide reverse domain name resolution query services for the terminal.

[0101] In an exemplary embodiment of the present disclosure, it further includes:

[0102] In response to detecting that the reverse domain name authoritative server can be accessed, send the reverse domain name resolution request to the reverse domain name authoritative server for resolution;

[0103] Receive the resolution result corresponding to the reverse domain name resolution request feedback by the reverse domain name authoritative server.

[0104] In an exemplary embodiment of the present disclosure, it further includes:

[0105] In response to a collection request for the original resolution data record sent by the reverse domain name resolution protection server, send the local original resolution data record to the reverse domain name resolution protection server corresponding to the collection request.

[0106] In the above embodiment, the original resolution data record may include the keywords shown in Table 1, and these keywords are also used to construct the reverse domain name resolution record benchmark library described later.

[0107] Table 1

[0108]

[0109] In an exemplary embodiment of the present disclosure, it further includes:

[0110] Receive the Zone file sent by the reverse domain name resolution protection server and store it as the local Zone file. The Zone file is configured to be generated from the original resolution data record, and the Zone file includes PTR records.

[0111] Figure 3 It is a flowchart of the reverse domain name resolution method in an exemplary embodiment of the present disclosure.

[0112] Reference Figure 3 , a reverse domain name resolution method is provided, which is applicable to a reverse domain name resolution protection server. The reverse domain name resolution protection server can interact with the Local DNS server for data. The reverse domain name resolution method includes:

[0113] Step S302: Send a collection request for the reverse original resolution data record to the Local DNS server;

[0114] Step S304: Receive the original resolution data record sent by the Local DNS server;

[0115] Step S306: Generate a Zone file according to the original resolution data record. The Zone file includes PTR records;

[0116] Step S308: Send the Zone file to the corresponding Local DNS server.

[0117] In an embodiment of the present disclosure, by sending a collection request for reverse original resolution data records to the Local DNS server, receiving the original resolution data records sent by the Local DNS server, generating a Zone file based on the original resolution data records, and then sending the Zone file to the corresponding Local DNS server, even in extreme cases such as the interruption of the domain name root, top-level domain name, and authoritative service, it can provide reverse domain name resolution services for terminals. Without the need for administrator configuration in the Local DNS and without maintaining a network connection with the protection platform, it can adaptively implement reverse domain name resolution protection based on the original resolution protection snapshot.

[0118] Next, each step of the reverse domain name resolution method will be described in detail.

[0119] In an exemplary embodiment of the present disclosure, generating a Zone file based on the original resolution data records includes:

[0120] Performing data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record reference library;

[0121] Extracting the resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record reference library to generate a reverse domain name resolution dimension table for the Local DNS server;

[0122] Generating the Zone file based on the reverse domain name resolution dimension table.

[0123] In the above embodiment, the reverse domain name resolution dimension table includes the content shown in Table 2 below.

[0124] Table 2

[0125]

[0126] In an exemplary embodiment of the present disclosure, performing data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record reference library includes:

[0127] Determining the data source information of the original resolution data records, where the data source information includes the identity identification information of the Local DNS server;

[0128] Querying the reverse domain name resolution dimension table corresponding to the Local DNS server pointed to by the identity identification information to determine whether the domain name in the resolution result of the original resolution data records has been stored in the reverse domain name resolution dimension table;

[0129] Based on the determination result of whether the domain name in the parsing result of the original parsing data record has been stored in the reverse domain name resolution dimension table, determine whether to perform data cleaning on the received original parsing data record to generate a reverse domain name resolution record benchmark library.

[0130] In an exemplary embodiment of the present disclosure, determining whether to perform data cleaning on the received original parsing data record to generate a reverse domain name resolution record benchmark library according to the determination result of whether the original parsing data record has been stored in the reverse domain name resolution dimension table includes:

[0131] In response to the domain name in the parsing result of the original parsing data record being stored in the reverse domain name resolution dimension table, perform forward parsing dial test verification on the original parsing data record;

[0132] In response to the original parsing data record passing the forward parsing dial test verification, parse whether the parsing result in the original parsing data record points to an existing FQDN;

[0133] In response to the parsing result in the original parsing data record pointing to an existing FQDN, perform merging processing on the parsing results pointing to the same existing FQDN;

[0134] In response to the parsing result in the original parsing data record not pointing to any existing FQDN, determine the corresponding FQDN according to the parsing result and store it;

[0135] In response to completing the merging processing of the parsing results pointing to the same existing FQDN or determining the corresponding FQDN according to the parsing result and storing it, perform data cleaning on the original parsing data record to generate a reverse domain name resolution record benchmark library.

[0136] In the above embodiment, FQDN (Fully Qualified Domain Name) refers to a clear and complete hierarchical address identifier in the domain name system, including the host name and all parent domain names, and ends with a dot (such as host.example.com.). Reverse resolution maps an IP address (such as 192.168.1.1) to the corresponding FQDN (such as host.example.com), which needs to be completed in the.arpa domain with the help of PTR records. For example, the reverse resolution query target for the IPv4 address 192.168.1.1 is 1.1.168.192.in-addr.arpa. (in FQDN form), and the associated FQDN is returned through its PTR record. The FQDN ensures the accuracy of reverse resolution and the verifiability of service identity through global uniqueness.

[0137] In an exemplary embodiment of the present disclosure, such asFigure 4 As shown in Figure 4 , the process of cleaning the collected original resolution data records to generate a reverse domain name resolution record benchmark library in the reverse domain name resolution method includes:

[0138] Step S402: Obtain the original sampling data records, that is, obtain the original resolution data records of the Local DNS server.

[0139] Step S404: Identify the data source, query the data dimension table corresponding to the data source location, and search and compare the corresponding reverse domain name resolution data.

[0140] Step S406: Is a new reverse resolution domain name added? If yes, execute step S410; if no, execute step S408.

[0141] Step S408: Is the parsing result updated? Specifically, determine whether the IP address in the parsing result is a newly added IP address. If yes, execute step S410; if no, execute step S416.

[0142] Step S410: Conduct a forward resolution ping test verification. Is it passed? If yes, execute step S412; if no, execute step S414.

[0143] Step S412: Does the parsing result point to an existing FQDN? If the same FQDN requires the parsing results to be merged, otherwise store them separately.

[0144] Step S414: Discard the invalid data.

[0145] Step S416: The cleaning is passed, update and save.

[0146] In an exemplary embodiment of the present disclosure, according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table, it is determined whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library, including:

[0147] In response to the domain name in the parsing result of the original resolution data record being stored in the reverse domain name resolution dimension table, conduct a forward resolution ping test verification on the original resolution data record;

[0148] In response to the original resolution data record failing the forward resolution ping test verification, discard the original resolution data record.

[0149] In an exemplary embodiment of the present disclosure, according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table, it is determined whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library, including:

[0150] In response to that the domain name in the parsing result in the original parsing data record is not stored in the reverse domain name resolution dimension table, determine whether the IP in the parsing result in the original parsing data record is a newly added IP;

[0151] In response to that the IP in the parsing result in the original parsing data record is the newly added IP, perform forward parsing test verification on the original parsing data record;

[0152] In response to that the IP in the parsing result in the original parsing data record is not the newly added IP, perform data cleaning processing on the received original parsing data record to generate a reverse domain name resolution record benchmark library.

[0153] In an exemplary embodiment of the present disclosure, the data cleaning processing includes at least one of cleaning, confidence, fusion, and merging.

[0154] In an exemplary embodiment of the present disclosure, extracting parsing data that meets the requirements of the LocalDNS server from the reverse domain name resolution record benchmark library to generate the reverse domain name resolution dimension table of the LocalDNS server includes:

[0155] Determine whether the original parsing data record in the reverse domain name resolution record benchmark library meets the data timeliness requirement;

[0156] In response to that the original parsing data record meets the data timeliness requirement, determine whether the domain name in the parsing result of the original parsing data record is the specified domain name of the Local DNS server;

[0157] In response to that the domain name in the parsing result of the original parsing data record is not the specified domain name of the Local DNS server, determine whether the request volume of the parsing result reaches the request volume threshold;

[0158] In response to that the request volume of the parsing result reaches the request volume threshold or in response to that the domain name in the parsing result of the original parsing data record is the specified domain name of the Local DNS server, determine the identity identification information of the LocalDNS server to which the original parsing data record belongs;

[0159] Perform the reverse domain name resolution dimension table query on the original parsing data record according to the identity identification;

[0160] In response to that the reverse domain name resolution dimension table query determines that the original parsing data record includes a new parsing result, inject the original parsing data record including the new parsing result into the reverse domain name resolution dimension table;

[0161] In response to the original parsed data record not meeting the data timeliness requirement, or the request volume of the parsed result not reaching the request volume threshold, or the reverse domain name resolution dimension table query determining that the original parsed data record does not include a new parsed result, the original parsed data record is discarded.

[0162] In an exemplary embodiment of the present disclosure, the reverse domain name resolution record includes at least one of a PTR record, a parsing log, and associated metadata.

[0163] In an exemplary embodiment of the present disclosure, on the basis of generating a reverse domain name resolution record benchmark library according to the steps shown Figure 4 as shown, the process of cleaning the collected original parsed data records to generate a reverse domain name resolution record benchmark library in the reverse domain name resolution method includes: Figure 5 as shown.

[0164] Step S502, import the benchmark data source in the reverse domain name resolution record benchmark library.

[0165] Step S504, is the data timeliness feasible? If yes, execute step S506; if no, execute step S516.

[0166] Step S506, is it a key protected domain name? If yes, execute step S510; if no, execute step S508.

[0167] Step S508, does the request volume reach the protection threshold? If yes, execute step S510; if no, execute step S516.

[0168] Step S510, classify the data source location (city).

[0169] Step S512, query the LDNS ID dimension table to which the data source belongs.

[0170] Step S514, is there a refresh of the data record? If yes, execute step S518; if no, execute step S516.

[0171] Step S516, discard the data.

[0172] Step S518, inject and save the data.

[0173] Based on the Local DNS server and the reverse domain name resolution protection server 604 shown in the above embodiment, execute the reverse domain name resolution steps. As Figure 6 shown, the steps executed by the reverse domain name resolution system composed of the LocalDNS server 602 and the reverse domain name resolution protection server 604 include:

[0174] Add a dedicated reverse domain name resolution protection server 604, preferably deployed in a secure and controlled network. A reverse domain name resolution protection module needs to be added to the Local DNS server 602 of the telecommunications operator, while no changes are required for other levels of operation servers.

[0175] First, construct reverse domain name resolution resources. The reverse domain name resolution protection server 604 initiates a reverse domain name resolution data collection task to each level of Local DNS server 602 through a unified collection interface. The data collection needs to be carried out periodically without interruption to ensure the effectiveness and accuracy of the collected data.

[0176] Secondly, the reverse domain name resolution protection system cleans, confidences, fuses, and merges the collected data to construct reverse domain name resolution protection data and generates a fault emergency resolution Zone file. Finally, the reverse domain name resolution protection system periodically distributes the emergency resolution Zone file to each Local DNS server 602.

[0177] So far, the preliminary preparation process of reverse domain name resolution protection is completed, and the system has the ability of reverse domain name resolution protection.

[0178] Thirdly, the reverse domain name resolution protection module of the Local DNS server 602 tracks the running status of the local reverse domain name resolution link. When a risk occurs, for example, when it is detected that the Local DNS server 602 cannot access the reverse domain name authoritative server 606, the reverse domain name resolution protection function is started, the Zone file is opened, the reverse domain name resolution data is imported, the associated results are queried, and the reverse domain name resolution service is continued to be provided for the terminal 600.

[0179] Corresponding to the above method embodiments, the present disclosure also provides a reverse domain name resolution device, which can be used to execute the above method embodiments.

[0180] Figure 7 It is a block diagram of a reverse domain name resolution device in an exemplary embodiment of the present disclosure.

[0181] Reference Figure 7 , a reverse domain name resolution device is provided, which is applicable to the Local DNS server. The Local DNS server can interact with the reverse domain name resolution protection server. The reverse domain name resolution device 700 may include:

[0182] A detection module 702, configured to detect the running status of the local reverse domain name resolution link in response to a reverse domain name resolution request sent by a terminal;

[0183] An import module 704 is configured to determine whether to import reverse domain name resolution records in a local Zone file according to the operating state, and the reverse domain name resolution records are used to provide reverse domain name resolution services for the terminal.

[0184] In an exemplary embodiment of the present disclosure, the import module 704 is further configured to:

[0185] Detect whether it is possible to access a reverse domain name authoritative server;

[0186] In response to detecting that it is not possible to access the reverse domain name authoritative server, determine that the operating state is a link failure state;

[0187] In response to the operating state being a link failure state, import the reverse domain name resolution records in the local Zone file.

[0188] In an exemplary embodiment of the present disclosure, the reverse domain name resolution device 700 is further configured to:

[0189] In response to detecting that it is possible to access the reverse domain name authoritative server, send the reverse domain name resolution request to the reverse domain name authoritative server for resolution;

[0190] Receive the resolution result corresponding to the reverse domain name resolution request feedback by the reverse domain name authoritative server.

[0191] In an exemplary embodiment of the present disclosure, the reverse domain name resolution device 700 is further configured to:

[0192] In response to a collection request for original resolution data records sent by a reverse domain name resolution protection server, send the local original resolution data records to the reverse domain name resolution protection server corresponding to the collection request.

[0193] In an exemplary embodiment of the present disclosure, the reverse domain name resolution device 700 is further configured to:

[0194] Receive the Zone file sent by the reverse domain name resolution protection server and store it as the local Zone file. The Zone file is configured to be generated from the original resolution data records, and the Zone file includes PTR records.

[0195] Corresponding to the above method embodiments, the present disclosure also provides a reverse domain name resolution device, which can be used to execute the above method embodiments.

[0196] Figure 8 It is a block diagram of a reverse domain name resolution device in an exemplary embodiment of the present disclosure.

[0197] Reference Figure 8, a reverse domain name resolution device 800 is provided, which is applicable to a reverse domain name resolution protection server. The reverse domain name resolution protection server can interact with a Local DNS server. The reverse domain name resolution device 800:

[0198] A sending module 802 is configured to send a collection request for reverse original resolution data records to the Local DNS server;

[0199] A receiving module 804 is configured to receive the original resolution data records sent by the Local DNS server;

[0200] A generating module 806 is configured to generate a Zone file according to the original resolution data records, and the Zone file includes PTR records;

[0201] The sending module 802 is further configured to send the Zone file to the corresponding Local DNS server.

[0202] In an exemplary embodiment of the present disclosure, the generating module 806 is further configured to:

[0203] Perform data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record benchmark library;

[0204] Extract resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record benchmark library to generate a reverse domain name resolution dimension table for the Local DNS server;

[0205] Generate the Zone file according to the reverse domain name resolution dimension table.

[0206] In an exemplary embodiment of the present disclosure, the generating module 806 is further configured to:

[0207] Determine the data source information of the original resolution data records, and the data source information includes the identity identification information of the Local DNS server;

[0208] Query the reverse domain name resolution dimension table corresponding to the Local DNS server pointed to by the identity identification information to determine whether the domain name in the resolution result of the original resolution data records has been stored in the reverse domain name resolution dimension table;

[0209] According to the determination result of whether the domain name in the resolution result of the original resolution data records has been stored in the reverse domain name resolution dimension table, determine whether to perform data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record benchmark library.

[0210] In an exemplary embodiment of the present disclosure, the generation module 806 is further configured to:

[0211] In response to the domain name in the parsing result in the original parsing data record being stored in the reverse domain name resolution dimension table, perform a forward parsing dial test verification on the original parsing data record;

[0212] In response to the original parsing data record passing the forward parsing dial test verification, parse whether the parsing result in the original parsing data record points to an existing FQDN;

[0213] In response to the parsing result in the original parsing data record pointing to an existing FQDN, perform a merging process on the parsing results pointing to the same existing FQDN;

[0214] In response to the parsing result in the original parsing data record not pointing to any existing FQDN, determine the corresponding FQDN according to the parsing result and store it;

[0215] In response to completing the merging process on the parsing results pointing to the same existing FQDN or determining the corresponding FQDN according to the parsing result and storing it, perform a data cleaning process on the original parsing data record to generate a reverse domain name resolution record benchmark library.

[0216] In an exemplary embodiment of the present disclosure, the generation module 806 is further configured to:

[0217] In response to the domain name in the parsing result in the original parsing data record being stored in the reverse domain name resolution dimension table, perform a forward parsing dial test verification on the original parsing data record;

[0218] In response to the original parsing data record not passing the forward parsing dial test verification, discard the original parsing data record.

[0219] In an exemplary embodiment of the present disclosure, the generation module 806 is further configured to:

[0220] In response to the domain name in the parsing result in the original parsing data record not being stored in the reverse domain name resolution dimension table, determine whether the IP in the parsing result in the original parsing data record is a newly added IP;

[0221] In response to the IP in the parsing result in the original parsing data record being the newly added IP, perform a forward parsing dial test verification on the original parsing data record;

[0222] In response to the IP in the parsing result in the original parsing data record not being the newly added IP, perform a data cleaning process on the received original parsing data record to generate a reverse domain name resolution record benchmark library.

[0223] In an exemplary embodiment of the present disclosure, the data cleaning process includes at least one of cleaning, confidence, fusion, and merging.

[0224] In an exemplary embodiment of the present disclosure, the generation module 806 is further configured to:

[0225] Determine whether the original resolution data record in the reverse domain name resolution record reference library meets the data timeliness requirement;

[0226] In response to the original resolution data record meeting the data timeliness requirement, determine whether the domain name of the resolution result in the original resolution data record is the designated domain name of the Local DNS server;

[0227] In response to the domain name of the resolution result in the original resolution data record not being the designated domain name of the Local DNS server, determine whether the request volume of the resolution result reaches the request volume threshold;

[0228] In response to the request volume of the resolution result reaching the request volume threshold or in response to the domain name of the resolution result in the original resolution data record being the designated domain name of the Local DNS server, determine the identity identification information of the Local DNS server to which the original resolution data record belongs;

[0229] Perform a reverse domain name resolution dimension table query on the original resolution data record according to the identity identification;

[0230] In response to the reverse domain name resolution dimension table query determining that the original resolution data record includes a new resolution result, inject the original resolution data record including the new resolution result into the reverse domain name resolution dimension table;

[0231] In response to the original resolution data record not meeting the data timeliness requirement or the request volume of the resolution result not reaching the request volume threshold or the reverse domain name resolution dimension table query determining that the original resolution data record does not include a new resolution result, discard the original resolution data record.

[0232] In an exemplary embodiment of the present disclosure, the reverse domain name resolution record includes at least one of a PTR record, a resolution log, and associated metadata.

[0233] Since the functions of the reverse domain name resolution device 700 and the reverse domain name resolution device 800 have been described in detail in their corresponding method embodiments, the present disclosure will not repeat them here.

[0234] In an exemplary embodiment of the present disclosure, in view of the business characteristics of reverse domain name resolution data in a relatively monotonous form, a single resolution process, and far fewer access times than forward domain name resolution, the present application proposes a reverse resolution protection system 900.

[0235] As Figure 9 and Figure 10 shown, the reverse resolution protection system 900 proposed by the present application is implemented based on the functions of the above-mentioned reverse domain name resolution device 700 and reverse domain name resolution device 800. The reverse resolution protection system 900 constructs reverse domain name resolution protection data through processes such as distributed data collection, cleaning, and confidence, and generates a fault emergency Zone resolution file. When a risk occurs, for example, when the reverse resolution protection module 1002 and the LocalDNS server 904 cannot access the reverse domain name authoritative server 906, the LocalDNS server 904 imports the resolution protection data and continues to provide reverse domain name resolution query services for the terminal 902.

[0236] In an exemplary embodiment of the present disclosure, a dedicated reverse domain name resolution protection server is added, preferably deployed in a securely controlled network.

[0237] In an exemplary embodiment of the present disclosure, in order to support the reverse domain name resolution protection function, each LocalDNS server 904 needs to add a reverse domain name resolution protection function module and connect to the reverse domain name resolution protection server through a unified standard interface.

[0238] In an exemplary embodiment of the present disclosure, the reverse domain name resolution protection server 908 issues the collection of original resolution data records to each LocalDNS server 904 in advance, and then through processing processes such as data cleaning, fusion (complementary), confidence, and construction of the resolution dimension table, finally generates each reverse domain name resolution protection domain Zone file and sends it back to each Local DNS server 904 respectively.

[0239] In an exemplary embodiment of the present disclosure, when a risk occurs and the original reverse domain name resolution link is interrupted, the LocalDNS server 904 enables the emergency protection function, imports the prepared resolution protection Zone file data, and continues to provide reverse domain name resolution query services for the terminal 902.

[0240] The detailed description of the core function module for implementing reverse domain name resolution protection is as follows.

[0241] (1) The functions of the reverse resolution protection module 1002 newly added to the LocalDNS server 904 include the following functions:

[0242] (1.1) Reverse domain name resolution data collection, that is, retrieving the original PTR resolution records, logs or relevant data, and cooperating with the reverse resolution protection system 900 to complete the collection requirements.

[0243] (1.2) The protected domain name Zone file management is achieved by periodically downloading the resolution Zone file data of the protected domain name from the reverse resolution protection system 900 and refreshing the resolution data at the agreed time.

[0244] (2) The start / stop management of reverse domain name resolution protection includes:

[0245] (2.1) Tracking whether the reverse domain name resolution link is normal (it can monitor whether the relevant NS recursion is successfully implemented);

[0246] (2.2) Starting the emergency resolution function and importing the pre-prepared Zone file resolution data;

[0247] (2.3) Stopping the resolution protection service and restoring the normal recursion service.

[0248] (3) Main function description of the core module of the reverse resolution protection system 900:

[0249] In an exemplary embodiment of the present disclosure, the reverse domain name resolution data collection is to regularly collect the original sampled reverse domain name resolution data from each Local DNS server 904.

[0250] In an exemplary embodiment of the present disclosure, constructing the resolution data benchmark library is to construct the reverse domain name resolution data benchmark library through the data cleaning, fusion and data confidence processes proposed in this application.

[0251] In an exemplary embodiment of the present disclosure, generating the resolution data dimension table of the Local DNS server 904 is to extract the resolution data that meets its own needs from the benchmark library according to the resolution protection policy, and generate a resolution dimension table suitable for its own use for each Local DNS server 904.

[0252] In an exemplary embodiment of the present disclosure, the Zone file synchronization update is implemented based on the resolution dimension table data, synthesizing the Zone file of the reverse domain name resolution protected domain name, and performing the timeliness synchronization update management and distributing it to the Local DNS server 904.

[0253] (4) The method and processing flow for constructing the reverse domain name resolution data benchmark library include:

[0254] (4.1) The reverse resolution protection system 900 periodically sends a reverse domain name resolution data collection list and policy to the Local DNS server 904, and at the same time collects the collection results. The key information fields of the collection list are also the key fields for constructing the reverse domain name resolution data benchmark library.

[0255] (4.2) Based on the original data reported by each Local DNS server 904, this application uses a unique data confidence method for data cleaning and fusion complementarity. The reverse resolution protection system 900 identifies the data source, queries the corresponding data dimension table of the data source location, searches and compares the original reverse domain name resolution data, determines whether new data is added, whether positive dial testing verification is required, whether result merging is required, etc. in the processing flow. Finally, the useful data is saved into the database, gradually storing and constructing the reverse domain name resolution data benchmark library.

[0256] (5) The generation rules of the LocalDNS reverse domain name resolution dimension table include but are not limited to the following:

[0257] (5.1) The reverse domain name resolution data benchmark library provides a data base for resolution protection. However, the resolution data of each LocalDNS is different. It is necessary to extract the resolution data that meets its own needs from the benchmark library according to the resolution protection policy, generate a resolution data dimension table suitable for its own use, and provide an effective data source for the final output of the Zone file.

[0258] (5.2) This application refers to multiple dimensions such as data timeliness, whether it is a key protected domain name, and the domain name request volume, and generates a reverse domain name resolution data dimension table for each Local DNS server 904 according to the data source location.

[0259] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0260] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0261] Those skilled in the art of the present technology field can understand that various aspects of the present application can be implemented as a system, method, or program product. Therefore, various aspects of the present application can be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which can be collectively referred to as "circuit", "module", or "system" here.

[0262] Refer to the following Figure 11 to describe the electronic device 1100 according to this embodiment of the present application. Figure 11 The displayed electronic device 1100 is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present application.

[0263] As Figure 11 shown, the electronic device 1100 is presented in the form of a general-purpose computing device. The components of the electronic device 1100 may include, but are not limited to: at least one of the above-mentioned processing units 1110, at least one of the above-mentioned storage units 1120, and a bus 1130 connecting different system components (including the storage unit 1120 and the processing unit 1110).

[0264] Among them, the storage unit stores program codes, and the program codes can be executed by the processing unit 1110, so that the processing unit 1110 executes the steps according to various exemplary embodiments of the present application described in the "Exemplary Method" section of the present specification above. For example, the processing unit 1110 can execute the method as shown in the embodiments of the present disclosure.

[0265] The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 11201 and / or a cache 11202, and may further include a read-only storage unit (ROM) 11203.

[0266] The storage unit 1120 may further include a program / utility 11204 having a set (at least one) of program modules 11205. Such program modules 11205 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data. The implementation of a network environment may be included in each or some combination of these examples.

[0267] The bus 1130 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any bus structure in a variety of bus structures.

[0268] The electronic device 1100 can also communicate with one or more external devices 1140 (such as a keyboard, a pointing device, a Bluetooth device, etc.), and can also communicate with one or more devices that enable the terminal to interact with the electronic device 1100, and / or communicate with any device that enables the electronic device 1100 to communicate with one or more other computing devices (such as a router, a modem, etc.). Such communication can be carried out through the input / output (I / O) interface 1150. Moreover, the electronic device 1100 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the network adapter 1160. As shown in the figure, the network adapter 1160 communicates with other modules of the electronic device 1100 through the bus 1130. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0269] In summary, the embodiments of the present disclosure have at least the following prominent advantages compared with the prior art:

[0270] (1) A method for constructing a reverse domain name resolution protection resource is proposed, specifically including: a LocalDNS reverse domain name resolution protection module, a core function module of the reverse domain name resolution protection system, the construction definition of a reverse domain name resolution data reference library, etc. Compared with the prior art, this way of constructing the resolution resource is novel, enabling the resolution protection not to rely on the original resolution link and providing more reliable and effective resolution protection. Even in extreme cases where the domain name root, top-level domain name, and authoritative service are all interrupted, the resolution protection service can still be provided.

[0271] (2) By providing independent reverse domain name resolution protection management for each LocalDNS, including the generation rule of the reverse domain name resolution dimension table for the targeted LocalDNS, the automatic start / stop management of the reverse domain name resolution protection, etc., dynamic and intelligent reverse domain name resolution protection is achieved. The LocalDNS does not require administrator configuration and does not need to maintain a connection with the protection platform, and can adaptively implement domain name resolution protection based on the original resolution protection snapshot.

[0272] Those skilled in the art can easily understand from the description of the above embodiments that the exemplary embodiments described herein can be implemented by software or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a portable hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0273] In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium, on which a program product capable of implementing the above method of this specification is stored. In some possible implementation manners, various aspects of the present application can also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present application described in the above "Exemplary Method" section of this specification.

[0274] The program product for implementing the above method according to the embodiments of the present application can be a portable compact disc read-only memory (CD-ROM) and includes program code, and can run on a terminal device, such as a personal computer. However, the program product of the present application is not limited thereto. In this document, the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, device, or device.

[0275] Among them, the readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0276] A computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which readable program code is carried. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device.

[0277] The program code contained on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0278] In an exemplary embodiment of the present disclosure, there is also provided a computer program product. The computer program product may be loaded or stored using any combination of one or more readable media, and the program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and also including conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the terminal computing device, partially on the terminal device, executed as an independent software package, partially on the terminal computing device and partially on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the terminal computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., by using an Internet service provider to connect through the Internet).

[0279] In addition, the above-mentioned drawings are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present application, and are not for limiting purposes. It is easy to understand that the processes shown in the above-mentioned drawings do not indicate or limit the time sequence of these processes. Additionally, it is also easy to understand that these processes may be executed synchronously or asynchronously in, for example, multiple modules.

[0280] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include well-known knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only regarded as exemplary, and the true scope and concept of the present disclosure are pointed out by the claims.

Claims

1. A reverse domain name resolution method, characterized in that, Applicable to a Local DNS server, the Local DNS server being capable of data interaction with a reverse domain name resolution protection server, the reverse domain name resolution method comprising: In response to a reverse domain name resolution request sent by a terminal, detecting the running state of a local reverse domain name resolution link; Determining whether to import reverse domain name resolution records in a local Zone file according to the running state, the reverse domain name resolution records being used to provide reverse domain name resolution services for the terminal.

2. The reverse domain name resolution method according to claim 1, wherein Determining whether to import reverse domain name resolution records in a local Zone file according to the running state, the reverse domain name resolution records being used to provide reverse domain name resolution services for the terminal comprising: Detecting whether it is possible to access a reverse domain name authoritative server; In response to detecting that it is not possible to access the reverse domain name authoritative server, determining that the running state is a link failure state; In response to the running state being a link failure state, importing the reverse domain name resolution records in the local Zone file.

3. The reverse domain name resolution method according to claim 2, characterized in that, Further comprising: In response to detecting that it is possible to access the reverse domain name authoritative server, sending the reverse domain name resolution request to the reverse domain name authoritative server for resolution; Receiving the resolution result corresponding to the reverse domain name resolution request fed back by the reverse domain name authoritative server.

4. The reverse domain name resolution method according to any one of claims 1 to 3, characterized in that Further comprising: In response to a collection request for original resolution data records sent by a reverse domain name resolution protection server; Sending the local original resolution data records to the reverse domain name resolution protection server corresponding to the collection request.

5. The reverse domain name resolution method according to any one of claims 1-3, characterized in that, Further comprising: Receiving a Zone file sent by the reverse domain name resolution protection server and storing it as the local Zone file, the Zone file being configured to be generated from the original resolution data records, the Zone file including PTR records.

6. A reverse domain name resolution method, characterized in that, Applicable to a reverse domain name resolution protection server, the reverse domain name resolution protection server being capable of data interaction with a Local DNS server, the reverse domain name resolution method comprising: Sending a collection request for reverse original resolution data records to the Local DNS server; Receiving the original resolution data records sent by the Local DNS server; Generating a Zone file according to the original resolution data records, the Zone file including PTR records; Sending the Zone file to the corresponding Local DNS server.

7. The reverse domain name resolution method according to claim 6, wherein Generating a Zone file according to the original resolution data records comprising: Performing data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record benchmark library; Extracting resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record benchmark library to generate a reverse domain name resolution dimension table for the Local DNS server; Generating the Zone file according to the reverse domain name resolution dimension table.

8. The reverse domain name resolution method according to claim 7, wherein, Performing data cleaning processing on the received original resolution data records to generate a reverse domain name resolution record benchmark library comprising: Determining the data source information of the original resolution data records, the data source information including the identity identification information of the Local DNS server; Query the reverse domain name resolution dimension table corresponding to the Local DNS server pointed to by the identity identification information to determine whether the domain name in the resolution result in the original resolution data record has been stored in the reverse domain name resolution dimension table; Determine whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library according to the determination result of whether the domain name in the resolution result in the original resolution data record has been stored in the reverse domain name resolution dimension table.

9. The reverse domain name resolution method according to claim 8, characterized in that, Determine whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table, including: In response to the domain name in the resolution result of the original resolution data record being stored in the reverse domain name resolution dimension table, perform a forward resolution dial test verification on the original resolution data record; In response to the original resolution data record passing the forward resolution dial test verification, analyze whether the resolution result in the original resolution data record points to an existing FQDN; In response to the resolution result in the original resolution data record pointing to an existing FQDN, perform a merging process on the resolution results pointing to the same existing FQDN; In response to the resolution result in the original resolution data record not pointing to any existing FQDN, determine the corresponding FQDN according to the resolution result and store it; In response to completing the merging process on the resolution results pointing to the same existing FQDN or determining the corresponding FQDN according to the resolution result and storing it, perform data cleaning processing on the original resolution data record to generate a reverse domain name resolution record benchmark library.

10. The reverse domain name resolution method according to claim 8, wherein Determine whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table, including: In response to the domain name in the resolution result of the original resolution data record being stored in the reverse domain name resolution dimension table, perform a forward resolution dial test verification on the original resolution data record; In response to the original resolution data record failing the forward resolution dial test verification, discard the original resolution data record.

11. The reverse domain name resolution method according to claim 8, wherein, Determine whether to perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library according to the determination result of whether the original resolution data record has been stored in the reverse domain name resolution dimension table, including: In response to the domain name in the resolution result of the original resolution data record not being stored in the reverse domain name resolution dimension table, determine whether the IP in the resolution result of the original resolution data record is a new IP; In response to the IP in the resolution result of the original resolution data record being the new IP, perform a forward resolution dial test verification on the original resolution data record; In response to the IP in the resolution result of the original resolution data record not being the new IP, perform data cleaning processing on the received original resolution data record to generate a reverse domain name resolution record benchmark library.

12. The reverse domain name resolution method according to any one of claims 7-11, characterized in that The data cleaning process includes at least one of cleaning, confidence, fusion, and merging.

13. The reverse domain name resolution method according to claim 6, characterized in that Extracting resolution data that meets the requirements of the LocalDNS server from the reverse domain name resolution record benchmark library to generate the reverse domain name resolution dimension table of the LocalDNS server includes: Determining whether the original resolution data record in the reverse domain name resolution record benchmark library meets the data timeliness requirement; In response to the original resolution data record meeting the data timeliness requirement, determining whether the domain name of the resolution result in the original resolution data record is the specified domain name of the Local DNS server; In response to the domain name of the resolution result in the original resolution data record not being the specified domain name of the Local DNS server, determining whether the request volume of the resolution result reaches the request volume threshold; In response to the request volume of the resolution result reaching the request volume threshold or in response to the domain name of the resolution result in the original resolution data record being the specified domain name of the Local DNS server, determining the identity identification information of the LocalDNS server to which the original resolution data record belongs; Performing a query of the reverse domain name resolution dimension table on the original resolution data record according to the identity identification; In response to the reverse domain name resolution dimension table query determining that the original resolution data record includes a new resolution result, injecting the original resolution data record including the new resolution result into the reverse domain name resolution dimension table; In response to the original resolution data record not meeting the data timeliness requirement or the request volume of the resolution result not reaching the request volume threshold or the reverse domain name resolution dimension table query determining that the original resolution data record does not include a new resolution result, discarding the original resolution data record.

14. The reverse domain name resolution method according to any one of claims 1-13, characterized in that The reverse domain name resolution record includes at least one of a PTR record, a resolution log, and associated metadata.

15. A reverse domain name resolution device, characterized in that, Applicable to a Local DNS server, the Local DNS server can perform data interaction with a reverse domain name resolution protection server. The reverse domain name resolution method and the reverse domain name resolution device include: A detection module, configured to detect the running state of the local reverse domain name resolution link in response to a reverse domain name resolution request sent by a terminal; An import module, configured to determine whether to import the reverse domain name resolution record in the local Zone file according to the running state, and the reverse domain name resolution record is used to provide reverse domain name resolution services for the terminal.

16. A reverse domain name resolution device, characterized in that, Applicable to a reverse domain name resolution protection server, the reverse domain name resolution protection server can perform data interaction with a Local DNS server. The reverse domain name resolution device includes: A sending module, configured to send a collection request for reverse original resolution data records to the Local DNS server; A receiving module, configured to receive the original resolution data records sent by the Local DNS server; A generating module, configured to generate a Zone file according to the original resolution data record, and the Zone file includes a PTR record; The sending module is further configured to send the Zone file to the corresponding LocalDNS server.

17. An electronic device, characterized in that, Comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the reverse domain name resolution method according to any one of claims 1-14 based on instructions stored in the memory.

18. A computer-readable storage medium, having a program stored thereon, which when executed by a processor implements the reverse domain name resolution method according to any one of claims 1-14.

19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the reverse domain name resolution method according to any one of claims 1-14.

Images