Methods, devices and equipment for self-healing of Domain Name System service failures

By establishing a trusted channel between the cloud and the terminal, and combining an active detection and passive feedback method for DNS fault self-healing, the problem of low efficiency in DNS fault self-healing in existing technologies is solved, achieving rapid and accurate fault recovery and improved business continuity.

CN122554311BActive Publication Date: 2026-11-10ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202611056639.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-07-15
Publication Date
2026-11-10
Estimated Expiration
2046-07-15

AI Technical Summary

Technical Problem

Existing DNS service failure self-healing solutions are inefficient and slow to respond, making it difficult to predict and accurately locate failures before they occur, thus affecting business continuity and user experience.

Method used

By establishing a trusted channel between the cloud and the terminal, combining proactive detection and passive feedback to obtain DNS fault information, performing aggregated analysis, determining the fault dimensions, and dynamically distributing backup IP addresses to achieve rapid self-healing.

Benefits of technology

It enables proactive prediction and real-time awareness of DNS faults, shortening fault recovery time from hours to minutes, improving business continuity and operational intelligence, and reducing bandwidth consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122554311B_ABST
    Figure CN122554311B_ABST
Patent Text Reader

Abstract

This specification discloses a method, apparatus, and device for self-healing Domain Name System (DNS) service failures. The scheme includes: establishing a trusted channel between the cloud and the terminal via a pre-set first IP address; obtaining corresponding DNS service failure information based on the trusted channel through active cloud detection and passive feedback from the terminal; determining the corresponding failure dimension by aggregating and analyzing the DNS service failure information; determining a backup second IP address based on the failure dimension, and distributing the second IP address to the terminal via the trusted channel.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to methods, apparatus and devices for self-healing of Domain Name System (DNS) service failures. Background Technology

[0002] Domain Name System (DNS) service is a distributed directory service that resolves domain names into corresponding IP addresses, enabling addressing and access between network devices. In scenarios with high service availability requirements, such as mobile payments, online games, and instant messaging, the reliability of operator DNS services is a crucial means of ensuring business continuity.

[0003] In some cases, the ISP's DNS service may return abnormal IPs (such as 0.0.0.0, 127.0.0.1, reserved addresses, etc.) due to hijacking, pollution, misconfiguration, etc., causing business requests to fail and affecting user experience and business execution success rate.

[0004] In traditional solutions, the following two methods can be implemented to resolve DNS service failures: 1. HTTP DNS solution: The client bypasses the local DNS and directly queries a trusted DNS server via the HTTP protocol.

[0005] 2. Domain name backup plan: The client has multiple backup domain names pre-configured, and switches to the backup domain name when the primary domain name fails.

[0006] Therefore, a more efficient and timely self-healing solution for Domain Name System (DNS) service failures is needed. Summary of the Invention

[0007] This specification provides one or more embodiments of a Domain Name System (DNS) service fault self-healing method, apparatus, device, and storage medium to solve the following technical problem: the need for a more efficient and timely DNS service fault self-healing solution.

[0008] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows: This specification provides one or more embodiments of a Domain Name System (DNS) service fault self-healing method, including: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Through the active detection in the cloud and the passive feedback from the terminal, the corresponding Domain Name System service fault information is obtained based on the trusted channel; By aggregating and analyzing the domain name system service failure information, the corresponding failure dimensions are determined; Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

[0009] This specification provides one or more embodiments of a Domain Name System (DNS) service fault self-healing device, comprising: The trusted channel establishment module establishes a trusted channel between the cloud and the terminal through a pre-configured first IP address; The fault information acquisition module obtains corresponding domain name system service fault information based on the trusted channel through active detection in the cloud and passive feedback from the terminal. The aggregation analysis module determines the corresponding fault dimensions by aggregating and analyzing the domain name system service fault information. The backup IP distribution module determines a backup second IP address based on the fault dimension, and distributes the second IP address to the terminal based on the trusted channel.

[0010] This specification provides one or more embodiments of a Domain Name System (DNS) service fault self-healing device, comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Through the active detection in the cloud and the passive feedback from the terminal, the corresponding Domain Name System service fault information is obtained based on the trusted channel; By aggregating and analyzing the domain name system service failure information, the corresponding failure dimensions are determined; Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

[0011] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Through the active detection in the cloud and the passive feedback from the terminal, the corresponding Domain Name System service fault information is obtained based on the trusted channel; By aggregating and analyzing the domain name system service failure information, the corresponding failure dimensions are determined; Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

[0012] The above-described at least one technical solution adopted in one or more embodiments of this specification can achieve the following beneficial effects: 1. Achieve proactive prediction and real-time awareness of DNS faults: Through a dual awareness mechanism that combines proactive cloud-based detection tasks with real-time monitoring of service requests on the client side, faults can be detected and predicted in a timely manner before or in the early stages of service disruption, shortening the average detection time. Based on the fault dimension settings, the faults can be accurately located to the required granularity such as "region-operator-domain".

[0013] 2. Construct a highly reliable dual-channel direct IP connection: Both the end-side anomaly detection and reporting channel and the dynamic IP distribution channel are implemented using pre-configured IPs, ensuring that control commands are reachable under any DNS failure environment and solving the availability problem of the disaster recovery channel itself.

[0014] 3. Achieve self-healing closed loop within tens of seconds: From detection and execution → risk reporting → predictive alarm → IP configuration → precise distribution → end-side activation, through dual trusted channels with direct IP connection and cloud-based intelligent decision-making, the fault recovery time is shortened from the traditional hours to minutes, improving business continuity.

[0015] 4. Achieve precise and targeted scheduling to reduce bandwidth consumption: The fault detection system can accurately locate the region-operator-domain granularity and only send configurations to terminals in specific provinces and operators, avoiding full push, narrowing the scope of changes, and reducing bandwidth consumption.

