DNS disaster recovery method, DNS disaster recovery system, and electronic device

Abstract

Embodiments of the present disclosure provide a DNS disaster recovery method, a DNS disaster recovery system, and an electronic device. The method is applied to a DNS disaster recovery system, the DNS disaster recovery system comprising heterogeneous first DNS and second DNS. The method comprises: the first DNS invokes a configuration interface of the second DNS to send a configuration request to the second DNS, the configuration request comprising configuration information to be synchronized to the second DNS; and if the result of synchronizing the configuration information by the second DNS is abnormal, the first DNS sends the configuration information to an emergency distribution component in the second DNS, so as to send the configuration information to a service node of the second DNS by means of the emergency distribution component. Heterogeneous disaster recovery of a DNS control plane is achieved.

Description

DNS disaster recovery method, DNS disaster recovery system and electronic device

[0001] The present disclosure claims priority to Chinese Patent Application No. 202411054220.2, filed on August 1, 2024 with the Chinese Patent Office, entitled "DNS disaster recovery method, DNS disaster recovery system and electronic device", the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] The present disclosure relates to the field of cloud networks, and more particularly, to a Domain Name System (DNS) disaster recovery method, a DNS disaster recovery system and an electronic device. BACKGROUND

[0003] DNS is a service of the Internet, which is used to convert domain names that are easy to remember and identify into corresponding digital IP addresses, and this process is called domain name resolution. DNS is a key component of the Internet infrastructure, allowing users to access websites through domain names without needing to remember complex IP addresses.

[0004] In view of the vulnerability of a single DNS service system in extreme failure scenarios, and in response to the demand for continuous and stable services of enterprises, it is urgent to design a disaster recovery for the DNS service system. The current mainstream DNS disaster recovery scheme is to use a Name Server (NS) multi-live scheme. Although this scheme achieves heterogeneous disaster recovery at the resolution service level to some extent, it involves various external dependencies such as account management, permission allocation, database interaction, etc. on the control plane based on two completely independent DNSs, and requires enterprise customers to maintain the data consistency of the two sets of DNSs on the control plane independently, which undoubtedly increases the complexity of daily operation. Moreover, it is difficult to quickly and uniformly switch the control plane configuration globally, and it is impossible to achieve heterogeneous disaster recovery of the control plane. SUMMARY

[0005] The present disclosure provides a DNS disaster recovery method, a DNS disaster recovery system and an electronic device, which achieves heterogeneous disaster recovery of the DNS control plane.

[0006] In a first aspect, the present disclosure provides a DNS disaster recovery method applied to a DNS disaster recovery system, wherein the DNS disaster recovery system comprises a first DNS and a second DNS which are heterogeneous; and the method comprises:

[0007] The first DNS calls a configuration interface of the second DNS, and sends a configuration request to the second DNS, wherein the configuration request comprises configuration information to be synchronized to the second DNS;

[0008] If the result of the synchronization of the configuration information by the second DNS is abnormal, the first DNS sends the configuration information to an emergency distribution component in the second DNS to send the configuration information to service nodes of the second DNS through the emergency distribution component.

[0009] In a second aspect, the present disclosure provides a DNS disaster recovery method applied to a first DNS in a DNS disaster recovery system, the DNS disaster recovery system comprising the first DNS and a second DNS heterogeneous to the first DNS; the method comprising:

[0010] sending a configuration request to the second DNS by calling a configuration interface of the second DNS, the configuration request comprising configuration information to be synchronized to the second DNS;

[0011] If the result of the synchronization of the configuration information by the second DNS is abnormal, the first DNS sends the configuration information to an emergency distribution component in the second DNS to send the configuration information to service nodes of the second DNS through the emergency distribution component.

[0012] In a third aspect, the present disclosure provides a DNS disaster recovery method applied to a second DNS in a DNS disaster recovery system, the DNS disaster recovery system comprising the second DNS and a first DNS heterogeneous to the second DNS; the method comprising:

[0013] receiving a synchronization request of configuration information sent by the first DNS by calling a configuration interface of the second DNS;

[0014] In the case that the result of the synchronization of the configuration information by the second DNS is abnormal, an emergency distribution component in the second DNS receives the configuration information sent by the first DNS and sends the configuration information to service nodes of the second DNS.

[0015] In a fourth aspect, the present disclosure provides a DNS disaster recovery system comprising a first DNS and a second DNS which are heterogeneous; the first DNS and the second DNS are configured to execute the method of the first aspect.

[0016] In a fifth aspect, the present disclosure provides an electronic device comprising a memory and a processor.

[0017] The memory is configured to store a computer program.

