Network disaster recovery method, device and system

By connecting multiple domain name service platforms to the domain name system and using the first domain name service platform to automatically resolve and allocate target domain name service platforms, the problems of low efficiency and inconvenient manual switching in the existing disaster recovery system are solved, and efficient disaster recovery processing and automatic equipment switching are achieved.

CN118921350APending Publication Date: 2024-11-08ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310518335.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-08
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing disaster recovery systems have low efficiency and require manual switching of equipment, which is inconvenient.

Method used

By connecting multiple domain name service platforms to the domain name system, the first domain name service platform is used to receive domain name service requests, resolve them, determine the target domain name service platform, and automatically allocate network service addresses. This reduces the workload of the domain name system, improves processing efficiency, and automatically switches in case of abnormalities, avoiding manual intervention.

Benefits of technology

It improves the processing efficiency of the disaster recovery system, reduces the workload of the domain name system, avoids manual equipment switching, and ensures service continuity and high availability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921350A_ABST
    Figure CN118921350A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a network disaster recovery method, device and system. The method comprises the following steps: receiving a domain name service request sent by a domain name system from a client; the domain name service request carries a domain name corresponding to the client; the domain name system accesses a plurality of domain name service platforms; the first domain name service platform is any one of the plurality of domain name service platforms; based on the domain name service request, analyzing a domain name corresponding to the client to obtain a domain name analysis result corresponding to the client; determining a target domain name service platform for performing domain name service for the client from the plurality of domain name service platforms according to the domain name resolution result; sending a network service address corresponding to the target domain name service platform to the client; and the client is used for connecting the target domain name service platform through the network service address corresponding to the target domain name service platform. The disaster recovery efficiency of the disaster recovery system can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of network disaster recovery, and in particular to a network disaster recovery method, device and system. Background Art

[0002] In the 5G era, with the development of network technology, communication network management systems and control systems are gradually integrated. Coupled with the growth of intelligent operation and maintenance and big data analysis needs, there is a trend of full integration of management and control. For example, IPTV (interactive network television) is a new technology that uses broadband networks to integrate Internet, multimedia, communication and other technologies to provide home users with a variety of interactive services including digital TV. It can adapt well to the trend of rapid network development today and make full and effective use of network resources. However, with the rapid growth of various types of business, management, control, and analysis information generated by the network, the high availability of the system and the disaster recovery of data are becoming increasingly urgent.

[0003] In the related art, the addresses of the primary and backup devices are usually pre-written in the disaster recovery system, and when the primary device service is abnormal, the user manually switches to the backup device, which is very inconvenient and has low disaster recovery efficiency. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a network disaster recovery method, device and system to solve the problem of low disaster recovery efficiency of existing disaster recovery systems.

[0005] To solve the above technical problems, the embodiments of the present application are implemented as follows:

[0006] On the one hand, an embodiment of the present application provides a network disaster recovery method, which is applied to a first domain name service platform, and the method includes: receiving a domain name service request from a client sent by a domain name system, the domain name service request carries the domain name corresponding to the client, the domain name system is connected to multiple domain name service platforms, and the first domain name service platform is any one of the multiple domain name service platforms. Based on the domain name service request, the domain name corresponding to the client is resolved to obtain a domain name resolution result corresponding to the client, and according to the domain name resolution result, a target domain name service platform that provides domain name service for the client is determined from the multiple domain name service platforms. The network service address corresponding to the target domain name service platform is sent to the client, and the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

[0007] On the other hand, an embodiment of the present application provides a network disaster recovery device, which is applied to a first domain name service platform, and the device includes: a receiving module, which is used to receive a domain name service request from a client sent by a domain name system, the domain name service request carries the domain name corresponding to the client, the domain name system is connected to multiple domain name service platforms, and the first domain name service platform is any one of the multiple domain name service platforms. A resolution module, which is used to resolve the domain name corresponding to the client based on the domain name service request, and obtain a domain name resolution result corresponding to the client. A first determination module, which is used to determine, from the multiple domain name service platforms, a target domain name service platform that provides domain name service for the client based on the domain name resolution result. A first sending module, which is used to send the network service address corresponding to the target domain name service platform to the client, and the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

[0008] On the other hand, an embodiment of the present application provides a network disaster recovery system, the system comprising a domain name system and multiple domain name service platforms connected to the domain name system. The domain name system is used to receive a domain name service request from a client, the domain name service request carries the domain name corresponding to the client. A first domain name service platform is used to resolve the domain name corresponding to the client according to the domain name service request sent by the domain name system, obtain a domain name resolution result corresponding to the client, determine a target domain name service platform for providing domain name service for the client from the multiple domain name service platforms according to the domain name resolution result, send the network service address corresponding to the target domain name service platform to the client, the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform, the first domain name service platform is any one of the multiple domain name service platforms.

[0009] On the other hand, an embodiment of the present application provides an electronic device, including a processor and a memory electrically connected to the processor, the memory storing a computer program, and the processor being used to call and execute the computer program from the memory to implement the above-mentioned network disaster recovery method.

[0010] On the other hand, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program can be executed by a processor to implement the above-mentioned network disaster recovery method.

[0011] According to the technical solution of the embodiment of the present application, in a domain name system connected to multiple domain name service platforms, the first domain name service platform (any one of the multiple domain name service platforms) receives a domain name service request from a client sent by the domain name system, the domain name service request carries the domain name corresponding to the client, and resolves the domain name corresponding to the client based on the domain name service request to obtain a domain name resolution result corresponding to the client. Then, according to the domain name resolution result, a target domain name service platform for providing domain name service to the client is determined from the multiple domain name service platforms. Then, the network service address corresponding to the target domain name service platform is sent to the client, and the client connects to the target domain name service platform through the network service address corresponding to the target domain name service platform. Since the first domain name service platform can be any domain name service platform in the domain name system, any domain name service platform in the domain name service platform can determine the target domain name service platform for the received domain name service request without the need for the domain name system to allocate a domain name service platform for the domain name service request, thereby reducing the workload of the domain name system in processing domain name service requests and improving the processing efficiency of domain name service requests. Furthermore, since the technical solution distributes the process of allocating the target domain name service platform to the first domain name service platform, even when the status of one (or some) domain name service platform is abnormal, the first domain name service platform can still allocate the corresponding target domain name service platform for the domain name service request without the need for the domain name system to handle disaster recovery, and there is no need for manual switching of equipment, thereby improving disaster recovery efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0013] Figure 1 This is a schematic diagram of an application scenario of a network disaster recovery system according to an embodiment of the present application;

[0014] Figure 2 is a schematic flow chart of a network disaster recovery method according to an embodiment of the present application;

