Top-level domain mirror image area management method, device, system and equipment

Abstract

The invention relates to the technical field of computer networks, and provides a top-level domain mirror image area management method, device, system and equipment, and the method comprises the steps that a main server constructs a DNS catalog area, an auxiliary server transmits a data synchronization request to the main server, and the data synchronization request is transmitted to the main server through a DNS area transmission protocol; and synchronizing the DNS directory area locally constructed by the main server to the local of the auxiliary server. According to the top-level domain mirror image area management method provided by the invention, the centralized DNS directory area is constructed through the main server to serve as a single configuration source of the multi-top-level domain mirror image service, automatic synchronization between the main server and the auxiliary server is realized through a DNS area transmission protocol by utilizing a DNS in-band management mode, and when the areas are increased or removed, the management efficiency of the main server and the auxiliary server is improved. The problems of low efficiency, high error probability and the like caused by manual configuration modification and manual operation are solved, and change scenes of different scales can be adapted by means of protocol transmission capability, so that the automation, the stability and the service reliability of the cluster are remarkably improved.

Description

Technical Field

[0001] This application relates to the field of computer network technology, and in particular to a method, apparatus, system and device for managing top-level domain mirror zones. Background Technology

[0002] Domain Name System (DNS) is one of the most fundamental network services on the Internet and one of the most important network elements in Internet service access. A large volume of user internet activity must be processed primarily through the DNS system. The efficiency, accuracy, and security of the DNS system directly impact the secure and stable operation of Internet services and user experience. With the continuous development of the Internet, DNS has also been given other application functions, such as service scheduling, domain name management, and data analysis, further enhancing its importance.

[0003] A top-level domain (TLD) is the highest-level domain name below the root domain in the Internet DNS namespace. Various normative documents and best practices from authoritative organizations recommend that, for optimal network performance, the authoritative name servers for each TLD should be evenly distributed across different networks and geographical locations. However, due to various constraints, authoritative name servers are not universally deployed for many major TLDs. Furthermore, these TLDs cannot establish mirror servers in the target region using in-band DNS solutions, leading to long latency and even resolution failures for the target region's domain name resolution. Therefore, it is necessary to use out-of-band DNS methods to establish TLD mirror servers in the target region.

[0004] Currently, there are two main approaches to managing full top-level domain (TLD) mirroring: The first is to use a small number of servers to establish a primary-secondary DNS server cluster, serving all TLDs simultaneously; the second is to establish a separate server cluster for each TLD. The former requires zone administrators to manually modify the service software configuration files when adjusting the zone list, then manually modify the configuration files of each secondary server sequentially using out-of-band DNS, and finally reload the configuration on each server. This operation is both inconvenient and error-prone. The latter requires significant management, maintenance, and economic costs for managing each TLD individually. Therefore, current TLD mirroring management suffers from low efficiency and high costs. Summary of the Invention

[0005] This application provides a method, apparatus, system, and device for managing top-level domain mirror zones, in order to solve the problems of low efficiency and high cost in the management of full top-level domain mirrors in the prior art.

[0006] Firstly, this application provides a top-level domain mirror zone management method applied to a master server, the top-level domain mirror zone management method comprising: Construct a DNS directory zone for domain name resolution services; the DNS directory zone is a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services. In response to a data synchronization request sent by the secondary server, the DNS directory zone is synchronized to the secondary server via the DNS zone transfer protocol.

[0007] In one embodiment, constructing the DNS directory zone for the domain name resolution service includes: Generate zone names for DNS directory zones based on invalid domain names in the reserved domain name space; Configure the originating authority record and domain name server record in the DNS directory zone; Configure a resource record in the DNS directory zone that identifies the structure version number of the DNS directory zone; In the direct subdomains of the DNS directory zone, create member nodes corresponding to each top-level domain, and configure pointer records pointing to the corresponding top-level domains on the member nodes; Each member node is assigned an ordinal number by an incrementing integer to obtain the node label value of each member node.

[0008] In one embodiment, after constructing the DNS directory zone for the Domain Name Resolution Service, the method further includes: Based on the classification characteristics of each target top-level domain, the target top-level domains are grouped to obtain the grouping attribute information of each target top-level domain; the classification characteristics include the domain name type, stability characteristics and functional characteristics defined by the Internet Assigned Numbers Authority (IANA); By storing the grouping attribute information in the form of text records into the category identifier domain name of the corresponding target member node, the attribute resource records of each target member node are obtained.

[0009] In one embodiment, the top-level domain mirror zone management method further includes: In response to the instruction to add a new top-level domain mirror zone, a member node corresponding to the new top-level domain is created at the end of the DNS directory zone, and a pointer record pointing to the new top-level domain is configured on the member node; The node label value of the member node is obtained by incrementing the current maximum node label value. The serial number field in the current initial authorization agency record is incremented to update the serial number field.

[0010] In one embodiment, the top-level domain mirror zone management method further includes: In response to the management instruction to delete a top-level domain mirror zone, delete the member node corresponding to the specified top-level domain in the DNS directory zone; The serial number field in the current initial authorization agency record is incremented to update the serial number field.

[0011] Secondly, this application also provides a top-level domain mirror zone management method, applied to a secondary server, the top-level domain mirror zone management method comprising: Send a data synchronization request to the master server; The system receives DNS directory zones sent by the master server via the DNS zone transfer protocol and updates the DNS directory zones locally. The DNS directory zones are a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services.

[0012] In one embodiment, the top-level domain mirror zone management method further includes: When it is detected that the sequence number field in the initial authoritative authority record of the DNS directory zone on the master server increases, the updated DNS directory zone sent by the master server is received through the DNS zone transport protocol, and the sequence number field in the updated DNS directory zone is synchronized. If a new top-level domain is detected in the updated DNS directory zone, a full zone transfer request for the new top-level domain is sent to the master server. The system receives the full resource records of the newly added top-level domain from the master server via the DNS zone transport protocol. Add the newly added top-level domain and its full resource records to the end of the local DNS directory zone.

[0013] In one embodiment, the top-level domain mirror zone management method further includes: When it is detected that the sequence number field in the initial authoritative authority record of the DNS directory zone on the master server increases, the updated DNS directory zone sent by the master server is received through the DNS zone transport protocol, and the sequence number field in the updated DNS directory zone is synchronized. If it is detected that a specified top-level domain has been deleted from the updated DNS directory zone, then the specified top-level domain is removed from the local DNS directory zone.

