Domain name resolution method and device, computer equipment and storage medium

Abstract

The invention relates to a domain name resolution method and device, computer equipment and a storage medium. The method comprises the following steps: generating next-hop analysis information according to a preset analysis link diagram under the condition of detecting that an analysis node of which the service is terminated exists in a domain name analysis system, and sending the next-hop analysis information to a local domain name server; the next-hop analysis information is used for indicating the local domain name server to query the received domain name. The resolution link diagram is pre-stored in the domain name resolution protection platform, so that the next-hop resolution information can be determined through the resolution link diagram under the condition that the existence of the service-terminated resolution node in the domain name resolution system is detected, and the next-hop resolution information can be determined through the resolution link diagram under the condition that the local domain name server cannot communicate with the service-terminated resolution node. And according to the next-hop analysis information, communicating with the next-hop analysis node, and querying the received domain name.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a domain name resolution method, device, computer equipment and storage medium. Background Art

[0002] When a client needs to access a web page or call a network function, it will initiate a query to the local domain name system (Local DNS) based on the URL. The local DNS will initiate a resolution query to the domain name authority server based on the URL. Further, through multiple jumps, the local DNS obtains the IP address corresponding to the URL and returns the web page or network function to the client based on the IP address. To ensure network security and the correctness of the IP address, the domain name resolution process needs to be protected.

[0003] In traditional technology, the domain name resolution process is protected by protecting the domain name authoritative server, such as establishing a distributed authoritative server group, redundant network lines, and server protection against DDOS attacks.

[0004] However, the traditional domain name resolution method cannot resolve the domain name in the case of service interruption, for example, the service provided by the domain name authoritative server, DNS scheduling server and other servers involved in the domain name resolution process is interrupted. Summary of the invention

[0005] Based on this, it is necessary to provide a domain name resolution method, device, computer equipment and storage medium that can resolve domain names in the event of service interruption to address the above technical problems.

[0006] In a first aspect, the present application provides a domain name resolution method, comprising:

[0007] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0008] The next hop resolution information is sent to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0009] In one embodiment, the generating the next hop resolution information according to the preset resolution link graph includes:

[0010] Determine a child node of the resolution node where the service is terminated in the preset resolution link graph;

[0011] The resolution information corresponding to the child node is determined as the next hop resolution information.

[0012] In one embodiment, the child node includes a plurality of resolution servers, and determining the resolution information corresponding to the child node as the next hop resolution information includes:

[0013] The resolution quantity corresponding to each of the resolution servers and the resolution information corresponding to the node are determined as the next-hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each of the resolution servers.

[0014] In one embodiment, the method for determining the number of resolutions corresponding to each resolution server includes:

[0015] Determining the resolution capability of each of the resolution servers;

[0016] The number of resolutions corresponding to each resolution server is determined according to the resolution capability of each resolution server.

[0017] In one embodiment, determining the resolution capability of each resolution server includes:

[0018] Determine the historical resolution times of each resolution server according to a preset link flow table;

[0019] The resolution capability of each resolution server is determined according to the historical resolution times of each resolution server.

[0020] In one embodiment, the method for obtaining the preset parsing link graph includes:

[0021] Receive historical domain name resolution data corresponding to the target domain name sent by the local domain name server;

[0022] According to the historical domain name resolution data, a plurality of resolution link data tables corresponding to the target domain name are constructed; each of the resolution link data tables includes resolution information of each resolution server on the corresponding link;

[0023] The preset parsing link graph is generated according to the multiple parsing link data tables.

[0024] In one embodiment, the method further comprises:

[0025] Detecting the status of each resolution server in the preset resolution link diagram;

[0026] When it is detected that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link graph to obtain an updated preset resolution link graph;

[0027] The generating the next hop resolution information according to the preset resolution link graph includes:

[0028] Next hop resolution information is generated according to the updated preset resolution link graph.

[0029] In a second aspect, the present application further provides a domain name resolution method, which is applied to a local domain name server, and the method includes:

[0030] Receiving next-hop resolution information sent by the domain name resolution protection platform; the next-hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system;

[0031] When the domain name is received, the domain name is queried according to the next hop resolution information.

[0032] In one embodiment, the method further comprises:

[0033] The historical domain name resolution data corresponding to the target domain name is sent to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

[0034] In a third aspect, the present application also provides a domain name resolution device, including:

[0035] A first generating module is used to generate next hop resolution information according to a preset resolution link diagram when detecting that there is a resolution node whose service is terminated in the domain name resolution system;

[0036] The first sending module is used to send the next hop resolution information to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0037] In a fourth aspect, the present application further provides a domain name resolution device, including:

[0038] The first receiving module is used to receive the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system;