[0018] The processor is configured to execute the computer program stored in the memory, and the computer program, when running, causes the processor to execute the method of the first aspect, the second aspect or the third aspect.

[0019] In a fifth aspect, the present disclosure provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor performs the method according to the first aspect, the second aspect or the third aspect.

[0020] In a sixth aspect, the present disclosure provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the processor implements the method according to the first aspect, the second aspect or the third aspect.

[0021] In the DNS disaster recovery method, the DNS disaster recovery system and the electronic device provided by the present disclosure, the master-backup channel for the synchronization of the control plane configuration information is constructed between the first DNS and the second DNS. The first DNS synchronizes the configuration information to the second DNS through the master channel, that is, by calling the configuration interface of the second DNS. In the case that the synchronization result of the second DNS is abnormal, the first DNS synchronizes the configuration information to the emergency distribution component in the second DNS through the backup channel, that is, by directly sending the configuration information to the emergency distribution component. The emergency distribution component directly distributes the configuration information to the service nodes of the second DNS, thereby realizing the synchronization of the control plane and the heterogeneous disaster recovery of the first DNS and the second DNS. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without any creative labor.

[0023] FIG. 1 is a schematic diagram of a DNS heterogeneous disaster recovery scheme;

[0024] FIG. 2 is a schematic diagram of a DNS service plane heterogeneous disaster recovery;

[0025] FIG. 3 is a schematic diagram of a DNS control plane exception;

[0026] FIG. 4 is a schematic diagram of a DNS disaster recovery system according to an embodiment of the present disclosure;

[0027] FIG. 5 is a flowchart of a DNS disaster recovery method according to an embodiment of the present disclosure;

[0028] FIG. 6 is a schematic diagram of a DNS disaster recovery system according to an embodiment of the present disclosure;

[0029] FIG. 7 is a schematic diagram of a DNS disaster recovery system according to an embodiment of the present disclosure;

[0030] FIG. 8 is a schematic block diagram of an electronic device according to an embodiment of the present disclosure. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0032] The technical terms used in the embodiments of this disclosure will be introduced.

[0033] NS: is a key component of DNS, responsible for translating domain names (such as example.com) into IP addresses (such as 192.0.2.1).

[0034] NS record: A record type in DNS used to specify the authoritative NS for a domain name. The authoritative NS is the server responsible for answering DNS queries about that domain. The NS record tells the DNS resolver which NS to query for the DNS records for that domain.

[0035] Active NS (NS) configuration refers to publishing multiple NS records for a single domain, essentially configuring multiple authoritative NS records for one domain. When one authoritative NS becomes unavailable, other available authoritative NS records can be selected based on algorithms, such as the Smoothed Round-Trip Time (SRTT) algorithm.

[0036] Global Traffic Manager (GTM): Through DNS-based load balancing strategies, it schedules business domain name requests and routes user requests to the nearest and most valid server address based on the user's source address, business server status, and load balancing strategy.

[0037] DNS heterogeneous disaster recovery: refers to deploying different types of DNS in different environments to ensure that even if a single DNS fails, there are still surviving DNS services to provide resolution services.

[0038] Cloud DNS: refers to the DNS resolution service provided by the public cloud.

[0039] Private DNS: refers to DNS software that users deploy themselves on self-built data centers, hardware servers, or cloud servers (Elastic Compute Service, ECS) to provide DNS configuration and resolution services.

[0040] SRTT algorithm: a method for calculating and smoothing the round-trip time (RTT) in the network. RTT refers to the time required for a data packet to be sent from the sender to the receiver and for the receiver to process and then send the confirmation information back to the sender.

[0041] The current widely used DNS heterogeneous disaster recovery scheme is achieved by integrating different DNS provided by different manufacturers, such as DNS A and DNS B shown in FIG. 1. On the control plane, the consistency of the control plane configuration of the two sets of DNS is ensured by manual maintenance, and on the service plane, the NS records from different DNS are published in parallel to provide services through NS multi-active mode. A user enters a domain name in the browser on the client side, the client sends a domain name query request to the operator local DNS, the operator local DNS can send the domain name query request to DNS A or DNS B for domain name resolution query, and the solid arrows in FIG. 1 indicate that DNS A and DNS B both provide domain name resolution services. Once any of the DNSs has an abnormal condition, the operator local DNS can intelligently select other available DNS according to the SRTT algorithm, as shown by the dashed line in FIG. 2, DNS B does not provide domain name resolution services, and DNS A provides domain name resolution services, realizing seamless switching and disaster recovery of resolution services.