[0014] Thirdly, this application also provides a top-level domain mirror zone management device, deployed on a master server, the top-level domain mirror zone management device comprising: The building module is used to build DNS directory zones for domain name resolution services; the DNS directory zones are a list of zones used to centrally manage multiple top-level domains that need to provide mirror services. The data synchronization module is used to respond to a data synchronization request sent by the secondary server and synchronize the DNS directory zone to the secondary server via the DNS zone transfer protocol.

[0015] Fourthly, this application also provides a top-level domain mirror zone management device, deployed on a secondary server, the top-level domain mirror zone management device comprising: The request sending module is used to send data synchronization requests to the master server; The data synchronization module is used to receive the DNS directory zones sent by the master server via the DNS zone transfer protocol and update the DNS directory zones to the local machine; the DNS directory zones are a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services.

[0016] Fifthly, this application also provides a top-level domain mirror zone management system, including: a primary server and a secondary server; The master server is used to: construct DNS directory zones for domain name resolution services; the DNS directory zones are a list of zones used to centrally manage multiple top-level domains that need to provide mirror services. The auxiliary server is used to: send data synchronization requests to the master server; The primary server is configured to: respond to the data synchronization request sent by the secondary server, and synchronize the DNS directory zone to the secondary server via the DNS zone transfer protocol; The auxiliary server is used to: receive the DNS directory zone sent by the primary server via the DNS zone transfer protocol, and update the DNS directory zone in its local machine.

[0017] In a sixth aspect, this application provides an electronic device, the electronic device including a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of any of the top-level domain mirror region management methods described above.

[0018] In a seventh aspect, this application also provides a non-transitory computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the top-level domain mirror region management methods described above.

[0019] Eighthly, this application also provides a computer program product comprising a computer program that can be stored on a non-transitory computer-readable storage medium, and which, when executed by the processor, implements the steps of any of the top-level domain mirror area management methods described above.

[0020] The top-level domain mirror zone management method, apparatus, system, and equipment provided in this application construct a centralized DNS directory zone on the master server as a single configuration source for multiple top-level domain mirror services. Utilizing in-band DNS management, it achieves automated synchronization between master and slave servers through the DNS zone transfer protocol. When adding or removing zones, it not only solves the problems of low efficiency and high error probability caused by manual configuration modifications and manual operations, but also adapts to different scales of change scenarios by leveraging the protocol's transmission capabilities. Overall, it realizes unified management and automated deployment of top-level domain mirror services, thereby significantly improving the automation, stability, and service reliability of the cluster. Attached Figure Description

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

[0022] Figure 1 This is a schematic diagram of the structural framework for top-level domain mirror zone management provided in this application.

[0023] Figure 2 This is one of the flowcharts illustrating the top-level domain mirror zone management method for the master server provided in this application.

[0024] Figure 3 This is a schematic diagram of the basic DNS zone structure for SOA records and NS records provided in this application.

[0025] Figure 4 This is a schematic diagram of the basic DNS zone structure for the RR records provided in this application.

[0026] Figure 5 This is a schematic diagram of the DNS zone structure of the member node RR records provided in this application.

[0027] Figure 6 This is a schematic diagram of the structure of the DNS directory area provided in this application.

[0028] Figure 7 This is a schematic diagram of the structure of the newly added top-level domain provided in this application.

[0029] Figure 8 This is the second flowchart illustrating the top-level domain mirror zone management method provided in this application.

[0030] Figure 9 This is one of the structural schematic diagrams of the top-level domain mirror zone management device provided in this application.

[0031] Figure 10 This is the second schematic diagram of the top-level domain mirror zone management device provided in this application.

[0032] Figure 11 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

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

[0034] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein.

[0035] It's important to note that the data distribution within top-level domains also follows the 20:80 principle, meaning that a small number of top-level domains hold the majority of all data across all public top-level domains. Meanwhile, most top-level domains contain relatively little data. Even with lightweight containers, managing each top-level domain individually using dedicated DNS authoritative service instances would be extremely costly in terms of implementation, maintenance, and finances. Considering the potential for single points of failure for individual name servers, the number of name servers would need to be multiplied, further increasing costs. Therefore, it is essential to utilize a primary-secondary name server cluster comprised of several servers to provide mirrored authoritative data services for these top-level domains.

[0036] Currently, when adjusting the list of zones served by a DNS domain name server, zone administrators typically need to first manually modify the service software configuration file, then manually modify the configuration files of each auxiliary server sequentially using out-of-band DNS, and finally reload the configuration on each server. This operation is both inconvenient and error-prone. Although semi-automated configuration can be achieved using methods such as distribution scripts, because this operation is based on out-of-band DNS protocol operations, the operation in various implementation software depends on the configuration steps of the implementation itself. When using heterogeneous software, corresponding steps need to be written separately for each software, making operational problems more likely.

[0037] Therefore, it is urgent to solve the synchronization problem between the primary and secondary servers when the regions in the region list need to be added or removed from the top-level domain full mirror.

[0038] Initially, the core standard document for the Domain Name System (DNS) mentioned "directory"-style data management for the domain name database, but only described a general process. For many years, a unified standard was not established, and experimental explorations based on algorithmic descriptions only existed in the implementations of a few DNS communities. It wasn't until the release of a new core standard document that the DNS directory zone was defined. This document described how to represent a list of zones using the format of regular DNS zones and transmit it using DNS zone transport. The DNS directory zone is the part of the DNS system used to manage the namespace of specific domain names. Its core function is to store and manage the mapping relationship between domain names and Internet Protocol (IP) addresses, thereby enabling domain name resolution.

[0039] Based on this, the management of full mirroring of top-level domains can be achieved by using DNS directory zones for zone list management and synchronization. By adding the top-level domains that need to provide mirroring services as member zones of the DNS directory zone, the DNS zone transfer protocol can be used to synchronize the zone lists between the primary server and the secondary server.

[0040] DNS zone transfer protocols primarily include Authoritative Zone Transfer (AXFR) and Incremental Zone Transfer (IXFR). AXFR is used when a secondary server first obtains zone data or when the primary server's data undergoes significant changes. It transmits the entire zone data from the primary server to the secondary server, ensuring the secondary server has a completely identical copy of the zone data. IXFR, on the other hand, transmits only the changed portion of the zone data to the secondary server when only some changes have occurred. This significantly reduces data transmission volume, improves transmission efficiency, and lowers network bandwidth usage. By appropriately utilizing these two DNS zone transfer protocols, efficient synchronization of zone lists between the primary and secondary servers can be achieved, ensuring the stability and reliability of full mirror management of the top-level domain. This is an in-band DNS transfer mechanism, a process that does not rely on external scripts, manual intervention, or non-standard interfaces, and is entirely based on RFC-compliant DNS protocols.