[0015] Figure 3 This is a schematic heartbeat interaction diagram of each domain name service platform in a network disaster recovery system according to an embodiment of the present application;

[0016] Figure 4 is a schematic heartbeat interaction diagram within each domain name service platform according to an embodiment of the present application;

[0017] Figure 5 is a schematic flow chart of a network disaster recovery method according to another embodiment of the present application;

[0018] Figure 6 is a schematic block diagram of a network disaster recovery device according to an embodiment of the present application;

[0019] Figure 7 is a schematic block diagram of a network disaster recovery system according to an embodiment of the present application;

[0020] Figure 8 The present invention is a schematic diagram of the hardware structure of a network disaster recovery device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] The embodiments of the present application provide a network disaster recovery method, device and system to solve the problem of low disaster recovery efficiency of existing disaster recovery systems.

[0022] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0023] The network disaster recovery method provided in the embodiment of the present application can be executed by an electronic device, or by software installed in the electronic device. Specifically, the electronic device can be a terminal device or a server device. Among them, the terminal device can include a smart phone, a laptop computer, a smart wearable device, a vehicle terminal, etc., and the server device can include an independent physical server, a server cluster composed of multiple servers, or a cloud server capable of cloud computing.

[0024] Figure 1 FIG. 1 is a schematic diagram of an application scenario of a network disaster recovery system according to an embodiment of the present application. Figure 1 As shown, the application scenario of the network disaster recovery system involves the network disaster recovery system and the client, wherein the network disaster recovery system includes a domain name system and multiple domain name service platforms connected to the domain name system, and the domain name system is used to receive domain name service requests from the client and forward the domain name service requests to the domain name service platform. The domain name service platform is used to receive domain name service requests from the domain name system, and resolve the domain name corresponding to the client based on the domain name service request to obtain the domain name resolution result corresponding to the client. Then, according to the domain name resolution result, the target domain name service platform for providing domain name service for the client is determined from multiple domain name service platforms, and the network service address of the target domain name service platform is sent to the client through the domain name system.

[0025] Optionally, in actual applications, each domain name service platform includes a local domain name system (LocalDNS) module, a proxy cancellation server (NGINX) module, and an interactive personal TV (IPTV) system module. Among them, the client sends a domain name service request to the domain name system, and the domain name system forwards the domain name service request to the first domain name service platform (any one of the multiple domain name service platforms or a designated domain name service platform), and the first domain name service platform can receive the domain name service request and determine the target domain name service platform. When determining the target domain name service platform, the LocalDNS module is used to resolve the domain name of the client, and the NGINX module is used to monitor the status of the IPTV system module of each domain name service platform, and promptly report it to the LocalDNS modules of the first domain name service platform and other domain name service platforms, wherein the IPTV system module includes the service status information of the domain name service platform.

[0026] Figure 2 is a schematic flow chart of a network disaster recovery method according to an embodiment of the present application, the method is applied to a first domain name service platform, the first domain name service platform can be Figure 1 Any one of the multiple domain name service platforms shown in . Figure 2 As shown, the network disaster recovery method includes the following steps:

[0027] S202, receiving a domain name service request from a client sent by a domain name system, where the domain name service request carries a domain name corresponding to the client.

[0028] Among them, the domain name, also known as the network domain, is the name of a computer or computer group on the Internet composed of a string of names separated by dots. It is used to locate the computer during data transmission. The domain name system is used to map domain names and Internet Protocol (IP) addresses to each other, making it easier for people to access the Internet without having to remember the IP address string that can be directly read by machines.

[0029] S204, based on the domain name service request, resolve the domain name corresponding to the client to obtain a domain name resolution result corresponding to the client.

[0030] Among them, domain name resolution is a service that uses the client's domain name to find the client's corresponding IP address so as to more conveniently access the client to be accessed.

[0031] Optionally, the domain name resolution result is an IP address corresponding to the client. The first domain name service platform resolves the received domain name corresponding to the client to obtain a domain name resolution result corresponding to the client, and the domain name resolution result includes the IP address of the client.

[0032] S206: According to the domain name resolution result, determine a target domain name service platform for providing domain name service for the client from multiple domain name service platforms.

[0033] S208, sending the network service address corresponding to the target domain name service platform to the client.

[0034] The client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

[0035] In this embodiment, the platform information of the first domain name service platform may be pre-configured in the domain name system. When the domain name system receives a domain name service request, it forwards the domain name service request to the first domain name service platform according to the configured platform information.

[0036] Optionally, the platform information of multiple domain name service platforms and the priority information between the multiple domain name service platforms can be pre-configured in the domain name system. The priority information is used to indicate which domain name service platform the domain name system will preferentially forward the domain name service request to. For example, the platform information of the first domain name service platform and the second domain name service platform are configured in the domain name system, and the priority of the first domain name service platform is higher than that of the second domain name service platform. Then, when the domain name system receives a domain name service request, it can preferentially forward the domain name service request to the first domain name service platform. If the forwarding fails, the domain name service request will be forwarded to the second domain name service platform. Among them, the forwarding failure situation may include any of the following: the service status of the first domain name service platform is abnormal, resulting in the inability to receive the domain name service request; no feedback information from the first domain name service platform for the domain name service request is received within a preset time period.

[0037] According to the technical solution of the embodiment of the present application, in a domain name system connected to multiple domain name service platforms, the first domain name service platform (any one of the multiple domain name service platforms) receives a domain name service request from a client sent by the domain name system, the domain name service request carries the domain name corresponding to the client, and resolves the domain name corresponding to the client based on the domain name service request to obtain a domain name resolution result corresponding to the client. Then, according to the domain name resolution result, a target domain name service platform for providing domain name service to the client is determined from the multiple domain name service platforms. Then, the network service address corresponding to the target domain name service platform is sent to the client, and the client connects to the target domain name service platform through the network service address corresponding to the target domain name service platform. Since the first domain name service platform can be any domain name service platform in the domain name system, any domain name service platform in the domain name service platform can determine the target domain name service platform for the received domain name service request without the need for the domain name system to allocate a domain name service platform for the domain name service request, thereby reducing the workload of the domain name system in processing domain name service requests and improving the processing efficiency of domain name service requests. Furthermore, since the technical solution distributes the process of allocating the target domain name service platform to the first domain name service platform, even when the status of one (or some) domain name service platform is abnormal, the first domain name service platform can still allocate the corresponding target domain name service platform for the domain name service request without the need for the domain name system to handle disaster recovery, and there is no need for manual switching of equipment, thereby improving disaster recovery efficiency.