[0042] In the above scheme, if the control plane of any DNS cannot be changed due to abnormality, but the service plane can still maintain the resolution service, if the user wants to establish global traffic management, the configuration of the DNS that does not have abnormality can be changed, but the DNS that has abnormality cannot be changed, as shown in FIG. 3. The result of this situation is that the DNS that does not have abnormality will resolve according to the updated configuration to obtain a new resolution result, and the DNS that has abnormality will continue to resolve according to the old configuration to continue to use the old resolution result, and cannot realize complete traffic switching in the whole network.

[0043] The reason for the above problem is that the current heterogeneous disaster recovery system is constructed based on two independent and logically different DNSs. On the control plane, they each rely on different account systems, permission management, and database resources, etc. Therefore, the existing heterogeneous disaster recovery scheme can only effectively deal with simple service resolution disaster recovery, and cannot realize the sharing and complementation of the control plane between different DNSs.

[0044] To this end, the disclosure embodiments propose a DNS disaster recovery system and a corresponding disaster recovery method, which build the emergency processing and seamless switching capability of two sets of DNS in the control plane abnormal scenario. To solve this difficulty, the disclosure embodiments build a master-slave dual data channel mechanism between the two sets of DNS. The master channel realizes the synchronization of the configuration information of the control plane between the two sets of DNS through the interface call. In the case of master channel synchronization exception, the configuration information is distributed to the NS, i.e., the DNS service node, through the emergency distribution component of the standby channel. Thus, the control plane consistency of the two sets of DNS is ensured, and the control plane disaster recovery of the two sets of DNS is realized.

[0045] FIG. 4 is a structural schematic diagram of a DNS disaster recovery system according to an embodiment of the disclosure. As shown in FIG. 4, the DNS disaster recovery system includes a heterogeneous first DNS and a second DNS. In the service plane, the first DNS and the second DNS can realize heterogeneous disaster recovery of resolution services, while in the control plane, the first DNS and the second DNS need to realize the synchronization of configuration information between them, and there is an important problem of emergency disaster recovery mechanism in the case of failure. As shown in the architecture of FIG. 4, the master channel for the control plane synchronization between the first DNS and the second DNS is in the form of a configuration interface. The first DNS can call the configuration interface of the second DNS to send a synchronization request of configuration information to the second domain name system. The second DNS performs corresponding configuration change processing after receiving the synchronization request, and finally issues the configuration information to the service node. The configuration interface of the second DNS is an external configuration interface provided by the second DNS. For example, a user can configure through the user interface of the client, and the client calls the configuration interface to send the configuration information to the second DNS. For another example, other DNS can call the configuration interface of the second DNS to synchronize the configuration information. It can be understood that the process of calling the configuration interface of the second DNS for configuration usually involves permission verification, persistent storage of configuration information, and may involve external dependent components such as databases, account permission management systems, and middleware. Any link problem may cause the configuration information to be unable to change normally. In the failure scenario, the first DNS can synchronize the configuration information through the standby channel. The standby channel is directly connected by the emergency distribution components of the first DNS and the second DNS. The first DNS no longer calls the regular configuration interface of the second DNS, but directly sends the configuration information to the emergency distribution component in the second DNS. The emergency distribution component in the second DNS directly sends the configuration information to the service node of the second DNS, thereby realizing the control plane disaster recovery.

[0046] FIG. 5 is a flowchart of a DNS disaster recovery method according to an embodiment of the disclosure. The method is applied to the DNS disaster recovery system described above. As shown in FIG. 5, the method includes:

[0047] S501, the first DNS calls a configuration interface of the second DNS, sends a configuration request to the second DNS, and the configuration request includes configuration information to be synchronized to the second DNS.

[0048] The configuration interface of the second DNS is an external interface provided by the second DNS, and a user can call the configuration interface to configure the second DNS through a client, or other DNSs can call the configuration interface of the second DNS to synchronize configuration information to the second DNS. In the embodiment of the present disclosure, the configuration interface can be understood as a main channel for configuring the second DNS.

[0049] For example, in the DNS disaster recovery system provided by the embodiment of the present disclosure, a user submits configuration information through a user interface of the first DNS, and in addition to issuing the configuration information submitted by the user to the service nodes of the first DNS, the first DNS also calls the configuration interface of the second DNS to send a configuration request to the second DNS, and the configuration request carries the configuration information, so as to realize the control plane synchronization of the first DNS and the second DNS.

[0050] S502, if the synchronization result of the configuration information of the second DNS is abnormal, the first DNS sends the configuration information to an emergency distribution component in the second DNS, so as to send the configuration information to the service nodes of the second DNS through the emergency distribution component.