[0041] A domain name server cluster includes multiple authoritative servers, which are divided into primary and secondary servers. The primary server is responsible for maintaining all domain name information in a specific zone and is the authoritative source of domain name information for that zone. The secondary domain name servers act as backups for the primary servers, replicating domain name information from the primary servers through zone transfers. This division ensures redundancy and stability in domain name resolution.

[0042] Before configuring DNS directory zones, you need to ensure that the implementation of each authoritative server in the domain name server cluster supports DNS directory zones. For example... Figure 1 As shown, Figure 1 This is a schematic diagram of the structural framework for top-level domain mirror zone management provided in this application. The primary server in the domain name server cluster acts as the directory producer for DNS directory zones, providing updates and zone transfers for top-level domain directory zones and each top-level domain. Each secondary server in the domain name server cluster acts as a directory consumer, requesting data updates and zone transfers from the primary server.

[0043] Based on this, the present application proposes the following embodiments, which are described below in conjunction with... Figures 2-8 This application describes the top-level domain mirror zone management method provided.

[0044] This application provides a method for managing top-level domain mirror zones applied to a master server. Figure 2 This is one of the flowcharts illustrating the top-level domain mirror zone management method for the master server provided in this application.

[0045] like Figure 2 As shown, the top-level domain mirror zone management method includes the following steps: Step 210: Construct DNS directory zones for domain name resolution services; the DNS directory zones are lists of zones used to centrally manage multiple top-level domains that need to provide mirroring services; Step 220: In response to the data synchronization request sent by the secondary server, synchronize the DNS directory zone to the secondary server via the DNS zone transfer protocol.

[0046] Specifically, the master server constructs a dedicated DNS directory zone for centralized management and representation of all top-level domains that require mirroring services. This directory zone follows the structure and semantics defined in the core Domain Name System (DNS) standard document, and is organized using the standard DNS zone format, enabling it to utilize existing DNS zone transport mechanisms for data synchronization.

[0047] When a secondary server needs data synchronization, it sends a data synchronization request to the primary server. Upon receiving this request, the primary server uses the DNS zone transfer protocol to transmit the constructed DNS directory zones to each secondary server. Furthermore, each secondary server, after receiving the DNS directory zones constructed by the primary server, updates its local DNS directory zones using the DNS zone transfer protocol, achieving complete synchronization of the top-level domain zone list information. This provides data support for subsequent top-level domain mirroring services, ensuring the stable operation and data consistency of the entire top-level domain mirroring zone management system.

[0048] In addition, since the top-level domain zone list information in the DNS directory zone is not suitable for public disclosure to ordinary businesses, it is necessary to restrict access permissions to the DNS directory zone.

[0049] The top-level domain mirror zone management method provided in this application constructs a centralized DNS directory zone on the master server as a single configuration source for multiple top-level domain mirror services. It utilizes DNS in-band management and achieves automated synchronization between master and slave servers through the DNS zone transfer protocol. When adding or removing zones, it not only solves the problems of low efficiency and high error probability caused by manual configuration modification and manual operation, but also can adapt to different scale of change scenarios by leveraging the protocol transmission capability. Overall, it realizes unified management and automated deployment of top-level domain mirror services, thereby significantly improving the automation, stability and service reliability of the cluster.

[0050] In one embodiment, based on step 201, constructing the DNS directory zone for the Domain Name Resolution Service includes: Generate zone names for DNS directory zones based on invalid domain names in the reserved domain name space; Configure the originating authority record and domain name server record in the DNS directory zone; Configure a resource record in the DNS directory zone that identifies the structure version number of the DNS directory zone; In the direct subdomains of the DNS directory zone, create member nodes corresponding to each top-level domain, and configure pointer records pointing to the corresponding top-level domains on the member nodes; Each member node is assigned an ordinal number by an incrementing integer to obtain the node label value of each member node.

[0051] Specifically, based on the guidelines for directory zones, to ensure that the DNS target zone does not conflict with the public DNS namespace, invalid domain names under the reserved domain name space are used as the basis for generating a dedicated zone name for the DNS directory zone. Preferably, domain names under the invalid domain name space are used as the zone name for the DNS directory zone, constructing the DNS directory zone as global-tlds.invalid. This naming convention conforms to the definition specifications for special purpose domain names, ensuring that the DNS directory zone is inaccessible in a recursive resolution environment, thereby enhancing system security and isolation.

[0052] The DNS directory zone first needs to be enabled in advance on all servers (primary and secondary servers) of the domain name server cluster through static configuration, just like a normal zone, to ensure that the servers in the cluster can recognize and synchronize the DNS directory zone.

[0053] Because DNS directory zones must adhere to the standard constraints of DNS zones, the DNS directory zone `global-tlds.invalid` must be configured with a Start of Authority (SOA) record and a Name Server (NS) record that conform to standard constraints. Although DNS directory zones cannot be accessed via recursive resolution, they require at least one NS resource record (RR) to constitute a semantically correct DNS zone. See also... Figure 3 and Figure 4 , Figure 3 This is a schematic diagram of the basic DNS zone structure for SOA records and NS records provided in this application. Figure 4 This is a schematic diagram of the basic DNS zone structure for the RR records provided in this application.

[0054] The SOA record sets the starting authority record for the DNS directory zone, which includes fields such as sequence number, refresh interval, retry interval, expiration time, and minimum inventory time. The sequence number field is used to identify the version status of the DNS directory zone, and it increments whenever the zone content changes to trigger the update operation of the secondary server.

[0055] The NS record configuration must include at least one NS record pointing to a semantic placeholder name server name. Following directory zone guidelines, the absolute domain name "invalid." is used as the NSDNAME field value; this configuration satisfies DNS protocol syntax requirements.

[0056] Information about directory zones needs to be stored as "attributes." A unique RR (Register Registry) representing the schema version number is configured in the DNS directory zone. This record is of type TXT and indicates the data schema version followed by the current DNS directory zone. This version number can be predefined and upgraded as the schema evolves.