[0039] The query module is used to query the domain name according to the next hop resolution information when receiving the domain name.

[0040] In a fifth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0041] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0042] The next hop resolution information is sent to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0043] In a sixth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0044] Receiving next-hop resolution information sent by the domain name resolution protection platform; the next-hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system;

[0045] When the domain name is received, the domain name is queried according to the next hop resolution information.

[0046] In a seventh aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0047] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0048] The next hop resolution information is sent to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0049] In an eighth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0050] Receiving next-hop resolution information sent by the domain name resolution protection platform; the next-hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system;

[0051] When the domain name is received, the domain name is queried according to the next hop resolution information.

[0052] In a ninth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0053] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0054] The next hop resolution information is sent to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0055] In a tenth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0056] Receiving next-hop resolution information sent by the domain name resolution protection platform; the next-hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system;

[0057] When the domain name is received, the domain name is queried according to the next hop resolution information.

[0058] The above-mentioned domain name resolution method, device, computer equipment and storage medium, when detecting that there is a resolution node with service termination in the domain name resolution system, generates next-hop resolution information according to a preset resolution link diagram, and sends the next-hop resolution information to a local domain name server; the next-hop resolution information is used to instruct the local domain name server to query the received domain name. The domain name resolution protection platform pre-stores the resolution link diagram, so that when detecting that there is a resolution node with service termination in the domain name resolution system, the next-hop resolution information can be determined through the resolution link diagram, so that when the local domain name server cannot communicate with the resolution node with service termination, it communicates with the next-hop resolution node according to the next-hop resolution information and queries the received domain name. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments of the present application or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0060] FIG1 is a diagram of an application environment of a domain name resolution method according to an embodiment;

[0061] FIG2 is a schematic diagram of a flow chart of a domain name resolution method in one embodiment;

[0062] FIG3 is a schematic diagram of parsing a link graph in one embodiment;

[0063] FIG4 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0064] FIG5 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0065] FIG6 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0066] FIG7 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0067] FIG8 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0068] FIG9 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0069] FIG10 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0070] FIG11 is a schematic diagram of a flow chart of a domain name resolution method in another embodiment;

[0071] FIG12 is a structural block diagram of a domain name resolution device in one embodiment;

[0072] FIG13 is a structural block diagram of a domain name resolution device in another embodiment;

[0073] FIG. 14 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0074] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0075] The domain name resolution method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, the local domain name server 102 communicates with the domain name resolution protection platform 104 through the network. The data storage system can store the data that the domain name resolution protection platform 104 needs to process. The data storage system can be integrated on the domain name resolution protection platform 104, or it can be placed on the cloud or other network servers. The domain name resolution protection platform 104 sends the next hop resolution information to the local domain name server 102. Among them, the local domain name server 10 can be an independent physical server, or it can be a server cluster or distributed system composed of multiple physical servers, or it can be a cloud server that provides cloud computing services. The domain name resolution protection platform 104 can be an independent physical server, or it can be a server cluster or distributed system composed of multiple physical servers, or it can be a cloud server that provides cloud computing services.

[0076] In one embodiment, as shown in FIG. 2 , a domain name resolution method is provided, which is described by taking the method applied to the domain name resolution protection platform in FIG. 1 as an example, including the following steps:

[0077] S201, when it is detected that there is a resolution node whose service is terminated in the domain name resolution system, next hop resolution information is generated according to a preset resolution link graph.

[0078] The next hop resolution information may be any one of the domain name information, hash value, and random number of the resolution node corresponding to the next hop.

[0079] In the embodiment of the present application, the resolution nodes in the domain name resolution system include domain name authority nodes, content delivery network (Content Delivery Network, CDN) traffic scheduling nodes, etc., each node includes at least one server, and the domain name resolution protection platform pre-establishes and stores the resolution link map. When it is detected that there is a resolution node with service termination in the domain name resolution system, the next hop resolution information is generated according to the resolution node with service termination and the preset resolution link map. As an optional implementation method, all link information corresponding to the resolution node can be determined from the preset resolution link map according to the resolution node with service termination, and all link information corresponding to the resolution node can be encapsulated in the form of a file as the next hop resolution information.

[0080] Optionally, the domain name resolution protection platform can determine whether there is a resolution node with terminated service in the domain name resolution system through information input by the user; or, the domain name resolution protection platform can determine whether there is a resolution node with terminated service in the domain name resolution system by receiving information from other management servers; or, the domain name resolution protection platform can determine whether there is a resolution node with terminated service in the domain name resolution system by sending a query request to the resolution node in the domain name resolution system.