[0016] 5. Enhance the intelligence level of operation and maintenance: Achieve full automation of the entire process from fault perception and decision-making to recovery, reduce reliance on manual intervention, and improve operation and maintenance efficiency. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a self-healing method for Domain Name System (DNS) service failures provided in one or more embodiments of this specification; Figure 2 A schematic diagram of a system architecture in an application scenario provided for one or more embodiments of this specification; Figure 3A detailed flowchart of a domain name system service fault self-healing method in an application scenario, provided for one or more embodiments of this specification; Figure 4 This specification provides an interactive timing diagram of a domain name system service fault self-healing in an application scenario, for one or more embodiments of this specification. Figure 5 A schematic diagram of a domain name system service fault self-healing device provided for one or more embodiments of this specification; Figure 6 This is a structural diagram of a domain name system service fault self-healing device provided for one or more embodiments of this specification. Detailed Implementation

[0019] This specification provides a method, apparatus, device, and storage medium for self-healing of Domain Name System (DNS) service failures.

[0020] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0021] In traditional solutions, HTTPDNS requires the additional integration of a Software Development Kit (SDK), which increases request latency. During initial access or when DNS fails completely, the service address itself may be difficult to resolve, posing a risk to channel availability. Furthermore, it lacks proactive detection and risk prediction capabilities. HTTPDNS can only resolve a limited range of domain names, and its limitations in end-side storage, server-side maintenance, and bandwidth costs make it difficult to serve as a general-purpose technical solution.

[0022] However, alternative domain names may also be hijacked; at the same time, it is necessary to wait for the Transmission Control Protocol (TCP) to time out, resulting in high switching latency; and it is also difficult to solve the problem of the first failure.

[0023] In summary, the traditional approach has the following shortcomings: 1. Delayed and passive fault detection: Traditional solutions lack distributed, real-time end-side detection mechanisms, relying on actual business request failures on the end side to trigger detection. Furthermore, monitoring struggles to provide real-time and comprehensive awareness of localized DNS service failures within specific regions or under specific operators, and it is difficult to aggregate DNS resolution quality across the entire network in real time. Faults are typically only detected after user complaints or widespread business failures, by which time services are already affected.

[0024] 2. Lack of proactive prediction capabilities: Traditional solutions only respond passively and struggle to identify the gradual deterioration trend of DNS services (e.g., slow increase in resolution latency, occasional abnormal IPs). This makes it difficult to intervene proactively before a large-scale failure occurs, thus missing opportunities for disaster recovery.

[0025] 3. Slow response and long recovery time: Traditional solutions involve a lengthy process from fault occurrence, detection, manual intervention, configuration activation to final recovery, with a total time usually exceeding 30 minutes. This makes it difficult to meet the minute-level recovery requirements of high-time-sensitivity businesses such as payment scenarios, resulting in serious user churn.

[0026] 4. Vulnerable channels make it difficult to issue scheduling instructions: Disaster recovery scheduling in traditional solutions relies on domain name resolution. In the event of a DNS failure, the scheduling instructions themselves are difficult to issue to the client through the domain name channel, causing the entire disaster recovery system to fall into the dilemma of "detecting the fault but being unable to recover from the disaster".

[0027] 5. Coarse-grained positioning, making it difficult to target precisely: Alarms only stay at the level of "carrier failure" and are difficult to pinpoint to specific regions, carriers, or domains. This results in disaster recovery strategies being distributed to all users, affecting users in unrelated areas and causing serious bandwidth waste.

[0028] Traditional solutions are all passive response-based, lacking proactive detection and prediction capabilities, making it difficult to intervene before a failure impacts business operations. They are also difficult to use as a general technical solution to solve DNS failures for all domain names, and require high operation and maintenance and bandwidth costs.

[0029] Based on this Figure 1 This diagram illustrates a self-healing method for Domain Name System (DNS) service failures, provided for one or more embodiments of this specification. This method can be applied to various business sectors, such as internet finance, e-commerce, instant messaging, gaming, and government services. The process can be executed by computing devices relevant to the specific sector (e.g., intelligent customer service servers or intelligent mobile terminals for payment services). Certain input parameters or intermediate results within the process can be manually adjusted to improve accuracy.

[0030] Figure 1 The process may include the following steps: S102: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address.

[0031] Figure 2 This is a schematic diagram of a system architecture for one or more embodiments of this specification, which mainly includes three components: cloud, terminal, and external network.

[0032] The cloud-based system primarily comprises a fault detection and awareness center and an IP scheduling and management center. The fault detection and awareness center is responsible for proactively detecting DNS health status and aggregating and analyzing abnormal information reported by terminals; the IP scheduling and management center is responsible for managing domain name-IP mapping relationships and issuing disaster recovery instructions in response to the awareness center's decisions.

[0033] The terminal refers to the client used to perform actual business (such as mobile payment, online games, instant messaging, etc.). It has a built-in intelligent sensing agent that can detect local DNS resolution anomalies (such as resolving to abnormal IPs like 0.0.0.0 or 127.0.0.1) and report them to the cloud through a trusted channel. It can also receive and execute disaster recovery strategies (such as IP mapping relationships) and detection tasks issued by the cloud. Abnormal IPs refer to invalid or reserved IP addresses that appear during DNS resolution, including but not limited to 0.0.0.0, 127.0.0.1, and various reserved IP address ranges defined in the Request for Comments (RFC) standard. These are key indicators for judging DNS anomalies.

[0034] The external network includes the DNS system, business servers, etc. The DNS system is the domain name resolution system, which converts domain names into IP addresses and is the foundation of network access. The business servers are the servers used to execute actual business operations.