[0038] In one embodiment, the domain name resolution result includes an IP address. When determining the target domain name service platform according to the domain name resolution result (i.e., S206), the following steps may be performed: according to a preset first correspondence between an IP address segment and a domain name service platform, a domain name service platform corresponding to the IP address corresponding to the client is determined as the target domain name service platform.

[0039] In this embodiment, the first domain name service platform resolves the domain name in the domain name service request to obtain the IP address corresponding to the client, and based on the IP address corresponding to the client, the IP address segment to which the IP address corresponding to the client belongs can be determined. Furthermore, based on the first corresponding relationship between the IP address segment and the domain name service platform, the domain name service platform corresponding to the IP address segment to which the IP address corresponding to the client belongs can be determined, and the domain name service platform is determined as the target domain name service platform.

[0040] In one embodiment, when determining the target domain name service platform according to the first correspondence between the preset IP address segment and the domain name service platform, the following steps A1-A2 may be performed:

[0041] Step A1, according to a first correspondence between an IP address segment and a domain name service platform, determining a plurality of candidate domain name service platforms corresponding to the IP address corresponding to the client.

[0042] Among them, each IP address segment may correspond to one or more domain name service platforms. The first domain name service platform resolves the acquired domain name of the client, obtains the IP address corresponding to the client, and determines the IP address segment to which the IP address corresponding to the client belongs. Then, based on the first corresponding relationship and the IP address segment to which the IP address corresponding to the client belongs, the candidate domain name service platform corresponding to the IP address corresponding to the client is determined. If the determined candidate domain name service platform includes only one, then the candidate domain name service platform is the target domain name service platform. If the determined candidate domain name service platform includes multiple, it is necessary to select one candidate domain name service platform from the multiple candidate domain name service platforms as the target domain name service platform. For example, the IP address segment to which the IP address corresponding to the client belongs corresponds to the first domain name service platform, the second domain name service platform and the third domain name service platform, then the first domain name service platform, the second domain name service platform and the third domain name service platform are the candidate domain name service platforms corresponding to the IP address corresponding to the client.

[0043] Step A2: According to the service status information corresponding to each domain name service platform pre-stored in the first domain name service platform, a domain name service platform with normal service status is selected from multiple candidate domain name service platforms as the target domain name service platform.

[0044] The service status information may include: normal service status or abnormal service status. The first domain name service platform may pre-store service status information corresponding to each domain name service platform. Optionally, the first domain name service platform and other domain name service platforms send and receive their respective service status information through the interaction of heartbeat messages. For example, when the second domain name service platform sends a heartbeat message to the first domain name service platform, the service status information of the second domain name service platform may be carried in the heartbeat message.

[0045] In this embodiment, the IP address segment corresponding to the IP address of the client is accurately determined through the first correspondence between the preset IP address segment and the domain name service platform, and then the domain name service platform to be selected corresponding to the IP address segment to which the client belongs is accurately determined, so as to realize the process of allocating the domain name service platform to the client through the domain name service platform, and reduce the working pressure of the domain name system. Further, in the case of multiple domain name service platforms to be selected, a domain name service platform with a normal service status can be determined according to the service status information of the domain name service platform to be selected, as the target domain name service platform, so that according to the first correspondence and the service status information of the domain name service platform to be selected, an accurate target domain name service platform with a normal service status can be allocated to the client, ensuring that the target domain name service platform provides domain name services for the client when the service status is normal.

[0046] In one embodiment, according to the service status information corresponding to each domain name service platform pre-stored in the first domain name service platform, a domain name service platform with a normal service status is selected from multiple candidate domain name service platforms as the target domain name service platform (i.e., step A2), and the following steps B1-B4 can be executed:

[0047] Step B1, determining priority information corresponding to multiple domain name service platforms to be selected.

[0048] Among them, in the first corresponding relationship between the preset IP address segment and the domain name service platform, if there is a certain IP address segment corresponding to multiple domain name service platforms, the priority information corresponding to the multiple domain name service platforms can be pre-configured.

[0049] The following Table 1 exemplarily shows the domain name service platforms corresponding to multiple IP address segments, and the priority information corresponding to the multiple domain name service platforms. In Table 1, the priority information corresponding to the multiple domain name service platforms is represented in the form of levels (such as level one, level two, level three, etc.). For example, the level one domain name service platform has the highest priority, the level two domain name service platform has the second highest priority, and so on.

[0050] Table 1

[0051]

[0052] Step B2: determining a candidate domain name service platform with the highest priority among multiple candidate domain name service platforms according to the priority information.

[0053] According to the priority information corresponding to each domain name service platform, the first domain name service platform can determine the domain name service platform with the highest priority among multiple domain name service platforms. For example, the "first-level domain name service platform" in Table 1 represents the domain name service platform with the highest priority. When a client in a certain IP address segment makes a domain name request service, the first domain name service platform determines the domain name service platform with the highest priority according to the priority information of the domain name service platform corresponding to the IP address segment. For example, if the IP address segment is "10.196.0.0-10.188.255.254", then among the multiple domain name service platforms corresponding to the IP address segment, the domain name service platform with the highest priority is the first-level domain name service platform (i.e., domain name service platform A).

[0054] Step B3: According to the service status information corresponding to each domain name service platform, if the service status of the candidate domain name service platform with the highest priority is normal, the candidate domain name service platform with the highest priority is determined as the target domain name service platform.

[0055] Following the example in step B2, the first domain name service platform determines the first-level domain name service platform according to the priority information, and when the service status of the first-level domain name service platform is normal, the first-level domain name service platform is used as the target domain name service platform. For example, in Table 1, for the IP address segment "10.196.0.0-10.188.255.254", when the service status of the first-level domain name service platform (i.e., domain name service platform A) is normal, the first-level domain name service platform is used as the target domain name service platform.

[0056] Step B4: If the service status of the candidate domain name service platform with the highest priority is abnormal, a candidate domain name service platform with the second highest priority and normal service status is selected as the target domain name service platform according to the priority information.

[0057] According to the service status information of each domain name service platform pre-stored in the first domain name service platform, the service status information of the highest priority domain name service platform to be selected determined in step B3 can be determined. If the service status of the highest priority domain name service platform to be selected is abnormal, then the first domain name service platform screens the next priority domain name service platform to be selected according to the priority information, and determines the service status of the next priority domain name service platform to be selected. If the service status of the next priority domain name service platform to be selected is normal, the next priority domain name service platform to be selected is determined as the target domain name service platform. If the service status of the next priority domain name service platform to be selected is abnormal, the next priority domain name service platform to be selected continues to be screened according to the priority order until a domain name service platform to be selected with a normal service status is screened out and determined as the target domain name service platform.