[0081] Exemplarily, as shown in FIG3, the resolution link graph may be a tree graph, one domain name corresponds to one resolution link graph, and the resolution link graph includes multiple resolution links corresponding to the domain name. Different resolution links may also result in different number of hops for resolving the same domain name. Resolution node 1 includes server 1 and server 2, resolution node 2 includes server 3, server 4, and server 5, resolution node 3 includes server 6 and server 7, and the functions of the servers in each resolution node are the same.

[0082] S202, sending the next hop resolution information to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0083] In an embodiment of the present application, the next hop resolution information is sent to the local domain name server. When the local domain name server receives the domain name, it queries the server corresponding to the next hop based on the next hop resolution information, so that the server corresponding to the next hop resolves the domain name and sends the next hop resolution information to the local domain name server.

[0084] In the above domain name resolution method, when it is detected that there is a resolution node with service termination in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram, and the next hop resolution information is sent to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name. The domain name resolution protection platform pre-stores the resolution link diagram, so that when it is detected that there is a resolution node with service termination in the domain name resolution system, the next hop resolution information can be determined through the resolution link diagram, so that when the local domain name server cannot communicate with the resolution node with service termination, it can communicate with the next hop resolution node according to the next hop resolution information and query the received domain name.

[0085] In one embodiment, an implementation of the above S201 is provided, as shown in FIG4 , the above “generating next hop resolution information according to a preset resolution link graph” may include:

[0086] S301, determining a child node of a resolution node whose service is terminated in a preset resolution link graph.

[0087] In an embodiment of the present application, the position of the service-terminated resolution node in the preset resolution link graph is determined, the next position connected to the position is determined, and the resolution node corresponding to the next position is determined as a child node of the service-terminated resolution node. Exemplarily, as shown in FIG3, if the service-terminated resolution node is resolution node 2, resolution node 3 is determined as a child node of the service-terminated resolution node.

[0088] S302: Determine the resolution information corresponding to the child node as the next hop resolution information.

[0089] In the embodiment of the present application, the child node corresponds to at least one server, and the resolution information of at least one server is used as the next hop resolution information. For example, as shown in Figure 3, if the resolution node 3 is a child node, the resolution information of server 6 and server 7 is used as the next hop resolution information.

[0090] In the above application embodiment, when there is a resolution node with terminated service in the domain name resolution system, the child nodes of the resolution node with terminated service are determined according to the preset resolution link diagram, thereby determining the resolution information corresponding to the child nodes, thereby improving the accuracy of the next-hop resolution information.

[0091] In one embodiment, an implementation method of the above S302 is provided, and the child node includes multiple resolution servers. The above "determining the resolution information corresponding to the child node as the next-hop resolution information" may include: determining the resolution quantity corresponding to each resolution server and the resolution information corresponding to the node as the next-hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capabilities of each resolution server.

[0092] The number of resolutions corresponding to each resolution server is the number of times each resolution server can perform resolutions within a preset time period.

[0093] In the embodiment of the present application, the domain name resolution protection platform determines the number of resolutions of each resolution server according to the resolution capability of each resolution server, and determines the number of resolutions corresponding to each resolution server and the resolution information corresponding to the node as the next hop resolution information. Further, the local domain name server can query the domain name received multiple times according to the number of resolutions corresponding to each resolution server and the resolution information corresponding to the node. Exemplarily, if the next hop resolution information includes resolution server 1, resolution server 2 and resolution server 2, wherein the number of resolutions corresponding to resolution server 1 is 300, the number of resolutions corresponding to resolution server 2 is 200, and the number of resolutions corresponding to resolution server 1 is 100, and the local domain name server receives 700 domain names within a preset time period, then the first 300 domain names are queried from resolution server 1, the 301st to 500th domain names are queried from resolution server 2, and the 501st to 600th domain names are queried from resolution server 3. If the domain names exceeding the 601st to 700th domain names of the resolution node are returned to the client by the local domain name server, the query error information is returned.

[0094] In the above application embodiment, the number of resolutions corresponding to each resolution server is determined according to the resolution capabilities of each resolution server, so that the local domain name server can distribute multiple domain name queries received to multiple resolution servers according to the number of resolutions corresponding to each resolution server, thereby balancing the load of each resolution server.

[0095] In one embodiment, as shown in FIG5 , determining the resolution capability of each resolution server may include:

[0096] S401, determining the resolution capability of each resolution server.

[0097] In an embodiment of the present application, as an optional implementation, a resolution capacity table of resolution servers may be pre-stored in the domain name resolution protection platform, so that the resolution capacity of each resolution server may be determined based on the resolution capacity table, and the resolution capacity may be represented by a numerical value.

[0098] As another optional implementation, the nodes in the preset resolution link diagram correspond to multiple resolution servers and the historical resolution times of the resolution servers. The domain name resolution protection platform can determine the historical resolution times of each resolution server based on the preset resolution link diagram, and thus determine the resolution capability of each resolution server based on the historical resolution times.