[0035] To ensure communication between the cloud and the terminal in the event of a Domain Name System (DNS) failure, a trusted channel is pre-established between the cloud and the terminal. This trusted channel is based on direct IP connection (without relying on domain name resolution) and uses an end-to-end encrypted communication link to ensure that fault reporting and disaster recovery command issuance remain reliable during DNS failures.

[0036] Figure 3 This specification provides a detailed flowchart of a Domain Name System (DNS) service fault self-healing method for one or more embodiments in an application scenario. The cloud receives a connection request initiated by the terminal through its built-in first IP address. During the terminal's compilation and packaging process, the IP address of the cloud's gateway data center and the cloud's certificate public key can be pre-written, enabling the terminal to directly interact with the cloud and initiate a connection request based on its built-in first IP address.

[0037] Based on the Transport Layer Security (TLS) handshake protocol, two-way digital certificate verification is performed with the terminal. TLS is an encrypted communication protocol used to provide confidentiality and data integrity between two communicating applications. The TLS handshake protocol, also known as the Transport Layer Security handshake protocol, is primarily used to negotiate encryption algorithms and exchange symmetric encryption keys before application layer data transmission, ensuring the security of subsequent communication.

[0038] During the two-way digital certificate verification process, the terminal initiates a TLS handshake request to the cloud, carrying an SNI (Server Name Indicator) field containing the original domain name. Upon receiving this request, the cloud sends the certificate in plaintext back to the terminal. The terminal then hashes the certificate using its built-in public key, verifying the certificate in plaintext based on this hash value.

[0039] If the verification is successful, a temporary session key is generated through negotiation and interaction with the terminal. Encrypted communication is then conducted based on this temporary session key, establishing a trusted channel between the terminal and the client. The temporary session key is used to encrypt data exchange during this session. The terminal generates a random number locally, encrypts the random number using a public key in the cloud, and sends it back to the cloud. Both parties then receive the same temporary session key. During data transmission, encrypted communication is performed based on this temporary session key, thus establishing a trusted channel for data exchange.

[0040] S104: Based on the trusted channel, obtain the corresponding Domain Name System service fault information through the active detection of the cloud and the passive feedback of the terminal.

[0041] The cloud-based fault detection and perception system includes an active detection task manager and an intelligent decision processor. The active detection task manager is mainly used to proactively and routinely send DNS resolution detection tasks to the target terminal group.

[0042] Figure 4This diagram illustrates the interactive timing of a Domain Name System (DNS) service fault self-healing process in one or more embodiments of this specification. The cloud-based system formulates an active detection strategy through an active detection task manager. This strategy may include detection targets, execution parameters, etc. Detection targets may include different ISPs, domain names, regions, etc., and their selection can be random or based on historical records to select targets with higher failure rates. Execution parameters may include detection frequency, number of samples per attempt, protocol type, etc., which can be adaptively adjusted based on actual needs. For example, for core domain names, the detection frequency can be set to the minute level, while for non-core domain names, the detection frequency can be appropriately reduced to the hour level. Detection frequencies can be set separately for specific regions and ISPs, and the detection frequency can be appropriately increased when the historical failure frequency of that region is high.

[0043] Based on proactive cloud-based detection, a Domain Name System (DNS) service detection task is sent to the terminal through a trusted channel, enabling the terminal to perform corresponding DNS service resolution based on the DNS service detection task and return the corresponding first resolution result to the cloud through the trusted channel.

[0044] The terminal is equipped with an edge-side intelligent sensing system, which includes a passive anomaly sensing module and an active detection execution module. The active detection execution module receives and executes Domain Name System (DNS) detection tasks sent from the cloud and reports the detection results to achieve active sensing.

[0045] For proactive probing, the cloud dynamically sends formatted DNS probing tasks (including parameters such as target domain name, specified Local DNS, and probing frequency) to terminal devices through an established trusted encrypted channel. The Local DNS is the domain name resolution service performed by the terminal device through the operator's DNS server (e.g., 114.114.114.114), and is the primary monitoring and disaster recovery target. After receiving the task, the terminal initiates a standard DNS resolution request to the specified operator's DNS server as instructed, simulating real business resolution behavior to obtain first-hand resolution results (which may include response IP, time consumption, return code, etc.). The terminal then encrypts and reports these results to the cloud through the trusted channel for subsequent fault diagnosis and root cause analysis. This process does not rely on public DNS throughout, effectively avoiding the risks of intermediate link tampering and resolution failure.

[0046] Based on passive feedback from the terminal, the system receives a second resolution result indicating anomalies in the Domain Name System (DNS) service data during actual business operations. The passive anomaly detection module monitors the DNS resolution results of real business requests, identifies abnormal IPs (such as 0.0.0.0 and 127.0.0.1), and achieves passive detection.

[0047] For passive feedback, the cloud does not need to actively issue probe commands. Instead, it receives DNS resolution anomaly information intercepted and reported in real time by the terminal during business operations. The terminal will perform bypass monitoring of DNS system calls initiated by real business operations; when the resolution result times out, has a non-zero error code (such as SERVFAIL, NXDOMAIN), or returns an abnormal IP (such as 0.0.0.0), it will capture the anomaly information contained in the passive fault and encrypt and report it to the cloud.

[0048] Based on the first and second DNS resolution results, the corresponding Domain Name System (DNS) service failure information is determined. This failure information may include details such as the domain name, region, ISP, network type, client version, and time window related to the anomaly, facilitating analysis in the cloud.

[0049] By combining proactive detection with reactive feedback, the coverage of the two can be complementary. Proactive detection can identify potential problems in advance, while reactive feedback can capture occasional anomalies in real business operations. The combination of the two can avoid missed reports.

[0050] S106: By aggregating and analyzing the domain name system service fault information, the corresponding fault dimensions are determined.

