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

Abstract

This disclosure provides a reverse DNS resolution method, apparatus, device, medium, and product. The reverse DNS resolution method includes: responding to a reverse DNS resolution request sent by a terminal, detecting the operational status of the local reverse DNS resolution link; and determining whether to import reverse DNS resolution records from a local Zone file based on the operational status. These reverse DNS resolution records are used to provide reverse DNS resolution services to the terminal. Through the embodiments of this disclosure, the reliability of the reverse DNS resolution scheme can be improved. Even in extreme cases such as interruptions to the domain root, top-level domain, and authoritative services, reverse DNS resolution services can still be provided to the terminal. Under the premise that the Local DNS does not require administrator configuration or need to maintain a network connection with the protection platform, reverse DNS resolution protection can be adaptively implemented based on existing DNS protection snapshots.

Description

Technical Field

[0001] This disclosure relates to the field of server technology, and more specifically, to a reverse domain name resolution method, apparatus, device, medium, and product. Background Technology

[0002] In related technologies, reverse DNS lookup is the process of resolving an IP address into its original corresponding domain name through reverse DNS resolution. Reverse DNS resolution is the opposite of forward DNS resolution; forward DNS resolution uses A records for lookup, while reverse DNS resolution uses PTR records.

[0003] Existing reverse DNS resolution solutions rely on manual configuration of PTR record updates to achieve reverse domain name resolution, which cannot achieve the new level of operation and maintenance that is non-cooperative, imperceptible to the terminal, and adaptive to switching.

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

[0005] The purpose of this disclosure is to provide a reverse domain name resolution method, apparatus, device, medium, and product to overcome, at least to some extent, the problems of poor reliability of reverse domain name resolution schemes caused by the limitations and defects of related technologies.

[0006] According to a first aspect of the present disclosure, a reverse domain name resolution method is provided, applicable to a local DNS server, wherein the local DNS server is capable of data interaction with a reverse domain name resolution protection server, the reverse domain name resolution method comprising: responding to a reverse domain name resolution request sent by a terminal, detecting the operating status of a local reverse domain name resolution link; and determining, based on the operating status, whether to import a reverse domain name resolution record from a local Zone file, wherein the reverse domain name resolution record is used to provide reverse domain name resolution services to the terminal.

[0007] In one exemplary embodiment of this disclosure, determining whether to import reverse DNS records from a local Zone file based on the operating state, wherein the reverse DNS records are used to provide reverse DNS services to the terminal, includes:

[0008] Check if access to the reverse domain name authority server is possible;

[0009] In response to the detection that the reverse domain name authority server cannot be accessed, the operating state is determined to be a link failure state;

[0010] In response to the running status being a link failure state, the reverse DNS record in the local Zone file is imported.

[0011] In one exemplary embodiment of this disclosure, it further includes:

[0012] In response to the detection that access to the reverse domain name authority server is possible, the reverse domain name resolution request is sent to the reverse domain name authority server for resolution;

[0013] Receive the resolution result corresponding to the reverse domain name resolution request from the reverse domain name authority server.

[0014] In one exemplary embodiment of this disclosure, it further includes:

[0015] In response to a request from the reverse DNS protection server to collect raw DNS records, the local raw DNS records are sent to the reverse DNS protection server corresponding to the collection request.

[0016] In one exemplary embodiment of this disclosure, it further includes:

[0017] The system receives a Zone file sent by the reverse DNS protection server and stores it as a local Zone file. The Zone file is configured to be generated from the original DNS resolution data records and includes PTR records.

[0018] According to a second aspect of the present disclosure, a reverse domain name resolution method is provided, applicable to a reverse domain name resolution protection server, wherein the reverse domain name resolution protection server is capable of data interaction with a local DNS server, and the reverse domain name resolution method includes:

[0019] Send a request to the Local DNS server to collect reverse raw resolution data records;

[0020] Receive the raw resolution data record sent by the LocalDNS server;

[0021] A Zone file is generated based on the original parsed data records, and the Zone file includes PTR records;

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

[0023] In one exemplary embodiment of this disclosure, generating a Zone file based on the original parsed data record includes:

[0024] The received raw DNS records are cleaned to generate a reverse DNS record base library.

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

[0026] The Zone file is generated based on the reverse DNS resolution dimension table.

[0027] In one exemplary embodiment of this disclosure, data cleaning processing is performed on the received raw DNS records to generate a reverse DNS record base library, including:

[0028] The data source information of the original resolved data record is determined, and the data source information includes the identity 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 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, 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.

[0031] In one exemplary embodiment of this disclosure, determining whether to perform data cleaning processing on the received original DNS resolution data records to generate a reverse DNS resolution record base library, based on the determination result of whether the original DNS resolution data records have been stored in the reverse DNS resolution dimension table, includes:

[0032] Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test.

[0033] In response to the verification of the original parsed data record through the forward parsing test, the parsing result in the original parsed data record is parsed to see if it points to the existing FQDN;

[0034] In response to the parsing result in the original parsed data record pointing to an existing FQDN, the parsing results pointing to the same existing FQDN are merged.

[0035] In response to the fact that the parsing result in the original parsed data record does not point to any existing FQDN, the corresponding FQDN is determined and stored based on the parsing result;

[0036] In response to completing the merging of resolution results pointing to the same existing FQDN or determining and storing the corresponding FQDN based on the resolution results, the original resolution data records are cleaned to generate a reverse domain name resolution record base library.

[0037] In one exemplary embodiment of this disclosure, determining whether to perform data cleaning processing on the received original DNS resolution data records to generate a reverse DNS resolution record base library, based on the determination result of whether the original DNS resolution data records have been stored in the reverse DNS resolution dimension table, includes:

[0038] Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test.

[0039] If the original parsed data record fails the forward parsing test verification, the original parsed data record is discarded.

[0040] In one exemplary embodiment of this disclosure, determining whether to perform data cleaning processing on the received original DNS resolution data records to generate a reverse DNS resolution record base library, based on the determination result of whether the original DNS resolution data records have been stored in the reverse DNS resolution dimension table, includes:

[0041] In response to the fact that the domain name in the resolution result of the original resolution data record is not stored in the reverse domain name resolution dimension table, it is determined whether the IP in the resolution result of the original resolution data record is a newly added IP;

[0042] If the IP address in the resolution result of the original resolution data record is the newly added IP address, a forward resolution test is performed on the original resolution data record to verify it.

[0043] If the IP address in the resolution result of the original resolution data record is not the newly added IP address, the received original resolution data record is cleaned to generate a reverse domain name resolution record base library.

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

[0045] In one exemplary embodiment of this disclosure, extracting resolution data that meets the requirements of the Local DNS server from the reverse DNS record base library to generate the reverse DNS server dimension table includes:

[0046] Determine whether the original DNS resolution records in the reverse DNS record benchmark database meet the data timeliness requirements;

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

[0048] If the domain name of the resolution result in the original resolution data record is not the specified domain name of the Local DNS server, determine whether the request volume of the resolution result has reached the request volume threshold.

[0049] If the number of requests for the resolution result reaches the request volume threshold, or if the domain name of the resolution result in the original resolution data record is a specified domain name of the Local DNS server, the identity information of the Local DNS server to which the original resolution data record belongs is determined.

[0050] The reverse domain name resolution dimension table query is performed on the original resolved data record based on the identity identifier;

[0051] In response to the reverse DNS resolution dimension table query determining that the original DNS resolution data record includes a new resolution result, the original DNS resolution data record including the new resolution result is injected into the reverse DNS resolution dimension table;

[0052] If the original resolution data record does not meet the data timeliness requirement, or the number of requests for the resolution result does not reach the request volume threshold, or the reverse domain name resolution dimension table query determines that the original resolution data record does not include new resolution results, the original resolution data record is discarded.

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

[0054] According to a third aspect of the present disclosure, a reverse domain name resolution apparatus is provided, suitable for a local DNS server, wherein the local DNS server is capable of data interaction with a reverse domain name resolution protection server, and the reverse domain name resolution method includes the following:

[0055] The detection module is configured to respond to reverse DNS resolution requests sent by the terminal and detect the running status of the local reverse DNS resolution link.

[0056] The import module is configured to determine whether to import reverse DNS records from the local Zone file based on the running status. These reverse DNS records are used to provide reverse DNS services to the terminal.

[0057] According to a fourth aspect of the present disclosure, a reverse domain name resolution apparatus is provided, suitable for a reverse domain name resolution protection server, wherein the reverse domain name resolution protection server is capable of data interaction with a local DNS server, and the reverse domain name resolution apparatus includes:

[0058] The sending module is configured to send a request to the Local DNS server to collect reverse raw resolution data records;

[0059] The receiving module is configured to receive the raw resolution data records sent by the Local DNS server;

[0060] The generation module is configured to generate a Zone file based on the original parsed data records, wherein the Zone file includes PTR records;

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

[0062] According to a fifth aspect of this disclosure, an electronic device is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform the method as described in any one of the preceding methods based on instructions stored in the memory.

[0063] According to a sixth aspect of this disclosure, a computer-readable storage medium is provided having a program stored thereon that, when executed by a processor, implements the reverse domain name resolution method as described in any of the preceding claims.

[0064] According to a seventh aspect of this disclosure, a computer program product is provided, comprising a computer program, characterized in that, when executed by a processor, the computer program implements the reverse domain name resolution method as described in any of the preceding claims.

[0065] In this embodiment, in response to a reverse DNS resolution request sent by the terminal, the operating status of the local reverse DNS resolution link is detected, and then the reverse DNS resolution record in the local Zone file is imported based on the operating status. The reverse DNS resolution record is used to provide reverse DNS resolution services to the terminal, which improves the reliability of the reverse DNS resolution scheme. Even in extreme cases such as the interruption of the domain root, top-level domain, and authoritative services, the reverse DNS resolution service can still be provided to the terminal. Under the premise that the Local DNS does not require administrator configuration and does not need to maintain a network connection with the protection platform, reverse DNS resolution protection can be adaptively implemented based on the original DNS resolution protection snapshot.

[0066] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0067] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0068] Figure 1 This is a schematic diagram of a reverse domain name resolution scheme in related technologies;

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

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

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

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

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

[0074] Figure 7 This is a block diagram of a reverse domain name resolution apparatus according to an exemplary embodiment of this disclosure;

[0075] Figure 8 This is a block diagram of another reverse domain name resolution apparatus in an exemplary embodiment of this disclosure;

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

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

[0078] Figure 11 This is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

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

[0080] Furthermore, the accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus repeated descriptions of them will be omitted. Some 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, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0081] like Figure 1 As shown, the reverse DNS (Domain Name System) domain name lookup scheme in related technologies involves the LocalDNS104 server resolving the IP address requested by terminal 102 from the reverse domain name authority server 106 into the original corresponding domain name through reverse domain name resolution. Reverse domain name resolution and forward domain name resolution are the opposite processes; forward domain name resolution uses A records for lookup, while reverse domain name resolution uses PTR records (Pointer Records). The most common TLDs for reverse domain name resolution are "in-addr.arpa" and "ip6.arpa", but are not limited to these.