[0057] All top-level domains requiring mirroring services are incorporated into a unified DNS directory zone for management, with each top-level domain serving as a member zone. To this end, direct subdomains named "zones" are created within the DNS directory zone, and corresponding member nodes are created for each top-level domain. Each member node is associated with the top-level domain name it represents through a Pointer Record (PTR). Specifically, the resource data (RDATA) field of the PTR record stores the corresponding top-level domain name, forming a "node-to-top-level domain" mapping. For example, "PTR arpa." associates the current member node with the top-level domain name "arpa" through a pointer record. All top-level domains requiring mirroring services are member zones, and the list of member zones is represented by the PTR record set of the member nodes. Each PTR record is unique within its respective PTR record set.

[0058] To ensure consistent member node order and support ordered processing, all member nodes are sorted according to the specified sorting rules in the document, and node label values ​​are assigned sequentially starting from the integer 1. Each member node uses its node label value as a prefix to form its complete node name. Once assigned, node label values ​​are not reused. Even if a top-level field is deleted, its original number remains vacant to avoid synchronization chaos caused by duplicate numbering.

[0059] You can refer to this. Figure 5 , Figure 5 This is a schematic diagram of the DNS zone structure of the member node RR records provided in this application. Figure 5 The document lists the RR records for member nodes of the top-level domains arpa, bmw, net, com, cn, xn--fiqs8s., and zw in the DNS directory zone.

[0060] This application embodiment constructs a DNS directory zone through a zone naming mechanism, standardized basic configuration, hierarchical top-level domain mapping, and ordered node identification, thereby achieving unified management and flexible expansion of the top-level domain mirror zone.

[0061] In one embodiment, after constructing the DNS directory zone for the Domain Name Resolution Service, the method further includes: Based on the classification characteristics of each target top-level domain, the target top-level domains are grouped to obtain the grouping attribute information of each target top-level domain; the classification characteristics include the domain name type, stability characteristics and functional characteristics defined by the Internet Assigned Numbers Authority (IANA); By storing the grouping attribute information in the form of text records into the category identifier domain name of the corresponding target member node, the attribute resource records of each target member node are obtained.

[0062] Specifically, to achieve more refined management of top-level domain mirror zones, target top-level domains can be grouped according to their classification characteristics. This could be all top-level domains or only a portion of them. Classification characteristics include, but are not limited to, the domain name type, stability features, and functional features defined by the Internet Assigned Numbers Authority (IANA).

[0063] IANA defines domain name types that cover a variety of different top-level domains, categorized according to the domain's purpose and characteristics. The classification criteria defined by IANA are shown in Table 1 below: Table 1 .

[0064] Top-level domains (TLDs) are grouped based on their stability. TLDs with more data are generally more stable, while TLDs with less data are typically registered by commercial enterprises or other entities, and their registration and deregistration are more frequent than other types of TLDs (such as general TLDs and geographic TLDs). Target TLDs can be classified as "stable" or "unstable" based on the actual situation. When member areas in a stable group change, it may indicate an attack or error, requiring an alert to be issued to the administrator for manual configuration to take effect, and the change should be logged. The classification criteria using stability characteristics are shown in Table 2 below: Table 2 .

[0065] Top-level domains are grouped according to their functional characteristics. For example, Internationalized Domain Names for Applications (IDNA) top-level domains typically require special front-end configuration to convert between U tags and A tags. Other top-level domains are reserved for local use, testing, or special purposes; these are not open for registration. If such a top-level domain appears, it may indicate an attack or error, requiring an alert to the administrator for manual configuration and log recording. The classification criteria based on functional characteristics are shown in Table 3 below. Table 3 .

[0066] Additionally, some private top-level domains can be added as needed and grouped separately from the public top-level domains.

[0067] Based on the classification characteristics of each target top-level domain, grouping is performed according to the above grouping method to obtain the grouping attribute information of each target top-level domain. After grouping, a unique category identifier domain name is configured for each target member node corresponding to each target top-level domain. Then, the grouping attribute information is written into the corresponding category identifier domain name through TXT type resource records, forming a structured set of attribute resource records.

[0068] You can refer to this. Figure 6 , Figure 6 This is a schematic diagram of the structure of the DNS directory zone provided in this application. Figure 6 The main file of the entire DNS directory area is displayed, including the basic DNS zone structure, top-level domain member nodes and their attribute resource records.

[0069] Based on the existing DNS directory zone, this embodiment of the invention further enhances the refinement and automation of top-level domain mirror zone management by grouping target top-level domains according to their classification characteristics and storing the group attribute information in the DNS directory zone in the form of standard resource records, thereby achieving structured and scalable metadata management.

[0070] It should be noted that after using DNS directory zones, updates to these zones should be automatic within the domain name server cluster. That is, if a domain name server supporting DNS directory zones completes a zone transfer for the DNS directory zone, it should automatically apply all modifications to that directory without manual intervention. Updates to DNS directory zones include the addition and deletion of top-level domains. The following are examples of DNS directory zone updates.

[0071] In one embodiment, the top-level domain mirror zone management method further includes: In response to the instruction to add a new top-level domain mirror zone, a member node corresponding to the new top-level domain is created at the end of the DNS directory zone, and a pointer record pointing to the new top-level domain is configured on the member node; The node label value of the member node is obtained by incrementing the current maximum node label value. The serial number field in the current initial authorization agency record is incremented to update the serial number field.

[0072] Specifically, when a new top-level domain needs to be added, the system will generate a new top-level domain mirror zone management command. The master server will respond to the new top-level domain mirror zone management command by automatically creating a member node corresponding to the new top-level domain at the end of the DNS directory zone. This member node exists as a direct subdomain of the DNS directory zone and is used to identify the newly added top-level domain.

[0073] Configure a PTR resource record on the newly created member node pointing to the new top-level domain name, thus mapping the node to the new top-level domain. Simultaneously, increment the current maximum node tag value by one, and then use the incremented value as the node tag value for the newly created member node. (See reference...) Figure 7 , Figure 7 This is a schematic diagram of the structure of the newly added top-level domain provided in this application.

[0074] After the member zones of the newly added top-level domain are constructed, the sequence number field in the SOA record of the DNS directory zone is incremented, i.e., the current sequence number field is incremented by one. This sequence number field is used to identify zone update changes, triggering the secondary server to initiate zone transfer synchronization.

[0075] In the scenario of adding new zones to the zone list, this application embodiment automatically adds member zones of the top-level domain at the end of the DNS directory zone, realizing automated management of top-level domain mirror zones. The expansion of the zone list can be completed without manual intervention, improving the management efficiency and operational reliability of top-level domain mirror zones.