[0051] During the aggregation analysis, the first and second resolution results reported by distributed multi-terminals are aggregated and statistically analyzed according to dimensions such as domain name, operator, and region. Core indicators such as resolution anomaly rate, average resolution latency, and abnormal IP ratio under the corresponding dimension are calculated. When the abnormal indicator under a certain dimension exceeds the preset threshold, it can be determined that there is a domain name system service failure in that dimension.

[0052] Specifically, for Domain Name System (DNS) service failure information, based on a sliding time window, multiple preset statistical dimensions are aggregated and statistically analyzed to obtain corresponding statistical indicators. The cloud-based intelligent decision processor simultaneously receives two types of data: one is the first resolution result of the active detection task on the client side, and the other is the second resolution result of DNS resolution anomalies passively collected during the actual business request process on the client side. The cloud will aggregate and statistically analyze multiple statistical dimensions such as "domain name, region, ISP, network type, client version, and time window," and calculate statistical indicators such as the anomaly ratio, number of abnormal terminals, anomaly duration, resolution time change trend, and abnormal IP type under each dimension.

[0053] Anomaly rate trend analysis is performed based on statistical indicators to predict risks according to preset disaster recovery thresholds. For each statistical indicator, anomaly rate trend analysis is performed based on the statistical indicators obtained by aggregation statistics based on a sliding time window. For example, an alarm is triggered when the anomaly rate exceeds the preset disaster recovery threshold (e.g., >5%); when the anomaly rate is on an upward trend but has not yet reached the threshold (e.g., rising continuously from 0.1% to 2%), it is marked as "risk warning" for early intervention.

[0054] If a risk exists, multidimensional drill-down convergence analysis is performed based on multiple specified dimensions in the statistical dimensions to determine the corresponding fault dimension, thereby achieving fault delimitation. For example, if the cloud selects region, operator, and domain name as specified dimensions, the data reported by the terminal is aggregated and statistically analyzed according to the (region, operator, domain name) triple, and the anomaly rate within a unit time window is calculated (obtained by "number of anomaly parsings / total number of parsings"), and the specific fault dimension is determined based on the anomaly rate.

[0055] In the process of judging specific fault dimensions, based on statistical dimensions, multiple preset specified dimensions are determined. Specified dimensions are usually region, operator, and domain name. In actual situations, they can also be adaptively adjusted according to needs. For example, "client version, network type" and other specified dimensions can be added according to business characteristics to accurately locate whether it is a configuration problem of a specific version of the client or an operator problem under a specific mobile network, avoid positioning deviation, and finally converge to obtain accurate fault dimension information.

[0056] Based on the priority of each specified dimension, drill-down analysis is performed sequentially. During the analysis of each specified dimension, the anomaly rate under different values ​​of that dimension is used to determine the anomaly values ​​corresponding to that dimension. The priority is pre-set and mainly used to determine the order of dimension analysis in this drill-down analysis. At this point, the fault range is located by comparing the anomaly rates of different dimension combinations. For example, if all domain names under "Region A - Operator B" have high anomaly rates, it can be determined that "Region A, Operator B DNS service is faulty." In this case, Region A and Operator B are the corresponding anomaly values. However, since the anomaly rate of all domain names is high, there is no corresponding anomaly value for the specified dimension "domain name." If only "Domain C" has a high anomaly rate under "Region A - Operator B," it can be determined that "Operator B's resolution of Domain C in Region A is abnormal." In this case, further refinement of the sub-region judgment can be performed for Region A to achieve more precise location. This process is a multi-dimensional drill-down convergence process, locating the smallest impact range of the fault from coarse to fine.

[0057] By converging and merging outlier values ​​from each specified dimension, the corresponding fault dimensions are obtained. Through drill-down analysis, the outlier values ​​from each specified dimension that contain outliers are merged to obtain the final fault dimension, which points to the specific dimension with the outlier and the specific value within that dimension.

[0058] Of course, if the current anomaly rate trend analysis does not reach the preset disaster recovery threshold, monitoring can continue.

[0059] S108: Determine a backup second IP address based on the fault dimension, and send the second IP address to the terminal based on the trusted channel.

[0060] The cloud-based domain-IP mapping management center pre-maintains a pool of backup IP resources configured by the business party. Each record includes attributes such as domain name, IP address, applicable province, applicable ISP, priority, and health status. Simultaneously, a scheduling policy generator is set up in the cloud. After the intelligent decision processor outputs fault location results (corresponding to specific abnormal values ​​in the fault dimension), the scheduling policy generator performs a filtering action on backup second IP addresses, generating corresponding IP mapping policies to obtain suitable second IP addresses through filtering and mapping.

[0061] Specifically, based on the abnormal values ​​of each specified dimension corresponding to the fault dimension, a pre-maintained backup IP resource pool is used for matching to obtain candidate IP addresses that match the abnormal values. Taking fault dimensions including domain name, region, and carrier as an example, domain name matching is performed to filter all backup IPs corresponding to the target domain name from the resource pool; region + carrier matching is performed, prioritizing IPs from the same region and carrier (proximity principle to reduce latency); if none are found, the search is expanded to IPs from the same region or different carriers.

[0062] The candidate IP addresses are filtered based on their health status to obtain backup second IP addresses. Through health status filtering, IPs known to be unhealthy are excluded (the cloud performs periodic health checks on backup IPs). Based on the final obtained second IP addresses, a distribution strategy is generated. The selected domain-IP mapping groups are marked with the target distribution range (corresponding to the region + carrier dimension), and accurately distributed to eligible terminals through a trusted channel.