[0051] After the second DNS receives the configuration request of the first DNS, the configuration information in the configuration request will be processed accordingly, and the processing process can include permission verification, persistent storage, and issuance, etc. There is a certain uncertainty in the process, and any problem in any link can cause the synchronization result of the second DNS to be abnormal, that is, the second DNS cannot successfully synchronize the configuration information of the first DNS. In this case, the first DNS uses a backup channel, that is, a channel for the first DNS to connect with the emergency distribution component in the second DNS, to send the configuration information to the emergency distribution component in the second DNS, and the emergency distribution component directly sends the configuration information to the service nodes of the second DNS, so as to avoid a series of processing processes and external dependent components involved in the synchronization using the configuration interface in the main channel, and realize the emergency disaster recovery of the control plane.

[0052] In the DNS disaster recovery method provided by the embodiment of the present disclosure, the main and backup channels for the control plane configuration information synchronization are constructed between the first DNS and the second DNS, the first DNS synchronizes the configuration information to the second DNS through the main channel by calling the configuration interface of the second DNS, in the case that the synchronization result of the second DNS is abnormal, the first DNS directly sends the configuration information to the emergency distribution component in the second DNS through the backup channel, and the emergency distribution component directly issues the configuration information to the service nodes of the second DNS, thereby realizing the control plane synchronization and heterogeneous disaster recovery of the first DNS and the second DNS.

[0053] On the basis of the above-mentioned embodiments, further description is made in combination with Fig. 6. The second DNS includes a gateway, a dispatching and distribution platform, and a resolution service platform. The dispatching and distribution platform can be used to implement persistent storage of DNS configuration information, intelligent calculation of resolution address real-time state, configuration distribution, and service node data consistency verification, etc. The resolution service platform includes service nodes in different regions. Referring to Fig. 6, optionally, the first DNS sends a configuration request to the gateway of the second DNS, the configuration request including configuration information. The second DNS responds to the configuration request to synchronize the configuration information. The process of the second DNS synchronizing the configuration information includes: the gateway of the second DNS authenticates the configuration request. If the authentication is passed, the gateway of the second DNS sends the configuration request to the dispatching and distribution platform of the second DNS. The dispatching and distribution platform stores the configuration information into the database of the second DNS, and sends the configuration information to the service nodes of the second DNS.

[0054] In the embodiments of the present disclosure, the first DNS is connected to the gateway of the second DNS to form a main channel for control plane synchronization. In the configuration processing flow of the main channel, the gateway of the second DNS authenticates the configuration request of the first DNS. After the authentication is passed, the configuration request is sent to the dispatching and distribution platform of the gateway of the second DNS. The data persistence layer in the dispatching and distribution platform can store the configuration information persistently into the database of the second DNS. Then, the event layer in the dispatching and distribution platform determines configuration events such as adding, deleting, searching, modifying, etc. of the configuration of the second DNS, and further distributes the configuration events to the service nodes through the distribution layer. The above-mentioned process is similar to the process of the user configuring the second DNS through the user interface of the client. The main channel plays a key role in updating configuration information in normal state. However, it cannot completely avoid potential risk factors in control aspect, such as uncertainty caused by external dependent components such as database, account permission management system, and middleware, etc. Therefore, in the embodiments of the present disclosure, a backup channel is added based on the main channel. The first DNS is directly connected to the emergency distribution component of the distribution layer, so as to avoid the above-mentioned processing process of the main channel and external dependence, and to realize direct synchronization and consistency change of the configuration information. Optionally, in the embodiments of the present disclosure, the backup channel can use an independent identity authentication mechanism from the main channel, for example, using certificate verification to ensure the safety and reliability of data transmission.

[0055] In the above embodiment, after the emergency distribution component issues the configuration information to the service node of the second DNS, the service node of the second DNS performs domain name resolution by using the latest configuration information. However, because the standby channel bypasses the processing procedure and external dependent components involved in the main channel, the configuration information is directly issued to the service node of the second DNS without being stored in the persistent storage, which causes the configuration information queried by the user in the WEB console of the second DNS, that is, the user interface, to be the configuration information before synchronization, that is, the configuration information queried by the user is inconsistent with the currently effective configuration information. To avoid this problem, after the configuration information of the second DNS is changed through the standby channel, the data automatic write-back capability is added in the embodiment of the present disclosure, that is, after the emergency distribution component sends the configuration information to the service node of the second DNS, the configuration information is stored in the database of the second DNS, so that when the user queries the configuration information through the user interface, the latest configuration information can be queried from the database, and it is ensured that the configuration information seen by the user is consistent with the actually effective configuration information.