[0099] S402: Determine the resolution quantity corresponding to each resolution server according to the resolution capability of each resolution server.

[0100] In the embodiment of the present application, when the resolution capability is expressed by a numerical value, the resolution quantity corresponding to each resolution server can be determined according to the resolution capability of each resolution server, the preset quantity and the preset first ratio. Optionally, the preset quantity can be the number of times the local domain name server receives the domain name within a preset time period. Exemplarily, if the next resolution information includes resolution server 1, resolution server 2 and resolution server 3, wherein the resolution capability of resolution server 1 is 0.25, the resolution capability of resolution server 2 is 0.5, and the resolution capability of resolution server 3 is 0.25, when the preset quantity is 1000, the initial resolution quantity corresponding to resolution server 1 is 250, the initial resolution quantity corresponding to resolution server 2 is 500, and the initial resolution quantity corresponding to resolution server 3 is 250. Further, the resolution quantity can be adjusted according to the preset ratio based on the initial resolution quantity determined according to the ratio value of the resolution capability of each resolution server and the preset quantity. Exemplarily, if the preset first ratio is 150%, the product of the initial resolution quantity and 150% is used as the resolution quantity corresponding to the resolution server.

[0101] In the above application embodiment, the number of resolutions is determined according to the resolution capability of each resolution server, so that the resolution number is more closely matched with the resolution server. The local domain name server resolves the domain name according to the number of resolutions to avoid high-load resolution on the resolution server.

[0102] In one embodiment, an implementation of the above S401 is provided, as shown in FIG6 , the above “determining the resolution capability of each resolution server” may include:

[0103] S501, determining the historical resolution times of each resolution server according to a preset link flow table.

[0104] In an embodiment of the present application, the domain name resolution protection platform receives the historical domain name resolution data corresponding to the target domain name sent by the local domain name server, and constructs a link flow table according to the resolution times of the resolution server of each resolution node in the historical domain name resolution data. Thus, when generating the next hop resolution information, the historical resolution times of the resolution server can be determined according to the link flow table. Exemplarily, the link flow table is shown in Table 1.

[0105] Table 1

[0106]

[0107] S502: Determine the resolution capability of each resolution server according to the historical resolution times of each resolution server.

[0108] In the embodiment of the present application, the resolution capability of each resolution server can be determined according to the ratio of the historical resolution times of each resolution server. For example, if the historical resolution times of resolution server 1 is 250, the historical resolution times of resolution server 2 is 500, and the historical resolution times of resolution server 3 is 250, then the resolution capability of resolution server 1 is 0.25, the resolution capability of resolution server 2 is 0.5, and the resolution capability of resolution server 3 is 0.25.

[0109] In the above application embodiment, the historical resolution times of each resolution server are determined according to the preset link flow table, and then the resolution capability of each resolution server is determined according to the historical resolution times, thereby improving the accuracy of the resolution capability of each resolution server.

[0110] In one embodiment, as shown in FIG. 7 , the domain name resolution method may further include:

[0111] S203, receiving historical domain name resolution data corresponding to the target domain name sent by the local domain name server.

[0112] In the embodiment of the present application, when the domain name resolution system is working properly, the local domain name server initiates a target domain name query to the domain name authority server, obtains the corresponding resolution data of the second-hop server, and then initiates a target domain name query to the second-hop server until the IP address of the target domain name is obtained. The local domain name server sends the data of each hop when the domain name resolution system is working properly as historical domain name resolution data to the domain name resolution protection platform.

[0113] Optionally, the local domain name server may send historical domain name resolution data corresponding to each hop to the domain name resolution protection platform after each hop; or, the local domain name server may send historical domain name resolution data to the domain name resolution protection platform after each obtaining the IP address of the target domain name.

[0114] S204, constructing multiple resolution link data tables corresponding to the target domain name based on historical domain name resolution data; each resolution link data table includes resolution information of each resolution server on the corresponding link.

[0115] In the embodiment of the present application, the domain name resolution protection platform extracts the data of the resolution link corresponding to each query in the historical domain name resolution data, and for each query, constructs a resolution link data table corresponding to the target domain name. Exemplarily, the resolution link data table can be shown in Table 2, where the last hop of the resolution link is a required item.

[0116] Table 2

[0117]

[0118] S205: Generate a preset parsing link graph according to the multiple parsing link data tables.

[0119] In an embodiment of the present application, data in multiple resolution link data tables are extracted and merged to generate a preset resolution link graph for the target domain name. Exemplarily, as shown in FIG. 3 , the preset resolution link graph can be a tree graph, in which each node corresponds to a resolution server and the historical resolution times of the resolution server.