[0076] In one embodiment, the top-level domain mirror zone management method further includes: In response to the management instruction to delete a top-level domain mirror zone, delete the member node corresponding to the specified top-level domain in the DNS directory zone; The serial number field in the current initial authorization agency record is incremented to update the serial number field.

[0077] Specifically, when a specified top-level domain needs to be deleted, the system generates a delete top-level domain mirror zone management command. The master server responds to this command by first locating the member node containing the specified top-level domain in the DNS directory zone, and then automatically deleting the corresponding PTR record and its attribute resource records from the DNS directory zone master file. This deletion operation ensures that the top-level domain is no longer listed as a mirror service object, and that subsequent zone transfers will not trigger data synchronization for that domain.

[0078] Since the top-level domain list does not change frequently, the node label values ​​of member nodes do not need to be reused in principle, and the numbering gaps caused by deleting member nodes in the middle of the list do not need to be reactivated.

[0079] After deleting a member zone of a specified top-level domain, the sequence number field in the SOA record within the DNS directory zone is incremented, i.e., the current sequence number field is incremented by one. This sequence number field is used to identify zone update changes, triggering the secondary server to initiate zone transfer synchronization.

[0080] In the scenario of reducing zones in the zone list, this invention automatically deletes member zones of a specified top-level domain in the DNS directory zone, realizing automated management of top-level domain mirror zones. Member reduction of the zone list can be completed without manual intervention, improving the management efficiency and operational reliability of top-level domain mirror zones.

[0081] This application also provides a method for managing top-level domain mirror zones applied to secondary servers. Figure 8 This is the second flowchart illustrating the top-level domain mirror zone management method provided in this application.

[0082] like Figure 8 As shown, the top-level domain mirror zone management method includes the following steps: Step 810: Send a data synchronization request to the master server; Step 820: Receive the DNS directory zone sent by the master server via the DNS zone transfer protocol, and update the DNS directory zone to the local machine; the DNS directory zone is a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services.

[0083] Specifically, the master server constructs a dedicated DNS directory zone for centralized management and representation of all top-level domains that require mirroring services. This directory zone follows the structure and semantics defined in the core Domain Name System (DNS) standard document, and is organized using the standard DNS zone format, enabling it to utilize existing DNS zone transport mechanisms for data synchronization.

[0084] When a secondary server needs data synchronization, it sends a data synchronization request to the primary server. Upon receiving this request, the primary server uses the DNS zone transfer protocol to transmit the constructed DNS directory zones to each secondary server. Furthermore, each secondary server, after receiving the DNS directory zones constructed by the primary server, updates its local DNS directory zones using the DNS zone transfer protocol, achieving complete synchronization of the top-level domain zone list information. This provides data support for subsequent top-level domain mirroring services, ensuring the stable operation and data consistency of the entire top-level domain mirroring zone management system.

[0085] In addition, since the top-level domain zone list information in the DNS directory zone is not suitable for public disclosure to ordinary businesses, it is necessary to restrict access permissions to the DNS directory zone.

[0086] The top-level domain mirror zone management method provided in this application constructs a centralized DNS directory zone on the master server as a single configuration source for multiple top-level domain mirror services. It utilizes DNS in-band management and achieves automated synchronization between master and slave servers through the DNS zone transfer protocol. When adding or removing zones, it not only solves the problems of low efficiency and high error probability caused by manual configuration modification and manual operation, but also can adapt to different scale of change scenarios by leveraging the protocol transmission capability. Overall, it realizes unified management and automated deployment of top-level domain mirror services, thereby significantly improving the automation, stability and service reliability of the cluster.

[0087] It should be noted that after using DNS directory zones, updates to these zones should be automatic within the domain name server cluster. That is, if a domain name server supporting DNS directory zones completes a zone transfer for the DNS directory zone, it should automatically apply all modifications to that directory without manual intervention. Updates to DNS directory zones include the addition and deletion of top-level domains. The following are examples of DNS directory zone updates.

[0088] In one embodiment, the top-level domain mirror zone management method further includes: When it is detected that the sequence number field in the initial authoritative authority record of the DNS directory zone on the master server increases, the updated DNS directory zone sent by the master server is received through the DNS zone transport protocol, and the sequence number field in the updated DNS directory zone is synchronized. If a new top-level domain is detected in the updated DNS directory zone, a full zone transfer request for the new top-level domain is sent to the master server. The system receives the full resource records of the newly added top-level domain from the master server via the DNS zone transport protocol. Add the newly added top-level domain and its full resource records to the end of the local DNS directory zone.

[0089] Specifically, the secondary server periodically queries the sequence number field of the SOA record in the DNS directory zone on the primary server using the DNS zone transfer protocol. When the primary server updates its DNS directory zone, it synchronously updates the sequence number field of the SOA record. The secondary server determines whether an update has occurred by comparing the sequence number field of the SOA record in its locally stored DNS directory zone with the latest sequence number field on the primary server.

[0090] When the secondary server detects an increase in the latest sequence number field on the primary server, it determines that the zone list has been updated and synchronously updates its local sequence number field. At this time, the secondary server automatically triggers the zone transfer process and retrieves the updated complete DNS directory zone data from the primary server through the DNS zone transfer protocol.

[0091] After receiving the updated data, the secondary server parses the PTR record set of the member nodes. If it finds that a certain top-level domain does not exist locally, it determines that the top-level domain is a newly added top-level domain and immediately sends a full zone transfer request for the newly added top-level domain to the primary server to obtain its full resource records.

[0092] After successfully receiving and applying all resource records of the newly added top-level domain via the DNS zone transfer protocol, the secondary server adds the newly added top-level domain and all its resource records to the end of its local DNS directory zone.

[0093] In this embodiment of the application, when a new top-level domain is added to the primary server, the secondary server achieves real-time monitoring and synchronization of the primary server's DNS directory zone updates through the DNS in-band transmission mechanism. This ensures the integrity and accuracy of the secondary server's local DNS directory zone data. This process can be completed without manual intervention, improving the management efficiency and operational reliability of the top-level domain mirror zone.

[0094] In one embodiment, the top-level domain mirror zone management method further includes: When it is detected that the sequence number field in the initial authoritative authority record of the DNS directory zone on the master server increases, the updated DNS directory zone sent by the master server is received through the DNS zone transport protocol, and the sequence number field in the updated DNS directory zone is synchronized. If it is detected that a specified top-level domain has been deleted from the updated DNS directory zone, then the specified top-level domain is removed from the local DNS directory zone.