[0056] In the above embodiment, the first DNS synchronizes the configuration information to the second DNS through the main channel, and in the case of abnormality, the second DNS can be synchronized through the standby channel, and the emergency disaster recovery of the control plane is realized. On this basis, the emergency processing of the first DNS control plane failure can also be provided in the embodiment of the present disclosure.

[0057] Optionally, in the case of control plane failure of the first DNS, the domain name resolution service of the first DNS is stopped; if the configuration change is performed by the second DNS in response to the operation of the user in the user interface of the second DNS before the control plane failure of the first DNS is recovered, the changed configuration information is synchronized to the first DNS by the second DNS after the control plane failure of the first DNS is recovered.

[0058] In the case of control plane failure of the first DNS, the domain name resolution service of the first DNS is stopped, that is, the service plane is processed for disaster recovery, and the first DNS no longer provides the domain name resolution service, and the domain name resolution service is performed by the second DNS. In this case, the control plane and the service plane of the second DNS are normal, the second DNS normally provides the service, and if the user performs the operation through the user interface of the second DNS, the configuration change is performed on the second DNS, and the service node of the second DNS performs the domain name resolution according to the changed configuration. In the case of configuration change of the second DNS, the second DNS can synchronize the changed configuration information to the first DNS through the configuration interface of the first DNS. Because the control plane of the first DNS fails to successfully synchronize, the second DNS can synchronize the changed configuration information to the first DNS after the control plane of the first DNS is recovered.

[0059] Through the above-mentioned embodiments of the present disclosure, the consistency of the control plane configuration information of the first DNS and the second DNS is ensured, and on this basis, the consistency of the resolution result of the service plane is described. The service node of the DNS resolves the domain name to the IP address of the server based on a health check mechanism, a load balancing strategy, and deep request source analysis, wherein the health check mechanism refers to health state detection on the IP address corresponding to each domain name to determine whether the IP address corresponding to the domain name is abnormal, so as to resolve the domain name to the IP address that is in normal operation. The load balancing strategy refers to a strategy for scheduling multiple IP addresses corresponding to the domain name when resolving the address, for example, scheduling according to the order, scheduling according to the round robin, or scheduling according to the pre-configured weight, etc., and the load balancing strategy can be configured through the configuration information. The deep request source analysis refers to analyzing the source of the domain name resolution request, such as the source operator or the source IP address, etc. Through the above-mentioned mechanism, the domain name is resolved to the nearest and effective server address.

[0060] In the embodiments of the present disclosure, the second DNS performs health state detection on the IP address corresponding to the domain name, and sends the health state result to the first DNS, or the first DNS performs health state detection on the IP address corresponding to the domain name, and sends the health state result to the second DNS. The health state result is used for domain name resolution, and the health state result is used to indicate whether the IP address is available. That is, in the DNS disaster recovery system of the present disclosure, one set of DNS performs health state detection on the IP address corresponding to the domain name to obtain the health state result, and the other set of DNS directly uses the health state result, and the two sets of DNS use the same health state result, thereby avoiding the inconsistency of the health state result of the IP address corresponding to each domain name in the two sets of DNS due to different detection times, different detection methods, etc. when the two sets of DNS independently perform health state detection.

[0061] The service node of the first DNS or the second DNS resolves the target domain name to the target IP address corresponding to the target domain name in response to the domain name resolution request for the target domain name based on the health state result of one or more IP addresses corresponding to the target domain name, the load balancing strategy in the configuration information, and the source of the domain name resolution request.

[0062] The service node of the first DNS or the second DNS determines one or more IP addresses corresponding to the target domain name close to the source of the domain name resolution request based on the source, and determines a target IP address from the available IP addresses according to a load balancing strategy based on the health status results of the IP addresses. Since the source of the domain name resolution request is certain, in the case that the first DNS and the second DNS adopt the same health status results and the same load balancing strategy, the resolution results are the same for the domain name resolution request whether the first DNS or the second DNS is used for domain name resolution. Thus, the resolution accuracy of the first DNS and the second DNS is highly aligned, and the user is provided with a high-quality service experience without difference.

[0063] Optionally, in the embodiment of the present disclosure, the first DNS is a cloud resolution DNS or an Internet Data Center (IDC) DNS, and the second DNS is a cloud resolution DNS. The first DNS is referred to as a fusion cloud DNS, and the second DNS is referred to as a cloud resolution DNS.