[0063] In addition, such as Figure 2 and Figure 4 As shown, in order to ensure the accuracy of the second IP address publication, a gray-scale publication mechanism can be adopted. Initially, the second IP address is published to a portion of terminals, and after the terminals report that the second IP address is normal, it is then published to a wider range or all terminals.

[0064] After receiving the second IP address and its corresponding mapping configuration package (including signature, version, validity period, etc.), the terminal verifies the signature. If the verification passes, it writes the signature to the mapping cache. At this point, the domain name can be directly connected through the second IP address. When the direct connection is successful and a business response is received, the terminal reports the self-healing effect (including success rate, time consumption, hit rate, etc.) to the cloud so that the cloud can record and iteratively upgrade.

[0065] 1. Achieve proactive prediction and real-time awareness of DNS faults: Through a dual awareness mechanism that combines proactive cloud-based detection tasks with real-time monitoring of service requests on the client side, faults can be detected and predicted in a timely manner before or in the early stages of service disruption, shortening the average detection time. Based on the fault dimension settings, the faults can be accurately located to the required granularity such as "region-operator-domain".

[0066] 2. Construct a highly reliable dual-channel direct IP connection: Both the end-side anomaly detection and reporting channel and the dynamic IP distribution channel are implemented using pre-configured IPs, ensuring that control commands are reachable under any DNS failure environment and solving the availability problem of the disaster recovery channel itself.

[0067] 3. Achieve self-healing closed loop within tens of seconds: From detection and execution → risk reporting → predictive alarm → IP configuration → precise distribution → end-side activation, through dual trusted channels with direct IP connection and cloud-based intelligent decision-making, the fault recovery time is shortened from the traditional hours to minutes, improving business continuity.

[0068] 4. Achieve precise and targeted scheduling to reduce bandwidth consumption: The fault detection system can accurately locate the region-operator-domain granularity and only send configurations to terminals in specific provinces and operators, avoiding full push, narrowing the scope of changes, and reducing bandwidth consumption.

[0069] 5. Enhance the intelligence level of operation and maintenance: Achieve full automation of the entire process from fault perception and decision-making to recovery, reduce reliance on manual intervention, and improve operation and maintenance efficiency.

[0070] In one or more embodiments, considering that in actual operation, if a failure occurs in a densely populated area, most terminals may simultaneously flood the same backup second IP address, which may cause ingress congestion or trigger rate limiting on the new IP, affecting user experience.

[0071] Based on this, according to the range corresponding to the fault dimension, the first number of terminals affected by that range is estimated, and the second number corresponding to the backup second IP address is determined based on the first number. At this time, the number of active terminals under this fault dimension in the same historical period can be used as a baseline, and multiplied by the recent growth rate coefficient to estimate the first number; then, the first number is divided by the upper limit of connections that a single backup IP can carry, and rounded up to obtain the required minimum number of backup IPs. If historical data is lacking, probe commands can be sent to a small number of terminals within this dimension in real time, and the total online scale can be estimated by the response samples, and then calculated as above.

[0072] The second number of backup IP addresses is determined based on the fault dimension. In this case, when selecting the second IP address, instead of selecting a single second IP address, the second number of second IP addresses that meet the corresponding requirements (including matching based on the fault dimension, filtering by health status, etc.) are selected. Of course, if the total number of second IP addresses that meet the corresponding requirements does not reach the second number, then all the second IP addresses that meet the corresponding requirements can be selected.

[0073] Based on the second number of second IP addresses, a corresponding scheduling policy is generated and sent to the terminals so that they can select the corresponding second IP address. The scheduling policy includes the second number of second IP addresses. When a terminal receives the scheduling policy, it can choose its own corresponding second IP address. This prevents IP cascading failure. When a large number of terminals switch concurrently, the requests are distributed across the entire IP pool containing the second IP address, preventing any single IP address from being overwhelmed.

[0074] Furthermore, although this method can distribute the pressure on each second IP address, it relies on the terminal's own random selection and may still cause congestion on some of the second IP addresses.

[0075] Based on this, when generating a scheduling policy, a corresponding scheduling policy is generated by specifying a hash algorithm and a currently generated random number, and then the scheduling policy is sent to the terminal. At this point, the scheduling policy includes not only the second IP address but also the selected specified hash algorithm and random number. The specified hash algorithm can be HMAC-SHA256, Maglev, etc. For the random number, a corresponding time limit can be set (e.g., 5 minutes). Within this time limit, the random number is valid. The main purpose of specifying the hash algorithm and random number is to assist the terminal in selecting its corresponding second IP address from multiple second IP addresses.

[0076] The terminal concatenates its unique identifier, the domain name of the currently executed service, and a random number, and then hashes the concatenated string using a specified hash algorithm to obtain a fixed-length digital fingerprint. When calculating its second IP address, the terminal concatenates its unique identifier (e.g., device fingerprint, built-in key), the domain name of the service to be accessed, and a random number into a string. Since different terminals use different random numbers and different actual services at different times, this string inherently possesses randomness. The specified hash algorithm is then used to hash this string, and the resulting fixed-length string serves as the digital fingerprint.

[0077] Modular operations are performed on the digital fingerprint to map it to a finite integer range, resulting in a corresponding index tag. Based on this index tag, each IP address in the locally maintained backup IP address pool is indexed to obtain a second IP address that matches the index tag. The digital fingerprint generated by hash operations is too large to be directly used for addressing. Modular operations force the fingerprint to be mapped to the integer range [0, N-1] by dividing it by the total number of backup IP addresses in the pool and taking the remainder. The final remainder serves as the index tag, instructing the terminal to directly select the corresponding IP address from the list.

[0078] In this way, the cloud does not need to record which second IP address each terminal is assigned. It can send the same description packet to enable the terminal to select the backup second IP address on its own. This enables a stateless dispatch scheduling strategy when a large number of terminals switch concurrently, so that the requests are distributed throughout the pool and the pressure on each second IP address in the pool is reduced.