[0120] In the above-mentioned application embodiment, a preset resolution link graph is generated based on historical domain name resolution data. The preset resolution link graph constructed based on known data has higher accuracy, thereby improving the accuracy of the local domain name server's query based on the next-hop resolution information when a resolution node with service termination is detected in the domain name resolution system.

[0121] In one embodiment, as shown in FIG8 , the domain name resolution method may further include:

[0122] S206, detecting the status of each resolution server in the preset resolution link diagram.

[0123] In an embodiment of the present application, the number of resolutions of each resolution server within a preset time period is determined. If the number of resolutions is greater than a preset trustworthy range, it is determined that the state of the resolution server is in an abnormal state; if the number of resolutions is not greater than the preset trustworthy range, it is determined that the state of the resolution server is in a normal state.

[0124] Optionally, the trusted range of each resolution server can be determined based on the number of resolutions corresponding to each resolution server and a preset second ratio. For example, the product of the number of resolutions corresponding to each resolution server and the preset second ratio is used as the upper limit of the trusted range, and 0 is used as the lower limit of the trusted range.

[0125] S207, when it is detected that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link graph to obtain an updated preset resolution link graph.

[0126] In an embodiment of the present application, if it is detected that the state of the resolution server is in an abnormal state, it indicates that the current security of the resolution server is relatively high, and the resolution server is removed from the preset resolution link graph to obtain an updated preset resolution link graph.

[0127] Optionally, when it is detected next time that the status of the removed resolution server is in a normal state, the resolution server may be added back to the preset resolution link graph.

[0128] Based on the above steps, the above “generating next hop resolution information according to the preset resolution link graph” includes:

[0129] S208: Generate next hop resolution information according to the updated preset resolution link graph.

[0130] In an embodiment of the present application, when a service-terminating resolution node is detected in the domain name resolution system, next-hop resolution information is generated according to the service-terminating resolution node and the updated preset resolution link graph. As an optional implementation, all link information corresponding to the resolution node can be determined from the updated preset resolution link graph according to the service-terminating resolution node, and all link information corresponding to the resolution node can be encapsulated in the form of a file as the next-hop resolution information.

[0131] In the above application embodiment, the preset resolution link diagram is updated according to the status of each resolution server, avoiding the use of unsafe resolution servers to resolve the domain name, thereby improving the security of resolving the domain name.

[0132] In one embodiment, as shown in FIG. 9 , a domain name resolution method is provided, which is described by taking the method applied to the local domain name server in FIG. 1 as an example, and includes the following steps:

[0133] S601, receiving the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when it detects that there is a resolution node with service termination in the domain name resolution system.

[0134] In an embodiment of the present application, the resolution nodes in the domain name resolution system include domain name authority nodes, CDB traffic scheduling nodes, etc. Each node includes at least one server. The domain name resolution protection platform pre-establishes and stores a resolution link graph. When the domain name resolution protection platform detects that there is a resolution node with terminated service in the domain name resolution system, it generates next-hop resolution information based on the resolution node with terminated service and the preset resolution link graph, and sends the next-hop information to the local domain name server.

[0135] S602: When receiving the domain name, query the domain name according to the next hop resolution information.

[0136] In an embodiment of the present application, when the local domain name server receives a domain name, it queries the server corresponding to the next hop based on the next hop resolution information, so that the server corresponding to the next hop resolves the domain name and sends the next hop resolution information to the local domain name server.

[0137] In the above domain name resolution method, when it is detected that there is a resolution node with service termination in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram, and the next hop resolution information is sent to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name. The domain name resolution protection platform pre-stores the resolution link diagram, so that when it is detected that there is a resolution node with service termination in the domain name resolution system, the next hop resolution information can be determined through the resolution link diagram, so that when the local domain name server cannot communicate with the resolution node with service termination, it can communicate with the next hop resolution node according to the next hop resolution information and query the received domain name.

[0138] In one embodiment, as shown in FIG10 , the domain name resolution method may further include:

[0139] S603, sending historical domain name resolution data corresponding to the target domain name to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

[0140] In the embodiment of the present application, when the domain name resolution system is working normally, the local domain name server initiates a target domain name query to the domain name authority server, obtains the corresponding resolution data of the second-hop server, and then initiates a target domain name query to the second-hop server until the IP address of the target domain name is obtained. The local domain name server sends the data of each hop when the domain name resolution system is working normally as historical domain name resolution data to the domain name resolution protection platform. The domain name resolution protection platform extracts the data of the resolution link corresponding to each query in the historical domain name resolution data, and constructs a resolution link data table corresponding to the target domain name for each query.