[0064] Referring to FIG. 7, a service plane and a control plane dual-plane heterogeneous disaster recovery service scheme is constructed by a cloud resolution DNS and a fusion cloud DNS. The cloud resolution DNS includes two key parts: a DNS global service scheduling and distribution platform and a DNS global resolution service platform. The DNS global service scheduling and distribution platform bears the tasks of persistent storage of DNS configuration information, intelligent calculation of real-time resolution address detection state, accurate and efficient configuration distribution mechanism, and strict global node data consistency verification; the DNS global resolution service platform is distributed in multiple regions around the world, and provides efficient domain name resolution services. In the top architecture of the cloud resolution DNS, relying on the Point of Presence (POP) gateway and the WEB console, an intuitive and friendly user operation interface is provided, and standardized API operation is also supported, and the security and controllability of the service are ensured through strict account authentication mechanism. Although the cloud resolution DNS has full-link heterogeneous capability, in order to avoid service stagnation of a single DNS service provider in an extreme scenario, a fusion cloud DNS is integrated in the embodiment of the present disclosure, which can be a flexible and scalable private DNS software, and can be independently deployed in various environments such as ECS servers in any cloud environment and self-built IDCs, thereby giving users the ability to independently construct and operate heterogeneous DNS disaster recovery services and comprehensively improve the robustness of high-reliability construction. The control plane of the fusion cloud DNS adopts a heterogeneous disaster recovery mechanism, that is, the fusion cloud DNS includes a control platform and a heterogeneous control platform that is heterogeneous to the control platform, and also includes service nodes distributed in different regions for providing DNS resolution services.

[0065] The fusion cloud DNS and the cloud resolution DNS are combined to realize high-precision resolution function alignment. Through the double-plane heterogeneous architecture of the control plane and the service plane, the scheduling consistency and the seamless integration of the heterogeneous disaster recovery mechanism can be ensured. For example, the fusion cloud DNS is used to uniformly manage the cloud resolution DNS, that is, the fusion cloud DNS is used as the primary management node, and the cloud resolution DNS is used as the backup management node. The advantage of this mode is that the fusion cloud DNS can be flexibly deployed in any environment as a private DNS, helping users to flexibly build heterogeneous services, and the cloud resolution DNS is used as a platform service to provide unified and standard OPENAPI services, which is beneficial to users to build heterogeneous disaster recovery services.

[0066] The fusion cloud DNS is a private DNS resolution solution, and the running environment and resources thereof are completely controlled by the user. When the control plane of the fusion cloud DNS fails, the user can temporarily suspend the resolution service of the fusion cloud DNS, and can change the configuration through the WEB console of the cloud resolution DNS, and then seamlessly switch to the cloud resolution DNS for resolution to provide continuous and stable resolution services. After the control plane of the fusion cloud DNS recovers, the cloud resolution DNS can synchronize the changed configuration information to the fusion cloud DNS.

[0067] The cloud resolution DNS is a platform service, and the operation permission of the user usually stops at the interface opened by the platform, and cannot directly access the underlying server resources. Therefore, in the case of control plane failure of the cloud resolution DNS, the user usually cannot take active intervention measures, but can only passively wait for the recovery of the system. Therefore, the emergency processing and seamless switching capability under the abnormal situation of the control plane of the cloud resolution DNS is very important. In the embodiment of the present disclosure, a primary and backup data channel mechanism is constructed. In the primary channel, the fusion cloud DNS is seamlessly connected to the POP gateway of the cloud resolution DNS, and the OPENAPI interface of the cloud resolution DNS is called to realize efficient and accurate configuration information delivery. This process is similar to the way in which the user changes the configuration through the WEB console or independently calls the OPEN API. The backup channel avoids external dependence of the control plane, and the fusion cloud DNS directly connects to the emergency distribution component in the cloud resolution DNS to directly distribute the configuration information to the globally distributed DNS service nodes, realizing direct synchronization and consistency change of the cloud resolution DNS service nodes.

[0068] When the master channel synchronization configuration information is abnormal, the fusion cloud DNS automatically issues configuration information through the backup channel to realize high-reliability change of configuration data. Since the backup channel bypasses the WEB console, the POP gateway, the database, the middleware and other processes and external dependencies, the configuration information is directly issued to the global DNS service node, which may cause the configuration data seen by the user on the WEB console to be inconsistent with the actual parsed and effective data. To avoid this problem, in the embodiment of the present disclosure, the data automatic write-back capability is added when changing the configuration information through the backup channel, that is, the configuration information changed by the backup channel is automatically written back to the database, so as to ensure that the configuration information seen by the user on the WEB console is consistent with the actual parsed and effective configuration information.

[0069] In the heterogeneous architecture at the service level, the NS multi-live scheme is used in the embodiment of the present disclosure, which can realize efficient and robust traffic allocation between different NS addresses. When the heterogeneous construction at the control level is implemented, the synchronization between the fusion cloud DNS and the cloud parsing DNS realizes the high coordination and alignment of the parsing function. This means that no matter whether the operator local DNS selects the fusion cloud DNS or the cloud parsing DNS as the parsing entrance, the consistency of the parsing effect can be ensured.