[0082] In the domain name system, the TLD (Top-Level Domain) is the highest-level classification identifier, located on the far right of the domain name. It is used to classify the type of internet resources or their country / region of origin, such as .com (commercial), .org (non-profit organizations), or .cn (China), etc. The most common TLDs in reverse DNS schemes are not traditional general or country-code top-level domains, but special structures specifically used for reverse DNS lookup, as follows:

[0083] (1) IPv4 reverse lookup TLD uses .in-addr.arpa. For example, the reverse lookup record for 192.168.1.42 is located in the 42.1.168.192.in-addr.arpa domain.

[0084] (2) IPv6 reverse lookup TLD uses .ip6.arpa. For example, the reverse lookup record for 2001:db8::1 is located in the domain 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.bd0.1.0.0.2.ip6.arpa.

[0085] Existing reverse DNS lookup protection schemes have at least the following technical problems:

[0086] Existing domain name resolution protection schemes mainly protect the reverse domain name authoritative server 106, such as by establishing a distributed authoritative server cluster (backup server 108), redundant network lines, and server DDoS attack protection, but they fail to cope with protection in extreme situations such as the interruption of domain name root and top-level domain services.

[0087] Existing reverse DNS resolution protection solutions require manual configuration changes by authoritative server administrators, which cannot achieve the new level of operation and maintenance that is non-cooperative, imperceptible to terminals, and adaptive to switching.

[0088] This public example, through in-depth research on reverse domain name resolution services, proposes a new reverse domain name resolution scheme based on the characteristics of reverse domain name resolution data. Specifically, it constructs a reverse domain name resolution data resource dimension table based on data collection and fusion methods, and utilizes the domain name protection system in collaboration with the local DNS server to provide a non-cooperative, adaptive resolution protection technology scheme for reverse domain name resolution.

[0089] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0090] Figure 2 This is a flowchart of the reverse domain name resolution method in an exemplary embodiment of this disclosure.

[0091] refer to Figure 2 Reverse DNS resolution methods can include:

[0092] Step S202: In response to the reverse DNS resolution request sent by the terminal, check the running status of the local reverse DNS resolution link;

[0093] Step S204: Determine whether to import the reverse DNS record in the local Zone file based on the running status. The reverse DNS record is used to provide reverse DNS service for the terminal.

[0094] In this embodiment, in response to a reverse DNS resolution request sent by the terminal, the operating status of the local reverse DNS resolution link is detected, and then the reverse DNS resolution record in the local Zone file is imported based on the operating status. The reverse DNS resolution record is used to provide reverse DNS resolution services to the terminal, which improves the reliability of the reverse DNS resolution scheme. Even in extreme cases such as the interruption of the domain root, top-level domain, and authoritative services, the reverse DNS resolution service can still be provided to the terminal. Under the premise that the Local DNS does not require administrator configuration and does not need to maintain a network connection with the protection platform, reverse DNS resolution protection can be adaptively implemented based on the original DNS resolution protection snapshot.

[0095] The following is a detailed explanation of each step in the reverse DNS lookup method.

[0096] In one exemplary embodiment of this disclosure, determining whether to import reverse DNS records from a local Zone file based on the operating state, wherein the reverse DNS records are used to provide reverse DNS services to the terminal, includes:

[0097] Check if access to the reverse domain name authority server is possible;

[0098] In response to the detection that the reverse domain name authority server cannot be accessed, the operating state is determined to be a link failure state;

[0099] In response to the running status being a link failure state, the reverse DNS record in the local Zone file is imported.

[0100] In the above embodiments, raw DNS records are collected and distributed to each Local DNS server. After data cleaning, fusion (complementarity), confidence verification, and resolution dimension table construction, Zone files for each reverse DNS protection domain are generated and sent back to each Local DNS server. Specifically, when a link failure is detected, the original reverse DNS link is interrupted. The Local DNS server activates its emergency protection function, importing data from pre-prepared Zone files for resolution protection to continue providing reverse DNS query services to the terminal.

[0101] In one exemplary embodiment of this disclosure, it further includes:

[0102] In response to the detection that access to the reverse domain name authority server is possible, the reverse domain name resolution request is sent to the reverse domain name authority server for resolution;

[0103] Receive the resolution result corresponding to the reverse domain name resolution request from the reverse domain name authority server.

[0104] In one exemplary embodiment of this disclosure, it further includes:

[0105] In response to a request from the reverse DNS protection server to collect raw DNS records, the local raw DNS records are sent to the reverse DNS protection server corresponding to the collection request.

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

[0107] Table 1

[0108]

[0109] In one exemplary embodiment of this disclosure, it further includes:

[0110] The system receives a Zone file sent by the reverse DNS protection server and stores it as a local Zone file. The Zone file is configured to be generated from the original DNS resolution data records and includes PTR records.

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

[0112] refer to Figure 3 A reverse DNS lookup method is provided, applicable to a reverse DNS lookup protection server, which is capable of data interaction with a local DNS server. The reverse DNS lookup method includes:

[0113] Step S302: Send a request to the Local DNS server to collect reverse raw resolution data records;

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

[0115] Step S306: Generate a Zone file based on the original parsed data record, wherein the Zone file includes PTR records;

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