[0141] In the above application embodiment, the historical domain name resolution data is sent to the domain name resolution protection platform, so that the domain name resolution protection platform generates a preset resolution link graph based on the historical domain name resolution data. The preset resolution link graph constructed based on known data has higher accuracy.

[0142] In one embodiment, a complete domain name resolution method is also provided, as shown in FIG11 , including:

[0143] S1, the domain name resolution protection platform receives the historical domain name resolution data corresponding to the target domain name sent by the local domain name server.

[0144] S2, the domain name resolution protection platform constructs multiple resolution link data tables corresponding to the target domain name based on historical domain name resolution data; each resolution link data table includes resolution information of each resolution server on the corresponding link.

[0145] S3, the domain name resolution protection platform generates a preset resolution link diagram based on multiple resolution link data tables.

[0146] S4, the domain name resolution protection platform detects the status of each resolution server in the preset resolution link diagram.

[0147] S5, when the domain name resolution protection platform detects that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link map to obtain an updated preset resolution link map.

[0148] S6, when the domain name resolution protection platform detects that there is a resolution node whose service has been terminated in the domain name resolution system, it determines the child nodes of the resolution node whose service has been terminated in the updated preset resolution link diagram.

[0149] S7, the domain name resolution protection platform determines the historical resolution times of each resolution server according to the preset link flow table.

[0150] S8, the domain name resolution protection platform determines the resolution capability of each resolution server according to the historical resolution times of each resolution server, and determines the resolution quantity corresponding to each resolution server according to the resolution capability of each resolution server.

[0151] S9, the domain name resolution protection platform determines the resolution quantity corresponding to each resolution server and the resolution information corresponding to the node as the next hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each resolution server.

[0152] S10, the domain name resolution protection platform sends the next hop resolution information to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0153] S11, when the local domain name server receives the domain name, it queries the domain name according to the next hop resolution information.

[0154] In the above domain name resolution method, when it is detected that there is a resolution node with service termination in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram, and the next hop resolution information is sent to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name. The domain name resolution protection platform pre-stores the resolution link diagram, so that when it is detected that there is a resolution node with service termination in the domain name resolution system, the next hop resolution information can be determined through the resolution link diagram, so that when the local domain name server cannot communicate with the resolution node with service termination, it can communicate with the next hop resolution node according to the next hop resolution information and query the received domain name.

[0155] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0156] Based on the same inventive concept, the embodiment of the present application also provides a domain name resolution device for implementing the domain name resolution method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more domain name resolution device embodiments provided below can refer to the limitations on the domain name resolution method above, and will not be repeated here.

[0157] In one embodiment, as shown in FIG12 , a domain name resolution device is provided, including: a first generating module 10 and a first sending module 11, wherein:

[0158] The first generating module 10 is used to generate next hop resolution information according to a preset resolution link graph when detecting that there is a resolution node whose service is terminated in the domain name resolution system.

[0159] The first sending module 11 is used to send next hop resolution information to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0160] In one embodiment, the generation module 10 includes: a first determination unit and a second determination unit, wherein:

[0161] The first determining unit is used to determine a child node of a resolution node whose service is terminated in a preset resolution link graph.

[0162] The second determining unit is specifically configured to determine the resolution information corresponding to the child node as the next hop resolution information.

[0163] In one embodiment, the subnode includes multiple resolution servers, and the above-mentioned second determination unit is specifically used to determine the resolution quantity corresponding to each resolution server and the resolution information corresponding to the node as the next hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each resolution server.

[0164] In one embodiment, the second determining unit is specifically configured to determine the resolution capability of each resolution server; and determine the resolution quantity corresponding to each resolution server according to the resolution capability of each resolution server.

[0165] In one embodiment, the second determining unit is specifically configured to determine the historical resolution times of each resolution server according to a preset link flow table; and determine the resolution capability of each resolution server according to the historical resolution times of each resolution server.

[0166] In one embodiment, the domain name resolution device further includes: a second receiving module, a building module, and a second generating module, wherein:

[0167] The second receiving module is used to receive historical domain name resolution data corresponding to the target domain name sent by the local domain name server.

[0168] The construction module is used to construct multiple resolution link data tables corresponding to the target domain name based on historical domain name resolution data; each resolution link data table includes resolution information of each resolution server on the corresponding link.

[0169] The second generating module is used to generate a preset parsing link graph according to a plurality of parsing link data tables.

[0170] In one embodiment, the above-mentioned domain name resolution device further includes: a detection module and an update module, wherein:

[0171] The detection module is used to detect the status of each resolution server in the preset resolution link diagram.

[0172] The updating module is used to remove the abnormal state of the resolution server from the preset resolution link diagram when detecting that the state of the resolution server is in an abnormal state, so as to obtain an updated preset resolution link diagram.