[0070] The embodiment of the present disclosure provides a DNS disaster recovery method applied to a first DNS in a DNS disaster recovery system, and the method comprises:

[0071] The configuration interface of the second DNS is called to send a configuration request to the second DNS, and the configuration request comprises configuration information to be synchronized to the second DNS; if the result of the second DNS synchronizing the configuration information is abnormal, the configuration information is sent to an emergency distribution component in the second DNS to send the configuration information to service nodes of the second DNS through the emergency distribution component.

[0072] The embodiment of the present disclosure provides a DNS disaster recovery method applied to a second DNS in a DNS disaster recovery system, and the method comprises:

[0073] The synchronization request of the configuration information sent by the first DNS through the configuration interface of the second DNS is received; in the case that the result of the second DNS synchronizing the configuration information is abnormal, the configuration information sent by the first DNS is received by an emergency distribution component in the second DNS, and the configuration information is sent to service nodes of the second DNS.

[0074] The method executed by the first DNS or the second DNS in the above embodiment can refer to the description of the foregoing embodiments, which will not be described here.

[0075] FIG. 8 is a schematic block diagram of an electronic device provided by the embodiment of the present disclosure. As shown in FIG. 8, the electronic device 800 can comprise at least one processor 801 for implementing the DNS disaster recovery method provided by the embodiment of the present disclosure.

[0076] Optionally, the electronic device 800 further includes at least one memory 802 for storing program instructions and / or data. The memory 802 is coupled with the processor 801. The coupling in the embodiments of the present disclosure is the indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, for information interaction between devices, units or modules. The processor 801 can operate in cooperation with the memory 802. The processor 801 can execute program instructions stored in the memory 802. At least one of the at least one memory can be included in the processor.

[0077] Optionally, the electronic device 800 further includes a communication interface 803 for communicating with other devices through a transmission medium, so that the electronic device 800 can communicate with other devices. The communication interface 803 can be, for example, a transceiver, an interface, a bus, a circuit or a device capable of realizing the transceiving function. The processor 801 can utilize the communication interface 803 to transceive data and / or information, and is used to implement the method provided by the embodiments of the present disclosure. For details, refer to the detailed description in the foregoing embodiments, which will not be repeated here.

[0078] The specific connection medium between the processor 801, the memory 802 and the communication interface 803 in the embodiments of the present disclosure is not limited. In FIG. 8, the processor 801, the memory 802 and the communication interface 803 are connected through a bus 804. The bus 804 is represented by a thick line in FIG. 8, and the connection mode between other components is only schematically illustrated, and is not limited. The bus can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, only one thick line is used in FIG. 8, but it does not mean that there is only one bus or only one type of bus.

[0079] It should be understood that the processor in the embodiments of the present disclosure can be an integrated circuit chip with processing capability. In the implementation process, each step of the method embodiments described above can be completed by the integrated logic circuit or the instruction in the form of software in the processor. The processor described above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. Each method, step and logic block diagram disclosed in the embodiments of the present disclosure can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present disclosure can be directly embodied as a hardware code processor for execution, or can be executed by a combination of hardware and software modules in the code processor. The software module can be located in a random memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register or other mature storage medium in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and combines the hardware to complete the steps of the above method.

[0080] It should also be understood that the memory in the embodiments of the present disclosure can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random Access Memory, RAM) used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Sync Link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the system and method described herein is intended to include but not limited to these and any other suitable types of memory.

[0081] The present disclosure also provides a DNS disaster recovery system, comprising a first DNS and a second DNS, wherein the first DNS and the second DNS are configured to perform the method of any one of the preceding embodiments.

[0082] The present disclosure also provides a computer readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed by a processor, the computer program causes the computer to perform the method of any one of the preceding embodiments.

[0083] The present disclosure also provides a computer program product comprising a computer program, which, when executed by a processor, implements the method of any one of the preceding embodiments.

[0084] The terms "unit", "module" and the like used in the present disclosure can be used to represent a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution.

[0085] Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. The choice of hardware or software, or combinations of both, would be dependent on the specific application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. In several embodiments provided in the present disclosure, it will be apparent that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the division of the units described above is merely illustrative, and for example, the division of the units is merely a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be omitted or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0086] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0087] In addition, each functional unit in each embodiment of the present disclosure can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0088] In the above embodiments, the functions of the various functional units can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, the software can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the whole or part of the flow or function according to the embodiments of the present disclosure is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL) or wireless (such as infrared, wireless, microwave, etc.)) way. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media sets. The available medium can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), optical medium (for example, digital video disc (DVD)), or semiconductor medium (for example, solid state disk (SSD)) and the like.