[0095] Specifically, the secondary server periodically queries the sequence number field of the SOA record in the DNS directory zone on the primary server using the DNS zone transfer protocol. When the primary server updates its DNS directory zone, it synchronously updates the sequence number field of the SOA record. The secondary server determines whether an update has occurred by comparing the sequence number field of the SOA record in its locally stored DNS directory zone with the latest sequence number field on the primary server.

[0096] When the secondary server detects an increase in the latest sequence number field on the primary server, it determines that the zone list has been updated and synchronously updates its local sequence number field. At this time, the secondary server automatically triggers the zone transfer process and retrieves the updated complete DNS directory zone data from the primary server through the DNS zone transfer protocol.

[0097] After receiving the update data, the secondary server resolves the PTR record set of the member nodes. If it finds that the PTR record of a certain top-level domain that exists locally is missing in the update data, it determines that the specified top-level domain has been deleted. At this time, the secondary server automatically removes the specified top-level domain from the local DNS directory zone and stops providing mirror domain name services for the specified top-level domain.

[0098] In this embodiment of the invention, when the primary server removes a top-level domain, the secondary server achieves real-time monitoring and synchronization of the primary server's DNS directory zone updates through the DNS in-band transmission mechanism. This ensures the integrity and accuracy of the secondary server's local DNS directory zone data. This process can be completed synchronously without manual intervention, improving the management efficiency and operational reliability of the top-level domain mirror zone.

[0099] Based on all the above embodiments, the overall process of the top-level domain mirror zone management method is described below.

[0100] The master server builds a dedicated DNS directory zone for centralized management and representation of all top-level domains that require mirroring services.

[0101] When a secondary server needs data synchronization, it sends a data synchronization request to the primary server. Upon receiving this request, the primary server uses the DNS zone transfer protocol to transmit the constructed DNS directory zones to each secondary server. Furthermore, each secondary server, after receiving the DNS directory zones constructed by the primary server using the DNS zone transfer protocol, updates the DNS directory zones to its local machine, achieving complete synchronization of the top-level domain zone list information.

[0102] Based on the directory zone guidelines, to ensure that the DNS target zone does not conflict with the public DNS namespace, invalid domain names under the reserved domain name space are used as the basis to generate a zone name dedicated to the DNS directory zone.

[0103] The DNS directory zone first needs to be enabled in advance on all servers (primary and secondary servers) of the domain name server cluster using static configuration, just like a regular zone. The configuration should include basic DNS zone structures such as SOA records, NS records, and RR records to ensure that the servers in the cluster can recognize and synchronize the DNS directory zone.

[0104] All top-level domains requiring mirroring services are included in a unified DNS directory zone for management, with each top-level domain serving as a member zone. To this end, direct subdomains named "zones" are created within the DNS directory zone, and a corresponding member node is created for each top-level domain. Each member node is associated with the name of the top-level domain it represents via a PTR record. All top-level domains requiring mirroring services are member zones, and the list of member zones is represented by the PTR record set of each member node. Each PTR record is unique within its respective PTR record set.

[0105] To ensure the consistency of member node order and support ordered processing, all member nodes are sorted according to the standard sorting rules specified in the document, and node label values ​​are assigned sequentially starting from the integer 1. Each member node uses its node label value as a prefix label to form the complete node name.

[0106] To achieve more refined management of top-level domain mirror zones, target top-level domains are grouped according to their classification characteristics. This can be all top-level domains or only some top-level domains, ultimately yielding grouping attribute information for each target top-level domain. These classification characteristics include, but are not limited to, the domain name type, stability features, and functional features defined by IANA.

[0107] After grouping is completed, a unique category identifier domain name is configured for each target member node corresponding to the target top-level domain. Then, the grouping attribute information is written into the corresponding category identifier domain name through TXT type resource records to form a structured set of attribute resource records.

[0108] When a new top-level domain needs to be added, the system will generate a new top-level domain mirror zone management command. The master server will respond to the new top-level domain mirror zone management command by automatically creating a member node corresponding to the new top-level domain at the end of the DNS directory zone. This member node exists as a direct subdomain of the DNS directory zone and is used to identify the newly added top-level domain.

[0109] Configure a PTR resource record on the newly created member node that points to the new top-level domain name, thus mapping the node to the new top-level domain. Simultaneously, increment the current maximum node label value by one, and then use the incremented value as the node label value for the newly created member node.

[0110] After the member zones of the newly added top-level domain are constructed, the sequence number field in the SOA record of the DNS directory zone is incremented, i.e., the current sequence number field is incremented by one. This sequence number field is used to identify zone update changes, triggering the secondary server to initiate zone transfer synchronization.

[0111] When a specified top-level domain needs to be deleted, the system will generate a delete top-level domain mirror zone management command. The master server will respond to the delete top-level domain mirror zone management command by first locating the member node where the specified top-level domain is located in the DNS directory zone, and then automatically deleting the corresponding PTR record and its attribute resource record from the DNS directory zone master file.

[0112] After deleting a member zone of a specified top-level domain, the sequence number field in the SOA record within the DNS directory zone is incremented, i.e., the current sequence number field is incremented by one. This sequence number field is used to identify zone update changes, triggering the secondary server to initiate zone transfer synchronization.

[0113] The secondary server periodically queries the sequence number field of the SOA record in the DNS directory zone on the primary server using the DNS zone transfer protocol. When the primary server updates its DNS directory zone, it also updates the sequence number field of the SOA record synchronously. The secondary server determines whether an update has occurred by comparing the sequence number field of the SOA record in its locally stored DNS directory zone with the latest sequence number field on the primary server.

[0114] When the secondary server detects an increase in the latest sequence number field on the primary server, it determines that the zone list has been updated and synchronously updates its local sequence number field. At this time, the secondary server automatically triggers the zone transfer process and retrieves the updated complete DNS directory zone data from the primary server through the DNS zone transfer protocol.

[0115] After receiving the updated data, the secondary server parses the PTR record set of the member nodes. If it finds that a certain top-level domain does not exist locally, it determines that the top-level domain is a newly added top-level domain and immediately sends a full zone transfer request for the newly added top-level domain to the primary server to obtain its full resource records.

[0116] After successfully receiving and applying all resource records of the newly added top-level domain via the DNS zone transfer protocol, the secondary server adds the newly added top-level domain and all its resource records to the end of its local DNS directory zone.