[0117] In this embodiment, by sending a request to the Local DNS server to collect reverse original DNS resolution data records, receiving the original DNS resolution data records sent by the Local DNS server, generating a Zone file based on the original DNS resolution data records, and then sending the Zone file to the corresponding Local DNS server, reverse DNS resolution service can be provided to the terminal even in extreme cases such as the interruption of domain root, top-level domain, and authoritative services. Under the premise that the Local DNS does not require administrator configuration and does not need to maintain a network connection with the protection platform, reverse DNS resolution protection can be adaptively implemented based on the original DNS resolution protection snapshot.

[0118] The following is a detailed explanation of each step in the reverse DNS lookup method.

[0119] In one exemplary embodiment of this disclosure, generating a Zone file based on the original parsed data record includes:

[0120] The received raw DNS records are cleaned to generate a reverse DNS record base library.

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

[0122] The Zone file is generated based on the reverse DNS resolution dimension table.

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

[0124] Table 2

[0125]

[0126] In one exemplary embodiment of this disclosure, data cleaning processing is performed on the received raw DNS records to generate a reverse DNS record base library, including:

[0127] The data source information of the original resolved data record is determined, and the data source information includes the identity information of the LocalDNS server;

[0128] Query the reverse domain name resolution dimension table corresponding to the Local DNS server pointed to by the identity 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;

[0129] 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, 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.

[0130] In one exemplary embodiment of this disclosure, determining whether to perform data cleaning processing on the received original DNS resolution data records to generate a reverse DNS resolution record base library, based on the determination result of whether the original DNS resolution data records have been stored in the reverse DNS resolution dimension table, includes:

[0131] Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test.

[0132] In response to the verification of the original parsed data record through the forward parsing test, the parsing result in the original parsed data record is parsed to see if it points to the existing FQDN;

[0133] In response to the parsing result in the original parsed data record pointing to an existing FQDN, the parsing results pointing to the same existing FQDN are merged.

[0134] In response to the fact that the parsing result in the original parsed data record does not point to any existing FQDN, the corresponding FQDN is determined and stored based on the parsing result;

[0135] In response to completing the merging of resolution results pointing to the same existing FQDN or determining and storing the corresponding FQDN based on the resolution results, the original resolution data records are cleaned to generate a reverse domain name resolution record base library.

[0136] In the above embodiments, FQDN (Fully Qualified Domain Name) refers to a clear and complete hierarchical address identifier in the Domain Name System, including the hostname and all parent domains, ending with a dot (e.g., host.example.com). Reverse lookup maps an IP address (e.g., 192.168.1.1) to the corresponding FQDN (e.g., host.example.com), which is accomplished using PTR records in the .arpa domain. For example, the reverse lookup query target for IPv4 address 192.168.1.1 is 1.1.168.192.in-addr.arpa. (in FQDN form), and its PTR record returns the associated FQDN. The FQDN ensures the accuracy of reverse lookup and the verifiability of service identity through global uniqueness.

[0137] In one exemplary embodiment of this disclosure, such as Figure 4 As shown, the process of cleaning the collected raw DNS resolution data records to generate a reverse DNS resolution record base library in the reverse DNS resolution method includes:

[0138] Step S402, raw sampling data record, that is, obtain the raw resolution data record 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: Should a new reverse DNS lookup domain be added? If yes, proceed to step S410; otherwise, proceed to step S408.

[0141] Step S408: Has the resolution result been updated? Specifically, determine whether the IP address in the resolution result is a newly added IP address. If yes, proceed to step S410; otherwise, proceed to step S416.

[0142] Step S410: Forward parsing test verification, does it pass? If yes, proceed to step S412; otherwise, proceed to step S414.

[0143] Step S412: Check if the parsing result points to an existing FQDN. If the FQDNs are the same, the parsing results need to be merged; otherwise, save them separately.

[0144] Step S414: Invalid data, discard.

[0145] Step S416: Cleaning passed, update and save.

[0146] In one exemplary embodiment of this disclosure, determining whether to perform data cleaning processing on the received original DNS resolution data records to generate a reverse DNS resolution record base library, based on the determination result of whether the original DNS resolution data records have been stored in the reverse DNS resolution dimension table, includes:

[0147] Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test.

[0148] If the original parsed data record fails the forward parsing test verification, the original parsed data record is discarded.

[0149] In one exemplary embodiment of this disclosure, determining whether to perform data cleaning processing on the received original DNS resolution data records to generate a reverse DNS resolution record base library, based on the determination result of whether the original DNS resolution data records have been stored in the reverse DNS resolution dimension table, includes:

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

[0151] If the IP address in the resolution result of the original resolution data record is the newly added IP address, a forward resolution test is performed on the original resolution data record to verify it.

[0152] If the IP address in the resolution result of the original resolution data record is not the newly added IP address, the received original resolution data record is cleaned to generate a reverse domain name resolution record base library.

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

[0154] In one exemplary embodiment of this disclosure, extracting resolution data that meets the requirements of the LocalDNS server from the reverse DNS record base library to generate the reverse DNS server dimension table includes:

[0155] Determine whether the original DNS resolution records in the reverse DNS record benchmark database meet the data timeliness requirements;

[0156] In response to the original resolution data record meeting the data timeliness requirement, it is determined whether the domain name of the resolution result in the original resolution data record is the specified domain name of the Local DNS server;

[0157] If the domain name of the resolution result in the original resolution data record is not the specified domain name of the Local DNS server, determine whether the request volume of the resolution result has reached the request volume threshold.

[0158] If the number of requests for the resolution result reaches the request volume threshold, or if the domain name of the resolution result in the original resolution data record is a specified domain name of the Local DNS server, the identity information of the Local DNS server to which the original resolution data record belongs is determined.

[0159] The reverse domain name resolution dimension table query is performed on the original resolved data record based on the identity identifier;