[0058] Following the example in step B2, the first domain name service platform determines the first-level domain name service platform according to the priority information. When the service status of the first-level domain name service platform is abnormal, the second-level domain name service platform with the second highest priority can be selected according to the priority information. For example, in Table 1, for the IP address segment "10.196.0.0-10.188.255.254", when the service status of the first-level domain name service platform (i.e., domain name service platform A) is abnormal, the second-level domain name service platform with the second highest priority (i.e., domain name service platform B) can be selected, and so on, until a candidate domain name service platform with a normal service status is found as the target domain name service platform.

[0059] In this embodiment, based on the priority information corresponding to multiple candidate domain name service platforms and the service status information of each candidate domain name service platform, a candidate domain name service platform with the highest priority and normal service status information is determined as the target domain name service platform. Since the candidate domain name service platforms are prioritized in advance, the target domain name service platform can be quickly determined, thereby improving the efficiency of allocating the target domain name service platform to the client.

[0060] In one embodiment, after the target domain name service platform is determined for the client, the following steps C1-C2 may be further performed:

[0061] Step C1: during the connection process between the client and the target domain name service platform, the service status of the candidate domain name service platform with the highest priority is monitored.

[0062] Among them, after determining the target domain name service platform, the first domain name service platform can send the network service address of the target domain name service platform to the client through the domain name system. During the process of the client connecting to the target domain name service platform, the first domain name service platform continues to monitor the service status of the candidate domain name service platform with the highest priority.

[0063] Step C2: after the service status of the candidate domain name service platform with the highest priority returns to normal, the corresponding network service address of the candidate domain name service platform with the highest priority is sent to the client.

[0064] In this embodiment, the first domain name service platform monitors the service status information of the highest priority candidate domain name service platform. When the service status of the highest priority candidate domain name service platform returns to normal, the highest priority candidate domain name service platform can be used as the target domain name service platform, and its corresponding network service address is sent to the client, so that the client can reconnect with the highest priority domain name service platform. Since the highest priority domain name service platform is usually the most compatible with the client (for example, the fastest service speed), this switching method can provide the client with better quality domain name service.

[0065] In another embodiment, after the first domain name service platform detects that the service status of the candidate domain name service platform with the highest priority has returned to normal, the switching action may not be performed, that is, it is not necessary to immediately send the network service address with the highest priority to the client, but when the client sends a domain name service request again, the network service address corresponding to the candidate domain name service platform with the highest priority whose service status has returned to normal is sent to the client. In this way, during the process of the client connecting to the target domain name service platform, the switching action of the target domain name service platform is not performed, thereby avoiding the situation where the domain name service being executed is interrupted due to the platform switching, so that the switching action of the domain name service platform can be performed without the client's perception.

[0066] In this embodiment, during the connection process between the client and the target domain name service platform, if the target domain name service platform is not the highest priority candidate domain name service platform corresponding to the current IP address segment, the first domain name service platform monitors the service status of the highest priority candidate domain name service platform. If it is monitored that the service status of the highest priority domain name service platform has returned to normal, then when the client sends a domain name service request again, the first domain name service platform will send the network service address corresponding to the highest priority candidate domain name service platform to the client, thereby enabling the client to quickly connect to the target domain name service platform that best matches the domain name service request.

[0067] In one embodiment, before the first domain name service platform receives the domain name service request from the client sent by the domain name system (i.e., executes S202), the following steps D1-D2 may be executed:

[0068] Step D1: Send a first heartbeat message to the second domain name service platform, where the first heartbeat message carries service status information of the first domain name service platform.

[0069] The second domain name service platform is any one or more of the multiple domain name service platforms except the first domain name service platform.

[0070] Step D2: receiving a second heartbeat message sent by the second domain name service platform, where the second heartbeat message carries service status information of the second domain name service platform.

[0071] In this embodiment, the first domain name service platform and the second domain name service platform are any domain name service platforms connected to the domain name system, that is, in the network disaster recovery system, different domain name service platforms can send heartbeat messages to each other, and the heartbeat messages carry the service status information of the domain name service platform. Through the heartbeat interaction between the various domain name service platforms, each domain name service platform can obtain the service status information of itself and other domain name service platforms.

[0072] Figure 3 FIG. 1 is a schematic diagram of the heartbeat interaction of each domain name service platform in a network disaster recovery system according to an embodiment of the present application. Figure 3As shown, it is assumed that three domain name service platforms are connected to the domain name system: domain name service platform A, domain name service platform B and domain name service platform C, wherein domain name service platform A sends heartbeat messages to domain name service platform B and domain name service platform C respectively, and the heartbeat messages carry the service status information of domain name service platform A; at the same time, domain name service platform A will also receive the heartbeat messages sent by domain name service platform B and the heartbeat messages sent by domain name service platform C, wherein the heartbeat messages sent by domain name service platform B carry the service status information of domain name service platform B, and the heartbeat messages sent by domain name service platform C carry the service status information of domain name service platform C. It can be seen that through the heartbeat interaction between each domain name service platform, each domain name service platform can obtain the service status information of other domain name service platforms.

[0073] In one embodiment, based on Figure 4 The structure of the network disaster recovery system shown in the figure, when the heartbeat interaction is performed between each domain name service platform, the LocalDNS module in the first domain name service platform can monitor the heartbeat message of the first domain name service platform, and the heartbeat message includes the service status information of the first domain name service platform. The service status information of the first domain name service platform may include the service status information of the IPTV system module. If any network element in the IPTV system module is abnormal, it means that the service status of the first domain name service platform is abnormal. If the network element in the IPTV system module is normal, then the service status of the first domain name service platform is normal. The LocalDNS module in the first domain name service platform can monitor the service status information of the IPTV system module, thereby monitoring the service status information of the first domain name service platform. Similarly, the working principles of other domain name service platforms and the first domain name service platform are the same and will not be repeated. In this embodiment, the functions and interaction methods of each network element in the IPTV system module are all prior art and will not be described in detail here.

[0074] When heartbeat interaction is performed between domain name service platforms, the NGINX module in the first domain name service platform sends a heartbeat message to the LocalDNS module of the second domain name service platform, and the heartbeat message sent by the first domain name service platform carries the service status information of the first domain name service platform. The second domain name service platform can be any one or more except the first domain name service platform. The NGINX module in the second domain name service platform can send a heartbeat message to the LocalDNS module of the first domain name service platform, and the heartbeat message carries the service status information of the second domain name service platform. The first domain name service platform can receive the heartbeat message sent by the second domain name service platform, and thus obtain the service status information of the second domain name service platform through the heartbeat message sent by the second domain name service platform.