[0117] Alternatively, after receiving the update data, the secondary server resolves the PTR record set of the member nodes. If it finds that the PTR record of a certain top-level domain that exists locally is missing in the update data, it determines that the specified top-level domain has been deleted. At this time, the secondary server automatically removes the specified top-level domain from the local DNS directory zone and stops providing mirror domain name services for the specified top-level domain.

[0118] The top-level domain mirror zone management device provided in this application is described below. The top-level domain mirror zone management device described below can be referred to in correspondence with the top-level domain mirror zone management method described above.

[0119] Figure 9 This is one of the structural schematic diagrams of the top-level domain mirror zone management device provided in this application. For example... Figure 9 As shown, the top-level domain mirror zone management device is deployed on the master server and includes a building module 910 and a data synchronization module 920. Module 910 is used to construct DNS directory zones for domain name resolution services; the DNS directory zones are a list of zones used to centrally manage multiple top-level domains that need to provide mirror services. The data synchronization module 920 is used to respond to a data synchronization request sent by the secondary server and synchronize the DNS directory zone to the secondary server via the DNS zone transfer protocol.

[0120] In one embodiment, the building module 910 is further configured to: Generate zone names for DNS directory zones based on invalid domain names in the reserved domain name space; Configure the originating authority record and domain name server record in the DNS directory zone; Configure a resource record in the DNS directory zone that identifies the structure version number of the DNS directory zone; In the direct subdomains of the DNS directory zone, create member nodes corresponding to each top-level domain, and configure pointer records pointing to the corresponding top-level domains on the member nodes; Each member node is assigned an ordinal number by an incrementing integer to obtain the node label value of each member node.

[0121] In one embodiment, the building module 910 is further configured to: Based on the classification characteristics of each target top-level domain, the target top-level domains are grouped to obtain the grouping attribute information of each target top-level domain; the classification characteristics include the domain name type, stability characteristics and functional characteristics defined by the Internet Assigned Numbers Authority (IANA); By storing the grouping attribute information in the form of text records into the category identifier domain name of the corresponding target member node, the attribute resource records of each target member node are obtained.

[0122] In one embodiment, the top-level domain mirror zone management device is further configured to: In response to the instruction to add a new top-level domain mirror zone, a member node corresponding to the new top-level domain is created at the end of the DNS directory zone, and a pointer record pointing to the new top-level domain is configured on the member node; The node label value of the member node is obtained by incrementing the current maximum node label value. The serial number field in the current initial authorization agency record is incremented to update the serial number field.

[0123] In one embodiment, the top-level domain mirror zone management device is further configured to: In response to the management instruction to delete a top-level domain mirror zone, delete the member node corresponding to the specified top-level domain in the DNS directory zone; The serial number field in the current initial authorization agency record is incremented to update the serial number field.

[0124] Figure 10 This is the second schematic diagram of the top-level domain mirror zone management device provided in this application. Figure 10 As shown, the top-level domain mirror zone management device is deployed on the secondary server and includes a request sending module 1010 and a data synchronization module 1020. The request sending module 1010 is used to send data synchronization requests to the master server; The data synchronization module 1020 is used to receive the DNS directory zone sent by the master server via the DNS zone transfer protocol and update the DNS directory zone to the local machine; the DNS directory zone is a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services.

[0125] In one embodiment, the top-level domain mirror zone management device is further configured to: When it is detected that the sequence number field in the initial authoritative authority record of the DNS directory zone on the master server increases, the updated DNS directory zone sent by the master server is received through the DNS zone transport protocol, and the sequence number field in the updated DNS directory zone is synchronized. If a new top-level domain is detected in the updated DNS directory zone, a full zone transfer request for the new top-level domain is sent to the master server. The system receives the full resource records of the newly added top-level domain from the master server via the DNS zone transport protocol. Add the newly added top-level domain and its full resource records to the end of the local DNS directory zone.

[0126] In one embodiment, the top-level domain mirror zone management device is further configured to: When it is detected that the sequence number field in the initial authoritative authority record of the DNS directory zone on the master server increases, the updated DNS directory zone sent by the master server is received through the DNS zone transport protocol, and the sequence number field in the updated DNS directory zone is synchronized. If it is detected that a specified top-level domain has been deleted from the updated DNS directory zone, then the specified top-level domain is removed from the local DNS directory zone.

[0127] The following describes the top-level domain mirror zone management system provided in this application. The top-level domain mirror zone management system described below corresponds to the top-level domain mirror zone management method described above. This application provides a top-level domain mirror zone management system, which includes: a secondary server and a primary server; The master server is used to: construct DNS directory zones for domain name resolution services; the DNS directory zones are a list of zones used to centrally manage multiple top-level domains that need to provide mirror services. The auxiliary server is used to: send data synchronization requests to the master server; The primary server is configured to: respond to the data synchronization request sent by the secondary server, and synchronize the DNS directory zone to the secondary server via the DNS zone transfer protocol; The auxiliary server is used to: receive the DNS directory zone sent by the primary server via the DNS zone transfer protocol, and update the DNS directory zone in its local machine.

[0128] Figure 11 This is a schematic diagram of the structure of the electronic device provided in this application, such as... Figure 11As shown, the electronic device may include: a processor 1110, a communications interface 1120, a memory 1130, and a communication bus 1140, wherein the processor 1110, the communications interface 1120, and the memory 1130 communicate with each other via the communication bus 1140. The processor 1110 can invoke logical instructions in the memory 1130 to execute a top-level domain mirroring zone management method. This method includes: constructing a DNS directory zone for domain name resolution services; the DNS directory zone is a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services; responding to a data synchronization request sent by a secondary server, synchronizing the DNS directory zone to the secondary server via the DNS zone transfer protocol; or, sending a data synchronization request to the primary server; receiving the DNS directory zone sent by the primary server via the DNS zone transfer protocol, and updating the DNS directory zone locally; the DNS directory zone is a list of zones used to centrally manage multiple top-level domains that need to provide mirroring services.