[0160] In response to the reverse DNS resolution dimension table query determining that the original DNS resolution data record includes a new resolution result, the original DNS resolution data record including the new resolution result is injected into the reverse DNS resolution dimension table;

[0161] If the original resolution data record does not meet the data timeliness requirement, or the number of requests for the resolution result does not reach the request volume threshold, or the reverse domain name resolution dimension table query determines that the original resolution data record does not include new resolution results, the original resolution data record is discarded.

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

[0163] In one exemplary embodiment of this disclosure, in accordance with Figure 4 Based on the steps shown to generate a reverse DNS record base library, such as Figure 5 As shown, the process of cleaning the collected raw DNS resolution data records to generate a reverse DNS resolution record base library in the reverse DNS resolution method includes:

[0164] Step S502: Import the benchmark data source from the reverse DNS record benchmark database.

[0165] Step S504: Is the data timeliness feasible? If yes, proceed to step S506; otherwise, proceed to step S516.

[0166] Step S506: Should the domain name be given priority protection? If yes, proceed to step S510; otherwise, proceed to step S508.

[0167] Step S508: Has the request volume reached the protection threshold? If yes, proceed to step S510; otherwise, proceed to step S516.

[0168] Step S510: Categorize data by city of origin.

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

[0170] Step S514: Has the data record been refreshed? If yes, proceed to step S518; otherwise, proceed to step S516.

[0171] Step S516: Discard the data.

[0172] Step S518: Data injection and saving.

[0173] Based on the Local DNS server and reverse domain name resolution protection server 604 shown in the above embodiments, the reverse domain name resolution steps are performed, such as... Figure 6 As shown, the steps performed by the reverse DNS resolution system, consisting of LocalDNS server 602 and reverse DNS protection server 604, include:

[0174] A new dedicated reverse DNS protection server, 604, should be added, ideally deployed in a secure and controlled network. A reverse DNS protection module needs to be added to the telecom operator's Local DNS server, 602, while no changes are required to other operator servers at any level.

[0175] First, reverse DNS resolution resources are constructed. The reverse DNS resolution protection server 604 initiates reverse DNS resolution data collection tasks to local DNS servers 602 at all levels through a unified collection interface. Data collection needs to be carried out continuously and periodically to ensure the validity and accuracy of the collected data.

[0176] Secondly, the reverse DNS protection system cleans, trusts, merges, and consolidates the collected data to construct reverse DNS protection data and generates emergency resolution Zone files. Finally, the reverse DNS protection system periodically sends emergency resolution Zone files to various Local DNS servers (602).

[0177] At this point, the preliminary preparation process for reverse DNS resolution protection is complete, and the system is now capable of providing reverse DNS resolution protection.

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

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

[0180] Figure 7 This is a block diagram of a reverse domain name resolution apparatus according to an exemplary embodiment of the present disclosure.

[0181] refer to Figure 7 A reverse DNS resolution device is provided, suitable for a LocalDNS server, wherein the LocalDNS server is capable of data interaction with a reverse DNS resolution protection server. The reverse DNS resolution device 700 may include:

[0182] The detection module 702 is configured to detect the operating status of the local reverse DNS resolution link in response to a reverse DNS resolution request sent by the terminal.

[0183] Import module 704 is configured to determine whether to import reverse DNS records from the local Zone file based on the running status. The reverse DNS records are used to provide reverse DNS services for the terminal.

[0184] In one exemplary embodiment of this disclosure, the import module 704 is further configured as follows:

[0185] Check if access to the reverse domain name authority server is possible;

[0186] In response to the detection that the reverse domain name authority server cannot be accessed, the operating state is determined to be a link failure state;

[0187] In response to the running status being a link failure state, the reverse DNS record in the local Zone file is imported.

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

[0189] In response to the detection that access to the reverse domain name authority server is possible, the reverse domain name resolution request is sent to the reverse domain name authority server for resolution;

[0190] Receive the resolution result corresponding to the reverse domain name resolution request from the reverse domain name authority server.

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

[0192] In response to a request from the reverse DNS protection server to collect raw DNS records, the local raw DNS records are sent to the reverse DNS protection server corresponding to the collection request.

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

[0194] The system receives a Zone file sent by the reverse DNS protection server and stores it as a local Zone file. The Zone file is configured to be generated from the original DNS resolution data records and includes PTR records.

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

[0196] Figure 8 This is a block diagram of a reverse domain name resolution apparatus according to an exemplary embodiment of the present disclosure.

[0197] refer to Figure 8A reverse DNS resolution device 800 is provided, suitable for a reverse DNS resolution protection server, wherein the reverse DNS resolution protection server is capable of data interaction with a local DNS server, and the reverse DNS resolution device 800 includes:

[0198] The sending module 802 is configured to send a request for collecting reverse raw resolution data records to the LocalDNS server;

[0199] The receiving module 804 is configured to receive the raw resolution data records sent by the LocalDNS server;

[0200] The generation module 806 is configured to generate a Zone file based on the original parsed data records, wherein the Zone file includes PTR records;

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

[0202] In one exemplary embodiment of this disclosure, the generation module 806 is further configured to:

[0203] The received raw DNS records are cleaned to generate a reverse DNS record base library.

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

[0205] The Zone file is generated based on the reverse DNS resolution dimension table.

[0206] In one exemplary embodiment of this disclosure, the generation module 806 is further configured to:

[0207] The data source information of the original resolved data record is determined, and the data source information includes the identity information of the LocalDNS server;

[0208] Query the reverse domain name resolution dimension table corresponding to the Local DNS server pointed to by the identity 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;