[0075] Since the second domain name service platform can be one or more, for example, the first domain name service platform is domain name service platform A, and the second domain name service platform includes domain name service platform B and domain name service platform C. Figure 4 Taking the structure of the domain name service platform in the example as an example, the NGINX module in domain name service platform A sends heartbeat messages to domain name service platform B and domain name service platform C respectively, and the heartbeat message carries the service status information of domain name service platform A. After the LocalDNS module in domain name service platform B receives the heartbeat message sent by domain name service platform A, it forwards it to the NGINX module in domain name service platform B. The NGINX module in domain name service platform B sends a heartbeat message to the LocalDNS module in domain name service platform A, and the heartbeat message carries the service status information of domain name service platform B. After the LocalDNS module in domain name service platform C receives the heartbeat message sent by domain name service platform A, it forwards it to the NGINX module in domain name service platform C. The NGINX module in domain name service platform C sends a heartbeat message to the LocalDNS module in domain name service platform A, and the heartbeat message carries the service status information of domain name service platform C. The NGINX module in domain name service platform B can send a heartbeat message to domain name service platform C. After receiving the heartbeat message sent by domain name service platform B, the LocalDNS module in domain name service platform C forwards it to the NGINX module in domain name service platform C. In other words, the NGINX module in each domain name service platform can send a heartbeat message to the LocalDNS module in other domain name service platforms, and the LocalDNS module in each domain name service platform can receive the heartbeat message sent by the NGINX module in other domain name service platforms, thereby realizing the interaction of service status information between various domain name service platforms.

[0076] In this embodiment, the first domain name service platform can obtain the service status information of the second domain name service platform based on the heartbeat interaction between various modules in the domain name service platform, so that each domain name service platform can know the service status information of other domain name service platforms.

[0077] In one embodiment, after the first domain name service platform sends the first heartbeat message to the second domain name service platform, if the second heartbeat message is not received within a preset time period, it is determined that the service status of the second domain name service platform is abnormal.

[0078] When the first domain name service platform sends a first heartbeat message, but does not receive a second heartbeat message sent by the second domain name service platform within a preset time, it can be determined that the second domain name service platform is abnormal. For example, the preset time is 10 seconds. After the first domain name service platform sends a first heartbeat message carrying service status information to the second domain name service platform, if 10 seconds have passed and the second heartbeat message sent by the second domain name service platform has not been received, it is determined that the service status of the second domain name service platform is abnormal.

[0079] In this embodiment, after the first domain name service platform sends a first heartbeat message, if the second heartbeat message received by the second domain name service platform is not received within a preset time period, it is determined that the service status of the second domain name service platform is abnormal. By determining whether the second heartbeat message is received within the preset time period, the status of the second domain name service platform can be confirmed more quickly.

[0080] The network disaster recovery method provided by the present application is described below through a specific embodiment.

[0081] Figure 5 is a schematic flow chart of a network disaster recovery method according to another embodiment of the present application. In this embodiment, the network disaster recovery method is applied to Figure 1 In the network disaster recovery system shown in the figure. Figure 5 As shown, the method comprises the following steps:

[0082] S501, configuring designated information in each domain name service platform, the designated information including: an IP address segment, a first correspondence between the IP address segment and the domain name service platform, and priority information between multiple domain name service platforms corresponding to the same IP address segment.

[0083] Assume that the priority information between multiple domain name service platforms corresponding to the pre-configured IP address segment is as shown in Table 1.

[0084] S502: The domain name service platforms exchange heartbeat messages, and obtain service status information of each domain name service platform through the heartbeat messages.

[0085] In this step, how to perform heartbeat interaction between various domain name service platforms has been described in detail in the above embodiments, and will not be repeated here. The execution order of S501 and S502 is not limited.

[0086] S503: The client sends a domain name service request to the domain name system. The domain name service request carries the domain name corresponding to the client.

[0087] S504: The domain name system carries the client's domain name service request and forwards it to the first domain name service platform.

[0088] The domain name system forwards the domain name service request to the pre-configured domain name service platform with the highest priority, and uses the domain name service platform with the highest priority and normal service status as the first domain name service platform. When the domain name system receives a domain name service request, it can preferentially forward the domain name service request to the first domain name service platform.

[0089] S505: The first domain name service platform parses the domain name service request to obtain the IP address of the client.

[0090] S506: The first domain name service platform determines a plurality of candidate domain name service platforms corresponding to the IP address segment according to the IP address of the client and a preset first correspondence between the IP address segment and the domain name service platform.

[0091] The first domain name service platform resolves the acquired domain name of the client to obtain the IP address corresponding to the client and determines the IP address segment to which the IP address corresponding to the client belongs. Then, based on the first corresponding relationship and the IP address segment to which the IP address corresponding to the client belongs, multiple candidate domain name service platforms corresponding to the IP address corresponding to the client are determined.

[0092] S507: The first domain name service platform determines a target domain name service platform from the multiple domain name service platforms to be selected according to the priority information corresponding to the multiple domain name service platforms to be selected and the service status information of each of the domain name service platforms to be selected.

[0093] Among them, the first domain name service platform first determines the domain name service platform with the highest priority among the multiple domain name service platforms to be selected based on the priority information corresponding to the multiple domain name service platforms to be selected, and determines the service status information of the domain name service platform with the highest priority. If the service status of the domain name service platform with the highest priority is normal, then the domain name service platform with the highest priority is determined as the target domain name service platform; if the service status of the domain name service platform with the highest priority is abnormal, then the first domain name service platform selects the domain name service platform with the next priority and the domain name service platform with normal service status in turn as the target domain name service platform according to the priority information.

[0094] S508: The first domain name service platform forwards the network service address of the target domain name service platform to the client through the domain name system.

[0095] S509: The client connects to the target domain name service platform according to the network service address of the target domain name service platform.

[0096] By adopting the technical solution of the embodiment of the present application, since the first domain name service platform can be any domain name service platform in the domain name system, any domain name service platform in the domain name service platform can determine the target domain name service platform for the received domain name service request, without the need for the domain name system to allocate a domain name service platform for the domain name service request, thereby reducing the workload of the domain name system in processing domain name service requests and improving the processing efficiency of domain name service requests. Furthermore, since the technical solution distributes the process of allocating the target domain name service platform to the first domain name service platform, even if the status of a certain domain name service platform (or platforms) is abnormal, the first domain name service platform can still allocate the corresponding target domain name service platform for the domain name service request, without the need for the domain name system to handle disaster recovery, and without the need for manual device switching, thereby improving disaster recovery efficiency.

[0097] In summary, specific embodiments of the present subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recorded in the claims can be performed in a different order and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing can be advantageous.