[0079] In one or more embodiments, when generating a backup second IP address for a terminal, matching can be performed based on a specified dimension, which includes a regional dimension. The range of this regional dimension is typically set according to administrative divisions. This can meet the business needs of most terminals. However, for a few more important terminals (such as fixed terminals of core business nodes), directly matching backup IPs according to administrative divisions may result in the selected IP being too far from the actual access point, increasing service access latency and affecting the access experience.

[0080] Based on this, for designated terminals with preset permissions, a corresponding second resolution result is generated based on the abnormal information in the Domain Name System service operation data when the terminal is performing actual business. The preset permissions are set in advance for fixed terminals of core business nodes, which can interact with other terminals within the local area network.

[0081] By using peer-to-peer (P2P) network communication, this system identifies other terminals within its local area network (LAN) that exhibit abnormal data activity related to the Domain Name System (DNS) service. P2P communication refers to a communication model where each node in the network has equal status and can directly transmit data to each other without the need for a central server. Typically, the other terminals within the designated LAN are performing core business-related tasks; therefore, by using this designated terminal, abnormal information can be collected from all terminals within the LAN, quickly summarizing any DNS service anomalies within the LAN.

[0082] The terminal tags corresponding to the specified terminal and other terminals are added to the corresponding second parsing result. The terminal tag can be a unique device identifier for each terminal. The second parsing result carrying the terminal tag is uploaded to the cloud through the specified terminal.

[0083] For a specified terminal and other terminals, the region dimension in the fault dimension is updated based on the location information corresponding to the specified terminal. When the cloud receives this second resolution result, due to the existence of the terminal tag, a very fine-grained label is added to the region dimension in the fault dimension. This allows the cloud to select a second IP address for the specified terminal (and other terminals within its local area network) based on the location information corresponding to the specified terminal (which may be pre-stored in the cloud or carried by the specified terminal in the second resolution result). The second IP address is accurate to the base station level, rather than the coarse administrative division level. This selects the backup IP address closest to the access point of the specified terminal, reducing access latency for core services and improving the access experience of core service nodes. At the same time, it does not require changing the original IP matching logic based on administrative divisions in the cloud. Adaptation can be achieved by only adjusting the fine-grained region dimension for the specified authorized terminals, resulting in strong compatibility.

[0084] Based on the same idea, one or more embodiments of this specification also provide apparatus and devices corresponding to the above methods, such as... Figure 5 , Figure 6 As shown.

[0085] Figure 5 This specification provides a schematic diagram of the structure of a Domain Name System (DNS) service fault self-healing device according to one or more embodiments. The device includes: Trusted channel establishment module 502: The cloud establishes a trusted channel with the terminal through a preset first IP address; The fault information acquisition module 504 acquires the corresponding domain name system service fault information based on the trusted channel through the active detection of the cloud and the passive feedback of the terminal. The aggregation analysis module 506 determines the corresponding fault dimensions by aggregating and analyzing the domain name system service fault information. The backup IP distribution module 508 determines a backup second IP address based on the fault dimension and distributes the second IP address to the terminal based on the trusted channel.

[0086] Optionally, the trusted channel establishment module 502 receives connection requests initiated by the terminal through its built-in first IP address in the cloud. Based on the transport layer secure handshake protocol, two-way digital certificate verification is performed with the terminal; If the verification is successful, a temporary session key is generated through negotiation and interaction with the terminal, and encrypted communication is performed based on the temporary session key, thereby establishing a trusted channel with the terminal.

[0087] Optionally, the fault information acquisition module 504, based on the active detection in the cloud, sends a domain name system service detection task to the terminal through the trusted channel, so that the terminal performs corresponding domain name system service resolution based on the domain name system service detection task, and feeds back the corresponding first resolution result to the cloud through the trusted channel; Based on the passive feedback from the terminal, a second resolution result is received when the domain name system service operation data contains abnormal information during the actual business execution of the terminal; Based on the first and second parsing results, the corresponding Domain Name System service failure information is determined.

[0088] Optionally, the aggregation analysis module 506 aggregates and statistically analyzes multiple preset statistical dimensions based on a sliding time window to obtain corresponding statistical indicators for the domain name system service failure information. Anomaly rate trend analysis is performed based on the statistical indicators to predict risks based on preset disaster recovery thresholds. If a risk exists, a multidimensional drill-down convergence analysis is performed based on multiple specified dimensions in the statistical dimensions to determine the corresponding fault dimension.

[0089] Optionally, the aggregation analysis module 506 determines multiple preset specified dimensions based on the statistical dimensions; Based on the priority of each specified dimension, drill-down analysis is performed sequentially to determine the outlier values ​​corresponding to each specified dimension based on the outlier rate of each specified dimension under different values ​​during the analysis process. The abnormal values ​​of each specified dimension are converged and merged to obtain the corresponding fault dimensions.

[0090] Optionally, the backup IP distribution module 508 matches the abnormal values ​​of each specified dimension corresponding to the fault dimension in a pre-maintained backup IP resource pool to obtain candidate IP addresses that match the abnormal values. The candidate IP addresses are filtered based on their health status to obtain a backup second IP address.

[0091] Optionally, the backup IP distribution module 508 estimates the first number of terminals affected by the range corresponding to the fault dimension, and determines the second number of backup second IP addresses based on the first number. Based on the fault dimension, determine a second number of backup second IP addresses; Based on the second number of second IP addresses, a corresponding scheduling policy is generated, and the scheduling policy is sent to the terminal so that the terminal selects the corresponding second IP address according to the scheduling policy.