[0089] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present disclosure essentially or say the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0090] The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0091] The above merely provides the specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto, any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present disclosure, which should be covered within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A method of Domain Name System (DNS) disaster recovery, wherein, The method is applied to a DNS disaster recovery system, the DNS disaster recovery system comprising a first DNS and a second DNS which are heterogeneous; the method comprises: The first DNS invokes a configuration interface of the second DNS, and sends a configuration request to the second DNS, wherein the configuration request comprises configuration information to be synchronized to the second DNS; If a result of synchronization of the configuration information by the second DNS is abnormal, the first DNS sends the configuration information to an emergency distribution component in the second DNS, so as to send the configuration information to service nodes of the second DNS through the emergency distribution component.

2. The method of claim 1, wherein, After the emergency distribution component sends the configuration information to the service nodes of the second DNS, the method further comprises: The emergency distribution component stores the configuration information into a database of the second DNS.

3. The method of claim 1 or 2, wherein, The first DNS sends the configuration request to the second DNS, comprising: The first DNS sends the configuration request to a gateway of the second DNS; The method further comprises that the second DNS synchronizes the configuration information in response to the configuration request; The process of synchronization of the configuration information by the second DNS comprises: The gateway of the second DNS authenticates the configuration request, and in the case that the authentication is passed, the gateway of the second DNS sends the configuration request to a scheduling distribution platform of the second DNS, the scheduling distribution platform stores the configuration information into a database of the second DNS, and the scheduling distribution platform sends the configuration information to service nodes of the second DNS.

4. The method of any one of claims 1-3, wherein, Further comprising: In the case that a control plane of the first DNS fails, stopping a domain name resolution service of the first DNS; If the second DNS performs configuration change before the control plane of the first DNS recovers, after the control plane of the first DNS recovers, the second DNS synchronizes the changed configuration information to the first DNS.

5. The method of any one of claims 1-4, wherein, Further comprising: The second DNS performs health state detection on IP addresses corresponding to domain names, and sends health state results to the first DNS, or the first DNS performs health state detection on IP addresses corresponding to domain names, and sends health state results to the second DNS; the health state results are used to indicate whether the IP addresses are available.

6. The method of claim 5, wherein, Further comprising: The service nodes of the first DNS or the second DNS resolve a target domain name to a target IP address corresponding to the target domain name in response to a domain name resolution request for the target domain name, based on health state results of one or more IP addresses corresponding to the target domain name, a load balancing strategy in the configuration information, and a source of the domain name resolution request.

7. The method of any one of claims 1-6, wherein, The first DNS is a cloud resolution DNS or a data center DNS, and the second DNS is a cloud resolution DNS.

8. A Domain Name System (DNS) disaster recovery method, wherein, The method is applied to a first DNS in a DNS disaster recovery system, the DNS disaster recovery system comprising the first DNS and a second DNS which is heterogeneous with the first DNS; the method comprises: sending a configuration request to the second DNS by calling a configuration interface of the second DNS, the configuration request including configuration information to be synchronized to the second DNS; if the second DNS fails to synchronize the configuration information, sending the configuration information to an emergency distribution component in the second DNS to send the configuration information to service nodes of the second DNS through the emergency distribution component.

9. A Domain Name System (DNS) disaster recovery method, wherein, A second DNS applied to a DNS disaster recovery system, the DNS disaster recovery system including the second DNS and a first DNS heterogeneous to the second DNS; the method comprising: receiving a synchronization request of configuration information sent by the first DNS by calling a configuration interface of the second DNS; if the second DNS fails to synchronize the configuration information, an emergency distribution component in the second DNS receiving the configuration information sent by the first DNS and sending the configuration information to service nodes of the second DNS.

10. A Domain Name System (DNS) disaster recovery system, wherein, The DNS disaster recovery system includes a first DNS and a second DNS which are heterogeneous; the DNS disaster recovery system is configured to perform the method of any one of claims 1-7.

11. An electronic device, comprising: comprising: a memory and a processor; the memory is configured to store a computer program; the processor is configured to execute the computer program stored in the memory, and the computer program, when executed, causes the processor to perform the method of any one of claims 1-9.

12. A computer readable storage medium, wherein, The computer readable storage medium stores a computer program, and when the computer program is executed by the processor, the processor performs the method of any one of claims 1-9.

13. A computer program product, wherein, The computer program is executed by the processor to implement the method of any one of claims 1-9.

Images