[0209] 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, 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.

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

[0211] Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test.

[0212] In response to the verification of the original parsed data record through the forward parsing test, the parsing result in the original parsed data record is parsed to see if it points to the existing FQDN;

[0213] In response to the parsing result in the original parsed data record pointing to an existing FQDN, the parsing results pointing to the same existing FQDN are merged.

[0214] In response to the fact that the parsing result in the original parsed data record does not point to any existing FQDN, the corresponding FQDN is determined and stored based on the parsing result;

[0215] In response to completing the merging of resolution results pointing to the same existing FQDN or determining and storing the corresponding FQDN based on the resolution results, the original resolution data records are cleaned to generate a reverse domain name resolution record base library.

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

[0217] Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test.

[0218] If the original parsed data record fails the forward parsing test verification, the original parsed data record is discarded.

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

[0220] In response to the fact that the domain name in the resolution result of the original resolution data record is not stored in the reverse domain name resolution dimension table, it is determined whether the IP in the resolution result of the original resolution data record is a newly added IP;

[0221] If the IP address in the resolution result of the original resolution data record is the newly added IP address, a forward resolution test is performed on the original resolution data record to verify it.

[0222] If the IP address in the resolution result of the original resolution data record is not the newly added IP address, the received original resolution data record is cleaned to generate a reverse domain name resolution record base library.

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

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

[0225] Determine whether the original DNS resolution records in the reverse DNS record benchmark database meet the data timeliness requirements;

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

[0227] If the domain name of the resolution result in the original resolution data record is not the specified domain name of the Local DNS server, determine whether the request volume of the resolution result has reached the request volume threshold.

[0228] If the number of requests for the resolution result reaches the request volume threshold, or if the domain name of the resolution result in the original resolution data record is a specified domain name of the Local DNS server, the identity information of the Local DNS server to which the original resolution data record belongs is determined.

[0229] The reverse domain name resolution dimension table query is performed on the original resolved data record based on the identity identifier;

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

[0231] If the original resolution data record does not meet the data timeliness requirement, or the number of requests for the resolution result does not reach the request volume threshold, or the reverse domain name resolution dimension table query determines that the original resolution data record does not include new resolution results, the original resolution data record is discarded.

[0232] In one exemplary embodiment of this 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 respective method embodiments, they will not be repeated here.

[0234] In one exemplary embodiment of this disclosure, in view of the business characteristics of reverse domain name resolution, such as relatively monotonous data format, simple resolution process, and far fewer accesses than forward domain name resolution, this application proposes a reverse resolution protection system 900.

[0235] like Figure 9 and Figure 10 As shown, the reverse DNS resolution protection system 900 proposed in this application is implemented based on the functions of the aforementioned reverse DNS resolution devices 700 and 800. The reverse DNS resolution protection system 900 constructs reverse DNS resolution protection data through distributed data collection, cleaning, and confidence processes, and generates a fault emergency Zone resolution file. When a risk occurs, for example, when the reverse DNS resolution protection module 1002 or the LocalDNS server 904 cannot access the reverse DNS authority server 906, the LocalDNS server 904 imports the resolution protection data and continues to provide reverse DNS resolution query services to the terminal 902.

[0236] In one exemplary embodiment of this disclosure, a dedicated reverse DNS protection server is added, preferably deployed in a secure and controlled network.

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

[0238] In one exemplary embodiment of this disclosure, the reverse DNS protection server 908 first sends the raw resolution data records to each LocalDNS server 904, and then, after data cleaning, fusion (complementary), confidence and resolution dimension table construction, generates each reverse DNS protection domain name Zone file, which is then sent back to each LocalDNS server 904.

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

[0240] The core functional modules for implementing reverse DNS resolution protection are explained in detail below.

[0241] (1) The LocalDNS server 904 adds a reverse lookup protection module 1002, which includes the following functions:

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

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

[0244] (2) Reverse DNS resolution protection start / stop management includes:

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

[0246] (2.2) Activate the emergency parsing function and import the pre-prepared Zone file parsing data;

[0247] (2.3) Stop the parsing protection service and restore the normal recursive service.

[0248] (3) Description of the main functions of the 900 core module of the reverse analysis protection system:

[0249] In one exemplary embodiment of this disclosure, reverse domain name resolution data collection refers to periodically collecting raw sampled reverse domain name resolution data from various LocalDNS servers 904.

[0250] In one exemplary embodiment of this disclosure, constructing the reverse domain name resolution data benchmark library involves constructing the reverse domain name resolution data benchmark library through the data cleaning, fusion, and data confidence process proposed in this application.

[0251] In one exemplary embodiment of this disclosure, generating a local DNS server 904 resolution data dimension table means extracting resolution data that meets the requirements of the local DNS server 904 from the baseline library according to the resolution protection policy, and generating a resolution dimension table suitable for the local DNS server 904.

[0252] In one exemplary embodiment of this disclosure, the Zone file synchronization update is achieved based on the resolution of dimension table data, synthesizing a Zone file for the reverse domain name resolution protected domain name, and performing timely synchronization update management and distribution to the LocalDNS server 904.

[0253] (4) The construction method and processing flow of the reverse domain name resolution data benchmark database include:

[0254] (4.1) The reverse DNS protection system 900 periodically sends the reverse DNS data collection list and policy to the Local DNS server 904, and collects the collection results at the same time. The key information fields of the collection list are also the key fields for building the reverse DNS 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 DNS protection system 900 identifies the data source, queries the corresponding data dimension table of the data source location, searches and compares the original reverse DNS data, determines whether new data has been added, whether forward testing is required, and whether result merging is required, etc. Finally, useful data is saved into the database, and a reverse DNS data benchmark database is gradually built.

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

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