[0092] Optionally, the backup IP distribution module 508 generates a corresponding scheduling policy by specifying a hash algorithm and a currently generated random number, and distributes the scheduling policy to the terminal; The terminal concatenates its own unique identifier, the business domain name of the currently executing business, and the random number, and hashes the concatenated string using the specified hash algorithm to obtain a digital fingerprint of fixed length. Modular operation is performed on the digital fingerprint to map it to a finite integer range, resulting in a corresponding index tag. Based on the index tag, each IP address in the local backup IP address pool maintained by the terminal is indexed to obtain a second IP address that matches the index tag.

[0093] Optionally, the fault information acquisition module 504 generates a corresponding second resolution result for a specified terminal with preset permissions, based on the abnormal information of the domain name system service operation data when it performs actual business. Through peer-to-peer network communication, identify other terminals within your local area network whose Domain Name System (DNS) service operation data contains abnormal information; The terminal tags corresponding to the specified terminal and the other terminals are added to the second parsing result corresponding to themselves.

[0094] Optionally, the backup IP distribution module 508 updates the region dimension in the fault dimension based on the location information corresponding to the specified terminal and the other terminals.

[0095] Figure 6This specification provides a schematic diagram of the structure of a Domain Name System (DNS) service fault self-healing device according to one or more embodiments. The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Through the active detection in the cloud and the passive feedback from the terminal, the corresponding Domain Name System service fault information is obtained based on the trusted channel; By aggregating and analyzing the domain name system service failure information, the corresponding failure dimensions are determined; Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

[0096] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium corresponding to the above method, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Through the active detection in the cloud and the passive feedback from the terminal, the corresponding Domain Name System service fault information is obtained based on the trusted channel; By aggregating and analyzing the domain name system service failure information, the corresponding failure dimensions are determined; Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

[0097] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0098] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0100] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0101] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0102] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0103] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0104] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0106] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0107] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0108] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0109] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0110] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0111] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0112] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for self-healing of Domain Name System (DNS) service failures, comprising: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Based on the proactive detection in the cloud, a Domain Name System (DNS) service detection task is sent to the terminal through the trusted channel, so that the terminal performs corresponding DNS service resolution based on the DNS service detection task and sends the corresponding first resolution result back to the cloud through the trusted channel. Based on the passive feedback from the terminal, a second resolution result is received when the domain name system service operation data contains abnormal information during the actual business execution of the terminal; Based on the first and second parsing results, the corresponding Domain Name System service failure information is determined; By aggregating and analyzing the domain name system service failure information according to region, operator, and domain name, the corresponding failure dimensions are determined. Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

2. The method as described in claim 1, wherein the cloud establishes a trusted channel with the terminal through a preset first IP address, specifically including: The cloud-based receiving terminal initiates a connection request using its built-in first IP address; Based on the transport layer secure handshake protocol, two-way digital certificate verification is performed with the terminal; If the verification is successful, a temporary session key is generated through negotiation and interaction with the terminal, and encrypted communication is performed based on the temporary session key, thereby establishing a trusted channel with the terminal.

3. The method as described in claim 1, wherein the domain name system service fault information is aggregated and analyzed according to region, operator, and domain name to determine the corresponding fault dimension, specifically includes: For the domain name system service failure information, based on a sliding time window, multiple preset statistical dimensions are aggregated and statistically analyzed to obtain corresponding statistical indicators; Anomaly rate trend analysis is performed based on the statistical indicators to predict risks based on preset disaster recovery thresholds. If a risk exists, a multidimensional drill-down convergence analysis is performed based on multiple specified dimensions in the statistical dimensions to determine the corresponding fault dimension.

4. The method as described in claim 3, wherein multidimensional drill-down convergence analysis is performed based on multiple specified dimensions in the statistical dimensions to determine the corresponding fault dimensions, specifically including: Based on the statistical dimensions, a number of preset specified dimensions are determined; Based on the priority of each specified dimension, drill-down analysis is performed sequentially to determine the outlier values ​​corresponding to each specified dimension based on the outlier rate of each specified dimension under different values ​​during the analysis process. The abnormal values ​​of each specified dimension are converged and merged to obtain the corresponding fault dimensions.

5. The method as described in claim 4, wherein determining the backup second IP address based on the fault dimension specifically includes: Based on the abnormal values ​​of each specified dimension corresponding to the fault dimension, a matching is performed in a pre-maintained backup IP resource pool to obtain candidate IP addresses that match the abnormal values. The candidate IP addresses are filtered based on their health status to obtain a backup second IP address.

6. The method as described in claim 1, wherein a backup second IP address is determined based on the fault dimension, and the second IP address is sent to the terminal based on the trusted channel, specifically comprising: Based on the range corresponding to the fault dimension, the first number of terminals affected by the range is estimated, and based on the first number, the second number of backup second IP addresses is determined. Based on the fault dimension, determine a second number of backup second IP addresses; Based on the second number of second IP addresses, a corresponding scheduling policy is generated, and the scheduling policy is sent to the terminal so that the terminal selects the corresponding second IP address according to the scheduling policy.

7. The method as described in claim 6, wherein a corresponding scheduling policy is generated based on a second number of second IP addresses, and the scheduling policy is sent to the terminal so that the terminal selects a corresponding second IP address according to the scheduling policy, specifically comprising: By specifying a hash algorithm and the currently generated random number, a corresponding scheduling policy is generated and the scheduling policy is sent to the terminal. The terminal concatenates its own unique identifier, the business domain name of the currently executing business, and the random number, and hashes the concatenated string using the specified hash algorithm to obtain a digital fingerprint of fixed length. Modular operation is performed on the digital fingerprint to map it to a finite integer range, resulting in a corresponding index tag. Based on the index tag, each IP address in the local backup IP address pool maintained by the terminal is indexed to obtain a second IP address that matches the index tag.