[0098] The above is a network disaster recovery method provided in an embodiment of the present application. Based on the same idea, an embodiment of the present application also provides a network disaster recovery device.

[0099] Figure 6 is a schematic block diagram of a network disaster recovery device according to an embodiment of the present application, such as Figure 6 As shown, the device is applied to a first domain name service platform, including:

[0100] The receiving module 61 is used to receive a domain name service request from a client sent by the domain name system; the domain name service request carries the domain name corresponding to the client; the domain name system is connected to multiple domain name service platforms; the first domain name service platform is any one of the multiple domain name service platforms;

[0101] The resolution module 62 is used to resolve the domain name corresponding to the client based on the domain name service request, and obtain the domain name resolution result corresponding to the client;

[0102] A first determination module 63 is used to determine a target domain name service platform for providing domain name service for the client from multiple domain name service platforms according to the domain name resolution result;

[0103] The first sending module 64 is used to send the network service address corresponding to the target domain name service platform to the client; the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

[0104] In one embodiment, the domain name resolution result includes an Internet Protocol IP address;

[0105] When the first determination module 63 determines the target domain name service platform that provides domain name service for the client from the multiple domain name service platforms according to the domain name resolution result, the first determination module 63 specifically performs the following steps:

[0106] According to a first correspondence between a preset IP address segment and a domain name service platform, a domain name service platform corresponding to the IP address corresponding to the client is determined as a target domain name service platform.

[0107] In one embodiment, when the first determination module 63 determines the domain name service platform corresponding to the IP address corresponding to the client as the target domain name service platform according to the first correspondence between the preset IP address segment and the domain name service platform, the first determination module 63 specifically performs the following steps:

[0108] According to the first corresponding relationship, determine multiple domain name service platforms to be selected corresponding to the IP address corresponding to the client;

[0109] According to the service status information corresponding to each domain name service platform pre-stored in the first domain name service platform, a domain name service platform with a normal service status is selected from a plurality of candidate domain name service platforms as the target domain name service platform.

[0110] In one embodiment, the first determination module 63 selects a domain name service platform with a normal service status from multiple candidate domain name service platforms according to the service status information corresponding to each domain name service platform pre-stored in the first domain name service platform as the target domain name service platform, and specifically performs the following steps:

[0111] Determine priority information corresponding to multiple domain name service platforms to be selected;

[0112] Determine, according to the priority information, a candidate domain name service platform with the highest priority among multiple candidate domain name service platforms;

[0113] According to the service status information corresponding to each domain name service platform, if the service status of the candidate domain name service platform with the highest priority is normal, the candidate domain name service platform with the highest priority is determined as the target domain name service platform;

[0114] If the service status of the candidate domain name service platform with the highest priority is abnormal, the candidate domain name service platform with the second highest priority and normal service status is selected as the target domain name service platform according to the priority information.

[0115] In one embodiment, the network disaster recovery device further includes:

[0116] A monitoring module is used to monitor the service status of the candidate domain name service platform with the highest priority during the connection process between the client and the target domain name service platform after selecting the candidate domain name service platform with the second highest priority and normal service status as the target domain name service platform;

[0117] The second sending module is used to send the corresponding network service address of the candidate domain name service platform with the highest priority to the client after the service status of the candidate domain name service platform with the highest priority returns to normal.

[0118] In one embodiment, the network disaster recovery device further includes:

[0119] A third sending module is used to send a first heartbeat message to a second domain name service platform before receiving a domain name service request from a client sent by the domain name system; the first heartbeat message carries service status information of the first domain name service platform; the second domain name service platform is any one or more of the multiple domain name service platforms except the first domain name service platform;

[0120] The second receiving module is used to receive a second heartbeat message sent by the second domain name service platform; the second heartbeat message carries the service status information of the second domain name service platform.

[0121] In one embodiment, the network disaster recovery device further includes:

[0122] The second determination module is used to determine that the service status of the second domain name service platform is abnormal if no second heartbeat message is received within a preset time after the first heartbeat message is sent to the second domain name service platform.

[0123] Using the device of the embodiment of the present application, in a domain name system connected to multiple domain name service platforms, the first domain name service platform (any one of the multiple domain name service platforms) receives a domain name service request from a client sent by the domain name system, the domain name service request carries the domain name corresponding to the client, and resolves the domain name corresponding to the client based on the domain name service request to obtain a domain name resolution result corresponding to the client. Then, according to the domain name resolution result, a target domain name service platform for providing domain name service to the client is determined from multiple domain name service platforms. Then, the network service address corresponding to the target domain name service platform is sent to the client, and the client connects to the target domain name service platform through the network service address corresponding to the target domain name service platform. Since the first domain name service platform can be any domain name service platform in the domain name system, any domain name service platform in the domain name service platform can determine the target domain name service platform for the received domain name service request, without the need for the domain name system to allocate a domain name service platform for the domain name service request, thereby reducing the workload of the domain name system in processing domain name service requests and improving the processing efficiency of domain name service requests. Furthermore, since the technical solution distributes the process of allocating the target domain name service platform to the first domain name service platform, even when the status of one (or some) domain name service platform is abnormal, the first domain name service platform can still allocate the corresponding target domain name service platform for the domain name service request without the need for the domain name system to handle disaster recovery, and there is no need for manual switching of equipment, thereby improving disaster recovery efficiency.

[0124] Those skilled in the art should understand that Figure 6 The network disaster recovery device in can be used to implement the network disaster recovery method in the previous article. The detailed description should be similar to the description of the method in the previous article. To avoid tediousness, it will not be repeated here.

[0125] Based on the same idea, an embodiment of the present application also provides a network disaster recovery system. Figure 7 is a schematic block diagram of a network disaster recovery system according to an embodiment of the present application, such as Figure 7 As shown, the system includes: a domain name system 71 and multiple domain name service platforms 72 connected to the domain name system;

[0126] The domain name system 71 is used to receive a domain name service request from a client; the domain name service request carries a domain name corresponding to the client;

[0127] The first domain name service platform 72 is used to resolve the domain name corresponding to the client according to the domain name service request sent by the domain name system 71, and obtain the domain name resolution result corresponding to the client; according to the domain name resolution result, determine the target domain name service platform for providing domain name service for the client from multiple domain name service platforms 72; send the network service address corresponding to the target domain name service platform to the client; the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform; the first domain name service platform is any one of the multiple domain name service platforms 72.

[0128] In one embodiment, the first domain name service platform 72 includes: a domain name resolution device and a network service device;

[0129] A domain name resolution device, used to resolve the domain name corresponding to the client according to the domain name service request sent by the domain name system 71, obtain the domain name resolution result corresponding to the client; and send the domain name resolution result to the network service device;