[0258] (5.2) This application takes into account multiple dimensions such as data timeliness, whether the domain name is a key protected domain name, and the number of domain name requests, and generates a reverse domain name resolution data dimension table for each Local DNS server 904 based on the location of the data source.

[0259] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of 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 this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0261] Those skilled in the art will understand that various aspects of this application can be implemented as a system, method, or program product. Therefore, various aspects of this application can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, collectively referred to herein as a "circuit," "module," or "system."

[0262] The following reference Figure 11 To describe an electronic device 1100 according to this embodiment of the present application. Figure 11 The electronic device 1100 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0263] like Figure 11 As shown, the electronic device 1100 is manifested 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 processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including storage unit 1120 and processing unit 1110).

[0264] The storage unit stores program code that can be executed by the processing unit 1110, causing the processing unit 1110 to perform the steps described in the "Exemplary Methods" section above, according to various exemplary embodiments of this application. For example, the processing unit 1110 can perform the method shown in the embodiments of this disclosure.

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

[0266] Storage unit 1120 may also include a program / utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0267] Bus 1130 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0268] Electronic device 1100 can also communicate with one or more external devices 1140 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a terminal to interact with electronic device 1100, and / or with any device that enables electronic device 1100 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1150. Furthermore, electronic device 1100 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with 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.

[0269] In summary, the embodiments disclosed herein have at least the following significant advantages over the prior art:

[0270] (1) A method for constructing reverse DNS resolution protection resources is proposed, specifically including: a LocalDNS reverse DNS resolution protection module, a core functional module of the reverse DNS resolution protection system, and the construction and definition of a reverse DNS resolution data benchmark library. Compared with existing technologies, this method of constructing resolution resources is novel, enabling resolution protection to operate independently of existing resolution links and providing more reliable and effective resolution protection. Even in extreme situations such as the interruption of domain root, top-level domain, and authoritative services, resolution protection services can still be provided.

[0271] (2) By providing independent reverse domain name resolution protection management for each LocalDNS, including targeted reverse domain name resolution dimension table generation rules for LocalDNS and automatic start and stop management of reverse domain name resolution protection, dynamic and intelligent reverse domain name resolution protection is realized. LocalDNS does not require administrator configuration or network connection with the protection platform. It can adaptively realize domain name resolution protection based on the original resolution protection snapshot.

[0272] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0273] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible implementations, various aspects of this application may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of this application described in the "Exemplary Methods" section above.

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

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

[0276] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

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

[0278] In exemplary embodiments of this disclosure, a computer program product is also provided. This computer program product can be loaded or stored using any combination of one or more readable media. The program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a terminal computing device, partially on a terminal computing device, as a standalone software package, partially on a terminal computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the terminal computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0279] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this application, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0280] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and concept of this disclosure are indicated by the claims.

Claims

1. A reverse domain name resolution method, characterized by, This applies to a Local DNS server, which is capable of interacting with a reverse DNS protection server. The reverse DNS method includes: In response to a reverse DNS resolution request sent by the terminal, detect the running status of the local reverse DNS resolution link; Based on the running status, determine whether to import the reverse DNS resolution record from the local Zone file. The reverse DNS resolution record is used to provide reverse DNS resolution service for the terminal. In response to a request from the reverse DNS protection server to collect raw DNS records, the local raw DNS records are sent to the reverse DNS protection server corresponding to the collection request. The system receives a Zone file sent by the reverse DNS protection server and stores it as a local Zone file. The Zone file is configured to be generated from the original DNS resolution data records and includes PTR records.

2. The reverse domain name resolution method of claim 1, wherein, Based on the operating status, determine whether to import the reverse DNS resolution record from the local Zone file. The reverse DNS resolution record is used to provide reverse DNS resolution services to the terminal, including: Check if access to the reverse domain name authority server is possible; In response to the detection that the reverse domain name authority server cannot be accessed, the operating state is determined to be a link failure state; In response to the running status being a link failure state, the reverse DNS record in the local Zone file is imported.

3. The reverse domain name resolution method of claim 2, wherein, Also includes: In response to the detection that access to the reverse domain name authority server is possible, the reverse domain name resolution request is sent to the reverse domain name authority server for resolution; Receive the resolution result corresponding to the reverse domain name resolution request from the reverse domain name authority server.

4. The reverse domain name resolution method of claim 1, wherein, The reverse DNS record includes at least one of PTR records, DNS logs, and associated metadata.

5. A reverse domain name resolution method, characterized by, This applies to reverse DNS lookup protection servers, which are capable of interacting with local DNS servers. The reverse DNS lookup method includes: Send a request to the Local DNS server to collect reverse raw resolution data records; Receive the raw resolution data record sent by the Local DNS server; A Zone file is generated based on the original parsed data records. The Zone file includes PTR records, including: The received raw DNS records are cleaned to generate a reverse DNS record base library. Extract the resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record base library to generate the reverse domain name resolution dimension table of the Local DNS server; The Zone file is generated based on the reverse domain name resolution dimension table; Send the Zone file to the corresponding Local DNS server.

6. The reverse domain name resolution method of claim 5, wherein, The received raw DNS records undergo data cleaning processing to generate a reverse DNS record base library, including: The data source information of the original resolved data record is determined, and the data source information includes the identity 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 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; 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, 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.