[0173] The first generating module is used to generate next hop resolution information according to the updated preset resolution link graph.

[0174] In one embodiment, as shown in FIG13 , a domain name resolution device is provided, including: a first receiving module 12 and a query module 13, wherein:

[0175] The first receiving module 12 is used to receive the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when it detects that there is a resolution node with service termination in the domain name resolution system.

[0176] The query module 13 is used to query the domain name according to the next hop resolution information when receiving the domain name.

[0177] In one embodiment, the above-mentioned domain name resolution module also includes: a second sending module, used to send historical domain name resolution data corresponding to the target domain name to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

[0178] Each module in the above-mentioned domain name resolution device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0179] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG14. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store domain name resolution data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a domain name resolution method is implemented.

[0180] Those skilled in the art will understand that the structure shown in FIG. 14 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0181] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0182] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0183] The next hop resolution information is sent to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0184] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0185] Determine the child nodes of the resolution node whose service is terminated in the preset resolution link graph;

[0186] The resolution information corresponding to the child node is determined as the next hop resolution information.

[0187] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0188] The resolution quantity corresponding to each resolution server and the resolution information corresponding to the node are determined as the next hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each resolution server.

[0189] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0190] Determine the resolution capability of each resolution server;

[0191] The number of resolutions corresponding to each resolution server is determined according to the resolution capability of each resolution server.

[0192] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0193] Determine the historical resolution times of each resolution server according to the preset link flow table;

[0194] The resolution capability of each resolution server is determined based on the historical resolution times of each resolution server.

[0195] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0196] Receive historical domain name resolution data corresponding to the target domain name sent by the local domain name server;

[0197] Based on the historical domain name resolution data, multiple resolution link data tables corresponding to the target domain name are constructed; each resolution link data table includes the resolution information of each resolution server on the corresponding link;

[0198] A preset parsing link graph is generated based on multiple parsing link data tables.

[0199] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0200] Detect the status of each resolution server in the preset resolution link diagram;

[0201] When it is detected that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link graph to obtain an updated preset resolution link graph;

[0202] Generate next hop resolution information based on the preset resolution link diagram, including:

[0203] Generate next hop resolution information based on the updated preset resolution link graph.

[0204] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0205] Receiving the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when the domain name resolution protection platform detects that there is a resolution node with service termination in the domain name resolution system;

[0206] When a domain name is received, the domain name is queried based on the next hop resolution information.

[0207] In one embodiment, when the processor executes the computer program, the following steps are also implemented:

[0208] The historical domain name resolution data corresponding to the target domain name is sent to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

[0209] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0210] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0211] The next hop resolution information is sent to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0212] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0213] Determine the child nodes of the resolution node whose service is terminated in the preset resolution link graph;

[0214] The resolution information corresponding to the child node is determined as the next hop resolution information.

[0215] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0216] The resolution quantity corresponding to each resolution server and the resolution information corresponding to the node are determined as the next hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each resolution server.

[0217] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0218] Determine the resolution capability of each resolution server;

[0219] The number of resolutions corresponding to each resolution server is determined according to the resolution capability of each resolution server.

[0220] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0221] Determine the historical resolution times of each resolution server according to the preset link flow table;

[0222] The resolution capability of each resolution server is determined based on the historical resolution times of each resolution server.

[0223] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0224] Receive historical domain name resolution data corresponding to the target domain name sent by the local domain name server;

[0225] Based on the historical domain name resolution data, multiple resolution link data tables corresponding to the target domain name are constructed; each resolution link data table includes the resolution information of each resolution server on the corresponding link;

[0226] A preset parsing link graph is generated based on multiple parsing link data tables.

[0227] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0228] Detect the status of each resolution server in the preset resolution link diagram;

[0229] When it is detected that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link graph to obtain an updated preset resolution link graph;

[0230] Generate next hop resolution information based on the preset resolution link diagram, including:

[0231] Generate next hop resolution information based on the updated preset resolution link graph.

[0232] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0233] Receiving the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when the domain name resolution protection platform detects that there is a resolution node with service termination in the domain name resolution system;

[0234] When a domain name is received, the domain name is queried based on the next hop resolution information.

[0235] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0236] The historical domain name resolution data corresponding to the target domain name is sent to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

[0237] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0238] When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram;

[0239] The next hop resolution information is sent to the local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

[0240] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0241] Determine the child nodes of the resolution node whose service is terminated in the preset resolution link graph;

[0242] The resolution information corresponding to the child node is determined as the next hop resolution information.

[0243] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0244] The resolution quantity corresponding to each resolution server and the resolution information corresponding to the node are determined as the next hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each resolution server.

[0245] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0246] Determine the resolution capability of each resolution server;

[0247] The number of resolutions corresponding to each resolution server is determined according to the resolution capability of each resolution server.