[0130] The network service device is used to determine a target domain name service platform for providing domain name service for the client from multiple domain name service platforms 72 according to the domain name resolution result; and send the network service address corresponding to the target domain name service platform to the client.

[0131] In one embodiment, the first domain name service platform 72 further includes: a network element device;

[0132] The network element device is used to process corresponding services for the client after the client is connected to the target domain name service platform 72;

[0133] The network service device is also used to monitor the service status information of the network element equipment in the first domain name service platform 72; send the service status information to the domain name resolution device in the first domain name service platform 72, and send it to the domain name resolution device in the second domain name service platform 72; the second domain name service platform 72 is any one or more of the multiple domain name service platforms 72 except the first domain name service platform.

[0134] In one embodiment, the domain name resolution device included in the first domain name service platform 72 is also used to send a first heartbeat message to the second domain name service platform 72; the first heartbeat message carries the service status information of the first domain name service platform 72; and receive a second heartbeat message sent by the second domain name service platform 72; the second heartbeat message carries the service status information of the second domain name service platform 72.

[0135] A system using an embodiment of the present application includes a domain name system and multiple domain name service platforms connected to the domain name system. In the domain name system connected to multiple domain name service platforms, a first domain name service platform (any one of the multiple domain name service platforms) receives a domain name service request from a client sent by the domain name system, the domain name service request carries the domain name corresponding to the client, and resolves the domain name corresponding to the client based on the domain name service request to obtain a domain name resolution result corresponding to the client. Then, according to the domain name resolution result, a target domain name service platform for providing domain name service to the client is determined from the multiple domain name service platforms. Then, the network service address corresponding to the target domain name service platform is sent to the client, and the client connects to the target domain name service platform through the network service address corresponding to the target domain name service platform. Since the first domain name service platform can be any domain name service platform in the domain name system, any domain name service platform in the domain name service platform can determine the target domain name service platform for the received domain name service request, without the need for the domain name system to allocate a domain name service platform for the domain name service request, thereby reducing the workload of the domain name system in processing domain name service requests and improving the processing efficiency of domain name service requests. Furthermore, since the technical solution distributes the process of allocating the target domain name service platform to the first domain name service platform, even when the status of one (or some) domain name service platform is abnormal, the first domain name service platform can still allocate the corresponding target domain name service platform for the domain name service request without the need for the domain name system to handle disaster recovery, and there is no need for manual switching of equipment, thereby improving disaster recovery efficiency.

[0136] Based on the same idea, the embodiment of the present application also provides a network disaster recovery device, such as Figure 8 As shown. The network disaster recovery device may have relatively large differences due to different configurations or performances, and may include one or more processors 801 and memory 802, and the memory 802 may store one or more storage applications or data. Among them, the memory 802 can be a temporary storage or a permanent storage. The application stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the network disaster recovery device. Furthermore, the processor 801 can be configured to communicate with the memory 802 to execute a series of computer executable instructions in the memory 802 on the network disaster recovery device. The network disaster recovery device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input and output interfaces 805, and one or more keyboards 806.

[0137] Specifically in this embodiment, the network disaster recovery device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the network disaster recovery device, and the one or more programs are configured to be executed by one or more processors, including the following computer executable instructions:

[0138] Receiving a domain name service request from a client sent by a domain name system; the domain name service request carries a domain name corresponding to the client; the domain name system is connected to multiple domain name service platforms; the first domain name service platform is any one of the multiple domain name service platforms;

[0139] Based on the domain name service request, resolve the domain name corresponding to the client and obtain the domain name resolution result corresponding to the client;

[0140] According to the domain name resolution result, a target domain name service platform for providing domain name service for the client is determined from multiple domain name service platforms;

[0141] The network service address corresponding to the target domain name service platform is sent to the client; the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

[0142] The technical solution of the embodiment of the present application is adopted, and the network disaster recovery device is applied to the first domain name service platform, including receiving a domain name service request from a client sent by a domain name system, the domain name service request carries the domain name corresponding to the client, the domain name system accesses multiple domain name service platforms, and the first domain name service platform is any one of the multiple domain name service platforms. Based on the domain name service request, the domain name corresponding to the client is resolved to obtain the domain name resolution result corresponding to the client, and according to the domain name resolution result, the target domain name service platform for the client to provide domain name service is determined from the multiple domain name service platforms. The network service address corresponding to the target domain name service platform is sent to the client, and the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform. Among them, the first domain name service platform receives the domain name service request from the client sent by the domain name system, and resolves the service request, determines the target domain name service platform from the multiple domain name service platforms according to the resolution result, and sends the network address corresponding to the target domain name service platform to the client. The first domain name service platform can automatically determine the target domain name service platform from the multiple domain name service platforms without going through the domain name system or manually switching the device, which can solve the problem of low disaster recovery efficiency of the existing disaster recovery system.

[0143] The embodiment of the present application further proposes a computer-readable storage medium, which stores one or more computer programs, and the one or more computer programs include instructions. When the instructions are executed by an electronic device including multiple application programs, the electronic device can execute each process of the above-mentioned network disaster recovery method embodiment, and is specifically used to execute:

[0144] Receiving a domain name service request from a client sent by a domain name system; the domain name service request carries a domain name corresponding to the client; the domain name system is connected to multiple domain name service platforms; the first domain name service platform is any one of the multiple domain name service platforms;

[0145] Based on the domain name service request, resolve the domain name corresponding to the client and obtain the domain name resolution result corresponding to the client;

[0146] According to the domain name resolution result, a target domain name service platform for providing domain name service for the client is determined from multiple domain name service platforms;

[0147] The network service address corresponding to the target domain name service platform is sent to the client; the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

[0148] According to the technical solution of the embodiment of the present application, a computer-readable storage medium is applied to a first domain name service platform, including receiving a domain name service request from a client sent by a domain name system, the domain name service request carries the domain name corresponding to the client, the domain name system accesses multiple domain name service platforms, the first domain name service platform is any one of the multiple domain name service platforms, and based on the domain name service request, the domain name corresponding to the client is parsed to obtain the domain name parsing result corresponding to the client, and according to the domain name parsing result, a target domain name service platform for providing domain name service for the client is determined from multiple domain name service platforms. The network service address corresponding to the target domain name service platform is sent to the client, and the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform. Among them, the first domain name service platform receives the domain name service request from the client sent by the domain name system, and parses the service request, determines the target domain name service platform from multiple domain name service platforms according to the parsing result, and sends the network address corresponding to the target domain name service platform to the client, the first domain name service platform can automatically determine the target domain name service platform from multiple domain name service platforms, without going through the domain name system, and without manually switching devices, which can solve the problem of low disaster recovery efficiency of the existing disaster recovery system.