[0129] Furthermore, the logical instructions in the aforementioned memory 1130 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0130] On the other hand, this application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer can execute the top-level domain mirror zone management method provided in the above embodiments. The method includes: constructing a DNS directory zone for Domain Name Resolution Service; the DNS directory zone is a list of zones for centrally managing multiple top-level domains that need to provide mirror services; responding to a data synchronization request sent by a secondary server, synchronizing the DNS directory zone to the secondary server via the DNS Zone Transfer Protocol; or, sending a data synchronization request to a primary server; receiving the DNS directory zone sent by the primary server via the DNS Zone Transfer Protocol, and updating the DNS directory zone locally; the DNS directory zone is a list of zones for centrally managing multiple top-level domains that need to provide mirror services.

[0131] Furthermore, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the top-level domain mirror zone management method provided in the above embodiments. The method includes: constructing a DNS directory zone for Domain Name Resolution Service; the DNS directory zone is a list of zones for centrally managing multiple top-level domains that need to provide mirror services; synchronizing the DNS directory zone to the secondary server via the DNS Zone Transfer Protocol in response to a data synchronization request sent by the secondary server; or sending a data synchronization request to the primary server; receiving the DNS directory zone sent by the primary server via the DNS Zone Transfer Protocol, and updating the DNS directory zone locally; the DNS directory zone is a list of zones for centrally managing multiple top-level domains that need to provide mirror services.

[0132] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0133] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0134] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for managing a top-level domain mirror region, characterized by, The top-level domain mirror area management method applied to a primary server comprises: constructing a domain name resolution service DNS directory area; the DNS directory area is an area list for centrally managing a plurality of top-level domains requiring mirror service provision; in response to a data synchronization request sent by a secondary server, synchronizing the DNS directory area to the secondary server through a DNS area transmission protocol.

2. The top-level domain mirror region management method of claim 1, wherein, The DNS directory area is constructed by: generating a region name of the DNS directory area based on invalid domain names under a reserved domain name space; configuring a starting authority record and a domain name server record in the DNS directory area; configuring a resource record in the DNS directory area for identifying a structure version number of the DNS directory area; creating member nodes corresponding to the top-level domains in a direct sub-domain of the DNS directory area, and configuring pointer records pointing to the corresponding top-level domains on the member nodes; sequentially numbering the member nodes in ascending integers to obtain node label values of the member nodes.

3. The top-level domain mirror region management method of claim 2, wherein, After the DNS directory area is constructed, the method further comprises: grouping the target top-level domains according to classification characteristics of the target top-level domains to obtain grouping attribute information of the target top-level domains; the classification characteristics include domain name types, stability characteristics and functional characteristics defined by an Internet Digital Allocation Agency IANA; storing the grouping attribute information in a classification identification domain name of a corresponding target member node in a text record form to obtain attribute resource records of the target member nodes.

4. The top-level domain mirror region management method of claim 2, wherein, The top-level domain mirror area management method further comprises: in response to a new top-level domain mirror area management instruction, creating a member node corresponding to a new top-level domain at the end of the DNS directory area, and configuring a pointer record pointing to the new top-level domain on the member node; incrementing a current maximum node label value to obtain a node label value of the member node; incrementing a sequence number field in the starting authority record to update the sequence number field.

5. The top-level domain mirror region management method of claim 2, wherein, The top-level domain mirror area management method further comprises: in response to a top-level domain mirror area deletion management instruction, deleting a member node corresponding to a specified top-level domain in the DNS directory area; incrementing a sequence number field in the starting authority record to update the sequence number field.

6. A method for managing a top-level domain mirror region, characterized by, The top-level domain mirror area management method applied to a secondary server comprises: sending a data synchronization request to a primary server; receiving a DNS directory area sent by the primary server through a DNS area transmission protocol, and updating the DNS directory area in a local; the DNS directory area is an area list for centrally managing a plurality of top-level domains requiring mirror service provision.

7. The top-level domain mirror region management method of claim 6, wherein, The top-level domain mirror area management method further comprises: When a sequence number field in a starting authority record of the DNS directory region on the master server is detected to increase, an updated DNS directory region sent by the master server is received through the DNS region transmission protocol, and the sequence number field in the updated DNS directory region is synchronized; If a new top-level domain is detected in the updated DNS directory region, a full-region transmission request for the new top-level domain is sent to the master server; The full-resource record of the new top-level domain sent by the master server is received through the DNS region transmission protocol; The new top-level domain and the full-resource record thereof are added to the end of the local DNS directory region.

8. The top-level domain mirror region management method of claim 6, wherein, The top-level domain mirroring region management method further includes: When a sequence number field in a starting authority record of the DNS directory region on the master server is detected to increase, an updated DNS directory region sent by the master server is received through the DNS region transmission protocol, and the sequence number field in the updated DNS directory region is synchronized; If a specified top-level domain is detected to be deleted in the updated DNS directory region, the specified top-level domain is removed from the local DNS directory region.

9. A top-level domain mirror region management apparatus characterized by comprising: The top-level domain mirroring region management apparatus deployed on the master server includes: A construction module configured to construct a domain name resolution service DNS directory region; the DNS directory region is a region list for centrally managing a plurality of top-level domains requiring to provide mirroring services; A data synchronization module configured to, in response to a data synchronization request sent by a secondary server, synchronize the DNS directory region to the secondary server through a DNS region transmission protocol.

10. A top-level domain mirror region management apparatus characterized by comprising: The top-level domain mirroring region management apparatus deployed on the secondary server includes: A request sending module configured to send a data synchronization request to a master server; A data synchronization module configured to receive a DNS directory region sent by the master server through a DNS region transmission protocol, and update the DNS directory region in the local; the DNS directory region is a region list for centrally managing a plurality of top-level domains requiring to provide mirroring services.

11. A top-level domain mirror region management system, characterized by, The top-level domain mirroring region management system includes a master server and a secondary server; The master server is configured to construct a domain name resolution service DNS directory region; the DNS directory region is a region list for centrally managing a plurality of top-level domains requiring to provide mirroring services; The secondary server is configured to send a data synchronization request to the master server; The master server is configured to, in response to the data synchronization request sent by the secondary server, synchronize the DNS directory region to the secondary server through a DNS region transmission protocol; The secondary server is configured to receive the DNS directory region sent by the master server through the DNS region transmission protocol, and update the DNS directory region in the local.

12. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, The processor implements the steps of the top-level domain mirroring region management method according to any one of claims 1 to 8 when executing the computer program.

13. A non-transitory computer-readable storage medium having stored thereon a computer program, wherein The computer program, when executed by a processor, implements the steps of the top-level domain mirror region management method according to any one of claims 1 to 8.

14. A computer program product comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the steps of the top-level domain mirror region management method according to any one of claims 1 to 8.

Images