8. The method of claim 1, further comprising: For a specified terminal with preset permissions, a corresponding second resolution result is generated based on the abnormal information in the domain name system service operation data when it performs actual business. Through peer-to-peer network communication, identify other terminals within your local area network whose Domain Name System (DNS) service operation data contains abnormal information; The terminal tags corresponding to the specified terminal and the other terminals are added to the second parsing result corresponding to themselves.

9. The method as described in claim 8, wherein determining the backup second IP address based on the fault dimension specifically includes: For the specified terminal and the other terminals, the region dimension in the fault dimension is updated according to the location information corresponding to the specified terminal.

10. A self-healing device for Domain Name System (DNS) service failures, comprising: The trusted channel establishment module establishes a trusted channel between the cloud and the terminal through a pre-configured first IP address; The fault information acquisition module, based on the active detection in the cloud, sends a Domain Name System Service (DNS) detection task to the terminal through the trusted channel, so that the terminal performs corresponding DNS service resolution based on the DNS service detection task, and feeds back the corresponding first resolution result to the cloud through the trusted channel; Based on the passive feedback from the terminal, a second resolution result is received when the domain name system service operation data contains abnormal information during the actual business execution of the terminal; Based on the first and second parsing results, the corresponding Domain Name System service failure information is determined; The aggregation analysis module determines the corresponding fault dimensions by aggregating and analyzing the domain name system service fault information according to region, operator, and domain name. The backup IP distribution module determines a backup second IP address based on the fault dimension, and distributes the second IP address to the terminal based on the trusted channel.

11. The apparatus of claim 10, wherein the trusted channel establishment module receives a connection request initiated by the terminal through its built-in first IP address in the cloud; Based on the transport layer secure handshake protocol, two-way digital certificate verification is performed with the terminal; If the verification is successful, a temporary session key is generated through negotiation and interaction with the terminal, and encrypted communication is performed based on the temporary session key, thereby establishing a trusted channel with the terminal.

12. The apparatus of claim 10, wherein the aggregation analysis module, based on a sliding time window, aggregates and statistically analyzes multiple preset statistical dimensions to obtain corresponding statistical indicators for the domain name system service fault information; Anomaly rate trend analysis is performed based on the statistical indicators to predict risks based on preset disaster recovery thresholds. If a risk exists, a multidimensional drill-down convergence analysis is performed based on multiple specified dimensions in the statistical dimensions to determine the corresponding fault dimension.

13. The apparatus of claim 12, wherein the aggregation analysis module determines a plurality of preset specified dimensions based on the statistical dimensions; Based on the priority of each specified dimension, drill-down analysis is performed sequentially to determine the outlier values ​​corresponding to each specified dimension based on the outlier rate of each specified dimension under different values ​​during the analysis process. The abnormal values ​​of each specified dimension are converged and merged to obtain the corresponding fault dimensions.

14. The apparatus of claim 13, wherein the backup IP distribution module matches the abnormal values ​​of each specified dimension corresponding to the fault dimension in a pre-maintained backup IP resource pool to obtain candidate IP addresses that match the abnormal values; The candidate IP addresses are filtered based on their health status to obtain a backup second IP address.

15. The apparatus of claim 10, wherein the backup IP distribution module estimates the first number of terminals affected by the range corresponding to the fault dimension, and determines the second number of backup second IP addresses based on the first number; Based on the fault dimension, determine a second number of backup second IP addresses; Based on the second number of second IP addresses, a corresponding scheduling policy is generated, and the scheduling policy is sent to the terminal so that the terminal selects the corresponding second IP address according to the scheduling policy.

16. The apparatus of claim 15, wherein the backup IP distribution module generates a corresponding scheduling policy by specifying a hash algorithm and a currently generated random number, and distributes the scheduling policy to the terminal; The terminal concatenates its own unique identifier, the business domain name of the currently executing business, and the random number, and hashes the concatenated string using the specified hash algorithm to obtain a digital fingerprint of fixed length. Modular operation is performed on the digital fingerprint to map it to a finite integer range, resulting in a corresponding index tag. Based on the index tag, each IP address in the local backup IP address pool maintained by the terminal is indexed to obtain a second IP address that matches the index tag.

17. The apparatus of claim 10, wherein the fault information acquisition module generates a corresponding second resolution result for a designated terminal with preset permissions, based on the abnormal information existing in the domain name system service operation data when it performs actual business; Through peer-to-peer network communication, identify other terminals within your local area network whose Domain Name System (DNS) service operation data contains abnormal information; The terminal tags corresponding to the specified terminal and the other terminals are added to the second parsing result corresponding to themselves.

18. The apparatus of claim 17, wherein the backup IP distribution module updates the region dimension in the fault dimension based on the location information corresponding to the designated terminal and the other terminals.

19. A self-healing device for Domain Name System (DNS) service failures, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The cloud establishes a trusted channel with the terminal through a pre-configured first IP address; Based on the proactive detection in the cloud, a Domain Name System (DNS) service detection task is sent to the terminal through the trusted channel, enabling the terminal to perform corresponding DNS service resolution based on the DNS service detection task and return the corresponding first resolution result to the cloud through the trusted channel; based on the passive feedback from the terminal, a second resolution result is received indicating that the DNS service operation data contains abnormal information when the terminal is performing actual business; based on the first resolution result and the second resolution result, the corresponding DNS service fault information is determined; By aggregating and analyzing the domain name system service failure information according to region, operator, and domain name, the corresponding failure dimensions are determined. Based on the fault dimension, a backup second IP address is determined, and based on the trusted channel, the second IP address is sent to the terminal.

Citation Information

Patent Citations

  • Adaptive switching method and system for connectivity diagnosis of DNS (Domain Name Server)

    CN119254665A