[0149] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0150] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0151] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0152] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0153] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0154] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0155] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0156] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0157] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0158] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0159] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0160] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0161] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A network disaster recovery method, characterized in that: Applied to the first domain name service platform, the method includes: Receiving a domain name service request from a client sent by a domain name system; the domain name service request carries a domain name corresponding to the client; the domain name system is connected to multiple domain name service platforms; the first domain name service platform is any one of the multiple domain name service platforms; Based on the domain name service request, the domain name corresponding to the client is resolved to obtain a domain name resolution result corresponding to the client; According to the domain name resolution result, determining a target domain name service platform for providing domain name service for the client from the multiple domain name service platforms; The network service address corresponding to the target domain name service platform is sent to the client; the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

2. The method according to claim 1, characterized in that The domain name resolution result includes an Internet Protocol IP address; Determining a target domain name service platform for providing domain name service for the client from the multiple domain name service platforms according to the domain name resolution result includes: According to a first correspondence between a preset IP address segment and a domain name service platform, a domain name service platform corresponding to the IP address corresponding to the client is determined as the target domain name service platform.

3. The method according to claim 2, characterized in that The step of determining, according to a first correspondence between a preset IP address segment and a domain name service platform, a domain name service platform corresponding to the IP address corresponding to the client as the target domain name service platform includes: Determine, according to the first corresponding relationship, a plurality of candidate domain name service platforms corresponding to the IP address corresponding to the client; According to the service status information corresponding to each of the domain name service platforms pre-stored in the first domain name service platform, a domain name service platform with a normal service status is selected from the multiple domain name service platforms to be selected as the target domain name service platform.

4. The method according to claim 3, characterized in that The method of selecting a domain name service platform with a normal service status from the plurality of candidate domain name service platforms according to the service status information corresponding to each of the domain name service platforms pre-stored in the first domain name service platform as the target domain name service platform includes: Determine priority information corresponding to the multiple domain name service platforms to be selected; Determine, according to the priority information, a candidate domain name service platform with the highest priority among the multiple candidate domain name service platforms; According to the service status information corresponding to each of the domain name service platforms, if the service status of the candidate domain name service platform with the highest priority is normal, determining the candidate domain name service platform with the highest priority as the target domain name service platform; If the service status of the candidate domain name service platform with the highest priority is abnormal, then according to the priority information, a candidate domain name service platform with the second highest priority and normal service status is selected as the target domain name service platform.

5. The method according to claim 4, characterized in that After selecting the candidate domain name service platform with the second highest priority and normal service status as the target domain name service platform, the method further includes: During the connection between the client and the target domain name service platform, monitoring the service status of the candidate domain name service platform with the highest priority; After the service status of the candidate domain name service platform with the highest priority returns to normal, the corresponding network service address of the candidate domain name service platform with the highest priority is sent to the client.

6. The method according to claim 1, characterized in that Before receiving the domain name service request sent by the domain name system from the client, the method further includes: Sending a first heartbeat message to a second domain name service platform; the first heartbeat message carries service status information of the first domain name service platform; the second domain name service platform is any one or more of the multiple domain name service platforms except the first domain name service platform; Receive a second heartbeat message sent by the second domain name service platform; the second heartbeat message carries service status information of the second domain name service platform.

7. The method according to claim 6, characterized in that After sending the first heartbeat message to the second domain name service platform, the method further includes: If the second heartbeat message is not received within a preset period of time, it is determined that the service status of the second domain name service platform is abnormal.

8. A network disaster recovery device, characterized in that: Applied to the first domain name service platform, the device includes: A receiving module, configured to receive a domain name service request from a client sent by a domain name system; the domain name service request carries a domain name corresponding to the client; the domain name system is connected to multiple domain name service platforms; the first domain name service platform is any one of the multiple domain name service platforms; A resolution module, used to resolve the domain name corresponding to the client based on the domain name service request, and obtain a domain name resolution result corresponding to the client; A first determination module, configured to determine, according to the domain name resolution result, a target domain name service platform from among the multiple domain name service platforms that provides domain name service for the client; The first sending module is used to send the network service address corresponding to the target domain name service platform to the client; the client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform.

9. A network disaster recovery system, characterized in that: It includes a domain name system and multiple domain name service platforms connected to the domain name system; The domain name system is used to receive a domain name service request from a client; The domain name service request carries the domain name corresponding to the client; A first domain name service platform, configured to resolve the domain name corresponding to the client according to the domain name service request sent by the domain name system, and obtain a domain name resolution result corresponding to the client; According to the domain name resolution result, determining a target domain name service platform for providing domain name service for the client from the multiple domain name service platforms; Sending the network service address corresponding to the target domain name service platform to the client; The client is used to connect to the target domain name service platform through the network service address corresponding to the target domain name service platform; the first domain name service platform is any one of the multiple domain name service platforms.

10. The system according to claim 9, characterized in that The first domain name service platform includes: a domain name resolution device and a network service device; The domain name resolution device is used to resolve the domain name corresponding to the client according to the domain name service request sent by the domain name system, obtain the domain name resolution result corresponding to the client; and send the domain name resolution result to the network service device; The network service device is used to determine a target domain name service platform that provides domain name service for the client from the multiple domain name service platforms according to the domain name resolution result; and send the network service address corresponding to the target domain name service platform to the client.

11. The system according to claim 10, characterized in that The first domain name service platform also includes: a network element device; The network element device is used to process corresponding services for the client after the client is connected to the target domain name service platform; The network service device is also used to monitor the service status information of the network element device in the first domain name service platform; send the service status information to the domain name resolution device in the first domain name service platform, and send it to the domain name resolution device in the second domain name service platform; the second domain name service platform is any one or more of the multiple domain name service platforms except the first domain name service platform.

12. The system according to claim 11, characterized in that The domain name resolution device is further used to send a first heartbeat message to the second domain name service platform; the first heartbeat message carries the service status information of the first domain name service platform; Receiving a second heartbeat message sent by the second domain name service platform; The second heartbeat message carries service status information of the second domain name service platform.

13. An electronic device, characterized in that: The method comprises a processor and a memory electrically connected to the processor, wherein the memory stores a computer program, and the processor is used to call and execute the computer program from the memory to implement the network disaster recovery method according to any one of claims 1 to 7.

14. A computer-readable storage medium, characterized in that: The storage medium is used to store a computer program, and the computer program can be executed by a processor to implement the network disaster recovery method according to any one of claims 1 to 7.