7. The reverse domain name resolution method of claim 6, wherein, Based on the determination result of whether the original DNS resolution data record has been stored in the reverse DNS resolution dimension table, determining whether to perform data cleaning processing on the received original DNS resolution data record to generate a reverse DNS resolution record base library includes: Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test. In response to the verification of the original parsed data record through the forward parsing test, the parsing result in the original parsed data record is parsed to see if it points to the existing FQDN; In response to the parsing result in the original parsed data record pointing to an existing FQDN, the parsing results pointing to the same existing FQDN are merged. In response to the fact that the parsing result in the original parsed data record does not point to any existing FQDN, the corresponding FQDN is determined and stored based on the parsing result; In response to completing the merging of resolution results pointing to the same existing FQDN or determining and storing the corresponding FQDN based on the resolution results, the original resolution data records are cleaned to generate a reverse domain name resolution record base library.

8. The reverse domain name resolution method of claim 6, wherein, Based on the determination result of whether the original DNS resolution data record has been stored in the reverse DNS resolution dimension table, determining whether to perform data cleaning processing on the received original DNS resolution data record to generate a reverse DNS resolution record base library includes: Since the domain name in the resolution result of the original resolution data record has been stored in the reverse domain name resolution dimension table, the original resolution data record is verified by forward resolution test. If the original parsed data record fails the forward parsing test verification, the original parsed data record is discarded.

9. The reverse domain name resolution method of claim 6, wherein, Based on the determination result of whether the original DNS resolution data record has been stored in the reverse DNS resolution dimension table, determining whether to perform data cleaning processing on the received original DNS resolution data record to generate a reverse DNS resolution record base library includes: In response to the fact that the domain name in the resolution result of the original resolution data record is not stored in the reverse domain name resolution dimension table, it is determined whether the IP in the resolution result of the original resolution data record is a newly added IP; If the IP address in the resolution result of the original resolution data record is the newly added IP address, a forward resolution test is performed on the original resolution data record to verify it. If the IP address in the resolution result of the original resolution data record is not the newly added IP address, the received original resolution data record is cleaned to generate a reverse domain name resolution record base library.

10. The reverse domain name resolution method of any of claims 5-9, wherein, The data cleaning process includes at least one of the following: cleaning, confidence, fusion, and merging.

11. The reverse domain name resolution method of claim 5, wherein, Extracting DNS resolution data from the reverse DNS record base library that meets the requirements of the Local DNS server to generate the reverse DNS server dimension table includes: Determine whether the original DNS resolution records in the reverse DNS record benchmark database meet the data timeliness requirements; In response to the original resolution data record meeting the data timeliness requirement, it is determined whether the domain name of the resolution result in the original resolution data record is the specified domain name of the Local DNS server; If the domain name of the resolution result in the original resolution data record is not the specified domain name of the Local DNS server, determine whether the request volume of the resolution result has reached the request volume threshold. If the number of requests for the resolution result reaches the request volume threshold, or if the domain name of the resolution result in the original resolution data record is a specified domain name of the Local DNS server, the identity information of the Local DNS server to which the original resolution data record belongs is determined. The reverse domain name resolution dimension table query is performed on the original resolved data record based on the identity identifier; In response to the reverse DNS resolution dimension table query determining that the original DNS resolution data record includes a new resolution result, the original DNS resolution data record including the new resolution result is injected into the reverse DNS resolution dimension table; If the original resolution data record does not meet the data timeliness requirement, or the number of requests for the resolution result does not reach the request volume threshold, or the reverse domain name resolution dimension table query determines that the original resolution data record does not include new resolution results, the original resolution data record is discarded.

12. The reverse domain name resolution method of claim 5, wherein, The reverse DNS record includes at least one of PTR records, DNS logs, and associated metadata.

13. A reverse domain name resolution apparatus characterized by comprising: Applicable to a Local DNS server, the Local DNS server is capable of data interaction with a reverse DNS protection server, the reverse DNS resolution method, the reverse DNS resolution device includes: The detection module is configured to respond to reverse DNS resolution requests sent by the terminal and detect the running status of the local reverse DNS resolution link. The import module is configured to determine whether to import the reverse DNS resolution record in the local Zone file based on the running status. The reverse DNS resolution record is used to provide reverse DNS resolution service for the terminal. In response to a request from the reverse DNS protection server to collect raw DNS records, the local raw DNS records are sent to the reverse DNS protection server corresponding to the collection request. The system receives a Zone file sent by the reverse DNS protection server and stores it as a local Zone file. The Zone file is configured to be generated from the original DNS resolution data records and includes PTR records.

14. A reverse domain name resolution device, characterized in that, Suitable for reverse DNS lookup protection servers, the reverse DNS lookup protection server is capable of data interaction with local DNS servers, the reverse DNS lookup device includes: The sending module is configured to send a request to the Local DNS server to collect reverse raw resolution data records; The receiving module is configured to receive the raw resolution data records sent by the Local DNS server; The generation module is configured to generate a Zone file based on the original parsed data records. The Zone file includes PTR records, including: The received raw DNS records are cleaned to generate a reverse DNS record base library. Extract the resolution data that meets the requirements of the Local DNS server from the reverse domain name resolution record base library to generate the reverse domain name resolution dimension table of the Local DNS server; The Zone file is generated based on the reverse domain name resolution dimension table; The sending module is further configured to send the Zone file to the corresponding Local DNS server.

15. An electronic device, comprising: include: Memory; as well as A processor coupled to the memory, the processor being configured to execute the reverse domain name resolution method as described in any one of claims 1-12 based on instructions stored in the memory.

16. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the reverse domain name resolution method as described in any one of claims 1-12.

17. A computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the reverse domain name resolution method as described in any one of claims 1-12.

Images