[0248] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0249] Determine the historical resolution times of each resolution server according to the preset link flow table;

[0250] The resolution capability of each resolution server is determined based on the historical resolution times of each resolution server.

[0251] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0252] Receive historical domain name resolution data corresponding to the target domain name sent by the local domain name server;

[0253] Based on the historical domain name resolution data, multiple resolution link data tables corresponding to the target domain name are constructed; each resolution link data table includes the resolution information of each resolution server on the corresponding link;

[0254] A preset parsing link graph is generated based on multiple parsing link data tables.

[0255] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0256] Detect the status of each resolution server in the preset resolution link diagram;

[0257] When it is detected that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link graph to obtain an updated preset resolution link graph;

[0258] Generate next hop resolution information based on the preset resolution link diagram, including:

[0259] Generate next hop resolution information based on the updated preset resolution link graph.

[0260] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0261] Receiving the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when the domain name resolution protection platform detects that there is a resolution node with service termination in the domain name resolution system;

[0262] When a domain name is received, the domain name is queried based on the next hop resolution information.

[0263] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0264] The historical domain name resolution data corresponding to the target domain name is sent to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

[0265] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0266] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0267] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A domain name resolution method, characterized in that: The method is applied to a domain name resolution protection platform, and the method includes: When a resolution node with service termination is detected in the domain name resolution system, next hop resolution information is generated according to a preset resolution link diagram; The next hop resolution information is sent to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

2. The method according to claim 1, characterized in that The generating the next hop resolution information according to the preset resolution link graph includes: Determine a child node of the resolution node where the service is terminated in the preset resolution link graph; The resolution information corresponding to the child node is determined as the next hop resolution information.

3. The method according to claim 2, characterized in that The child node includes a plurality of resolution servers, and determining the resolution information corresponding to the child node as the next hop resolution information includes: The resolution quantity corresponding to each of the resolution servers and the resolution information corresponding to the node are determined as the next-hop resolution information; the resolution quantity is determined by the domain name resolution protection platform according to the resolution capability of each of the resolution servers.

4. The method according to claim 3, characterized in that The method for determining the number of resolutions corresponding to each resolution server includes: Determining the resolution capability of each of the resolution servers; The number of resolutions corresponding to each resolution server is determined according to the resolution capability of each resolution server.

5. The method according to claim 4, characterized in that The determining the resolution capability of each resolution server includes: Determine the historical resolution times of each resolution server according to a preset link flow table; The resolution capability of each resolution server is determined according to the historical resolution times of each resolution server.

6. The method according to any one of claims 1 to 5, characterized in that: The method for obtaining the preset analysis link graph includes: Receive historical domain name resolution data corresponding to the target domain name sent by the local domain name server; According to the historical domain name resolution data, a plurality of resolution link data tables corresponding to the target domain name are constructed; each of the resolution link data tables includes resolution information of each resolution server on the corresponding link; The preset parsing link graph is generated according to the multiple parsing link data tables.

7. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Detecting the status of each resolution server in the preset resolution link diagram; When it is detected that the state of the resolution server is in an abnormal state, the resolution server in the abnormal state is removed from the preset resolution link graph to obtain an updated preset resolution link graph; The generating the next hop resolution information according to the preset resolution link graph includes: Next hop resolution information is generated according to the updated preset resolution link graph.

8. A domain name resolution method, characterized in that: The method is applied to a local domain name server, and the method comprises: Receiving next-hop resolution information sent by the domain name resolution protection platform; the next-hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system; When the domain name is received, the domain name is queried according to the next hop resolution information.

9. The method according to claim 8, characterized in that The method further comprises: The historical domain name resolution data corresponding to the target domain name is sent to the domain name resolution protection platform; the historical domain name resolution data is used to instruct the domain name resolution protection platform to construct multiple resolution link data tables corresponding to the target domain name.

10. A domain name resolution device, characterized in that: The device comprises: A first generating module is used to generate next hop resolution information according to a preset resolution link diagram when detecting that there is a resolution node whose service is terminated in the domain name resolution system; The first sending module is used to send the next hop resolution information to a local domain name server; the next hop resolution information is used to instruct the local domain name server to query the received domain name.

11. A domain name resolution device, characterized in that: The device comprises: The first receiving module is used to receive the next hop resolution information sent by the domain name resolution protection platform; the next hop resolution information is generated by the domain name resolution protection platform according to a preset resolution link diagram when detecting that there is a resolution node with service termination in the domain name resolution system; The query module is used to query the domain name according to the next hop resolution information when receiving the domain name.

12. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 or 8 to 9 are implemented.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 or 8 to 9 are implemented.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 or 8 to 9 are implemented.

Images