CN117614933A - Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment - Google Patents

Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment Download PDF

Info

Publication number
CN117614933A
CN117614933A CN202311583057.4A CN202311583057A CN117614933A CN 117614933 A CN117614933 A CN 117614933A CN 202311583057 A CN202311583057 A CN 202311583057A CN 117614933 A CN117614933 A CN 117614933A
Authority
CN
China
Prior art keywords
dns
data
edge
domain name
deployed
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311583057.4A
Other languages
Chinese (zh)
Inventor
欧阳康
沈朝华
李瑚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Runxin Commercial Investment Shenzhen Co ltd
Original Assignee
Runxin Commercial Investment Shenzhen Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Runxin Commercial Investment Shenzhen Co ltd filed Critical Runxin Commercial Investment Shenzhen Co ltd
Priority to CN202311583057.4A priority Critical patent/CN117614933A/en
Publication of CN117614933A publication Critical patent/CN117614933A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to a cloud-edge collaborative distributed domain name resolution system, a domain name resolution method and equipment. The system comprises a DNS database deployed at a cloud end, an edge data center server and an edge DNS server which are deployed at each edge data center; a DNS database for storing DNS data of the whole system; the edge data center server is used for sending a DNS query request to edge DNS servers deployed in the same edge data center according to the received DNS request; and the edge DNS server is used for synchronizing the DNS data in the specific range stored in the DNS database to the local, generating local DNS analysis record data, acquiring matched DNS data from the local DNS analysis record data as target DNS data when a DNS query request is received, and responding to the received DNS query request based on the target DNS data. The method and the device can simultaneously solve the problem of difficult DNS data maintenance and the problem of low resolution speed and bandwidth occupation when performing cross-data center recursive query.

Description

Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment
Technical Field
The application relates to the technical field of domain name resolution, in particular to a cloud-edge collaborative distributed domain name resolution system, a domain name resolution method and equipment.
Background
In some project development and operational scenarios, multiple operating environments are typically involved, with the computing resources of these operating environments being independent of each other and even distributed across different data centers. For DNS (Domain Name System ) management of multiple data centers, most of the current industry is realized by means of independent maintenance or recursive query, the former is used for realizing recursive-free query (or referred to as iterative query) of intranet resolution by independently maintaining DNS data, but unified management across data centers cannot be realized; the latter can realize unified management of DNS data, but has slow storage and analysis speed when performing cross-data center recursion inquiry, so that the inquiry efficiency is reduced, and meanwhile, when the inquiry concurrency is large, certain bandwidth occupation is brought to a private line network crossing the data center.
Disclosure of Invention
Aiming at the defects or shortcomings, the embodiment of the application provides a cloud-edge collaborative distributed domain name resolution system, a cloud-edge collaborative distributed domain name resolution method, cloud-edge collaborative distributed domain name resolution equipment and a cloud-edge collaborative distributed domain name storage medium.
According to a first aspect, the present application provides a cloud-edge collaborative distributed domain name resolution system, in some embodiments, the system includes a DNS database deployed in a cloud, an edge data center server and an edge DNS server deployed in each edge data center;
a DNS database for storing DNS data of the whole system;
the edge data center servers are deployed in any edge data center and are used for sending DNS query requests to the edge DNS servers deployed in the same edge data center according to the received DNS requests;
and the edge DNS server is arranged in any edge data center and is used for synchronizing the DNS data in a specific range stored in the DNS database to the local, generating local DNS analysis record data, acquiring matched DNS data from the local DNS analysis record data as target DNS data when a DNS query request is received, and responding to the received DNS query request based on the target DNS data.
In some embodiments, the DNS databases are deployed at one or more cloud data centers, or are deployed independent of the cloud data centers.
In some embodiments, edge DNS servers deployed at any edge data center are further configured to request DNS data of a specific scope from a DNS database according to the data synchronization configuration information.
In some embodiments, edge DNS servers deployed at any edge data center are provided with a data synchronization service and a domain name resolution service;
the data synchronization service is used for synchronizing the DNS data in a specific range stored in the DNS database to the local and serializing the DNS data into Zone data;
and the domain name resolution service is used for resolving the Zone data and generating local DNS resolution record data.
In some embodiments, the DNS database is further configured to perform a corresponding DNS data maintenance operation in response to receiving the DNS data maintenance instruction.
In some embodiments, the categories of DNS data maintenance instructions include DNS data add instructions, DNS data delete instructions, and DNS data modify instructions;
the DNS data maintenance operation corresponding to the DNS data new instruction comprises the step of adding corresponding DNS data according to the received DNS data new instruction;
the DNS data maintenance operation corresponding to the DNS data deletion instruction comprises deleting corresponding DNS data according to the received DNS data deletion instruction;
the DNS data maintenance operations corresponding to the DNS data modifying instructions include modifying the corresponding DNS data according to the received DNS data modifying instructions.
In some embodiments, the DNS database is further configured to determine a target edge DNS server associated with the DNS data maintenance instructions, and send a data maintenance notification to the target edge DNS server;
the edge DNS server is deployed in any edge data center and is also used for maintaining and processing the local DNS analysis record data according to the received data maintenance notification.
The present application provides a domain name resolution method according to a second aspect, in some embodiments, the method is applied to an edge DNS server, the edge DNS server being deployed in an edge data center; the method comprises the following steps:
synchronizing DNS data in a specific range stored in a DNS database deployed in the cloud to the local to generate local DNS analysis record data; the DNS database stores DNS data of the whole system;
when a DNS query request sent by an edge data center server deployed in an edge data center is received, the matched DNS data is obtained from the local DNS analysis record data to serve as target DNS data, and the DNS query request is responded based on the target DNS data.
According to a third aspect, the present application provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the domain name resolution method provided in any of the embodiments described above when the computer program is executed by the processor.
According to a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the domain name resolution method provided in any of the embodiments described above.
In the above embodiment of the present application, a cloud-edge collaborative concept is adopted, a unified DNS database is maintained at the cloud end, and edge DNS servers are deployed at each edge data center, after implementing the scheme of the present application, a user may manage an interaction entry through one DNS database, so as to implement unified management of DNS data, meanwhile, because each edge data center is deployed with an independent edge DNS server, the edge DNS servers may synchronize DNS data in a specific range in the DNS database to a local place and generate local DNS resolution record data, after receiving a DNS request, the edge data center servers deployed at each edge data center may send a DNS query request to the edge DNS servers deployed at the same edge data center, and the edge DNS servers may utilize the local DNS resolution record data to obtain matched DNS data, and respond to the DNS request of the edge data center servers through the matched DNS data, where DNS queries of the edge DNS servers are only completed inside the data center, and the occupied bandwidth is very small when performing DNS data synchronization operations, and the DNS queries of the edge data center are not affected, so that the problem of difficult to resolve the data query speed can be solved, and the problem of the data query speed is difficult to be solved.
Drawings
Fig. 1 is a schematic diagram illustrating a composition of a cloud-edge collaborative distributed domain name resolution system provided in accordance with one or more embodiments of the present application;
FIG. 2 is a flow diagram of a domain name resolution method provided in accordance with one or more embodiments of the present application;
FIG. 3 is a block diagram illustrating a domain name resolution device provided in accordance with one or more embodiments of the present application;
FIG. 4 is an internal block diagram of a computer device provided in accordance with one or more embodiments of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings. It should be understood that the described embodiments are merely some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
In the description of this application, it should be understood that the terms "first," "second," "third," and the like are used merely to distinguish between similar objects and are not necessarily used to describe a particular order or sequence, nor should they be construed to indicate or imply relative importance. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art as the case may be. Furthermore, in the description of the present application, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
In order to facilitate understanding of the technical solutions provided in the present application, some technical terms mentioned in the background art are described below.
With respect to recursive queries, a recursive query is a DNS resolution process that is typically used to query DNS data between different data centers. In general, the processing of a recursive query may be as follows:
1. the client first sends a DNS request to the Local domain name Server (Local DNS Server), which contains the domain name to be queried.
2. After receiving the request, the local domain name server firstly checks its own cache, and detects whether the resolution result of the domain name is stored in the cache. If the resolution result of the domain name exists, the resolution result of the domain name is directly returned to the client. If there is no resolution result of the domain name, the following operation is continued.
3. If the cache does not have the resolution result of the domain name, the local domain name server sends an iterative query request to the root domain name server. The root domain name server is a server responsible for managing top-level domain names (e.g.,. Com,. Cn, etc.).
4. After receiving the request, the root domain name Server returns the address of the corresponding top domain name Server (TLD Server) to the local domain name Server according to the top domain (e.g., com) of the domain name.
5. After receiving the address of the top domain name server, the local domain name server sends a next iteration query request to the top domain name server.
6. The top-level domain name server returns the address of the authoritative domain name server (Authoritative DNS Server) for the domain name to the local domain name server based on the request.
7. The local domain name server then sends the last iteration query request to the authoritative domain name server.
8. After receiving the request, the authoritative domain name server searches the IP address corresponding to the domain name in the DNS database, and returns the analysis result containing the IP address to the local domain name server.
9. The local domain name server returns the resolution result to the client and stores the resolution result in its own cache so as to be able to respond to the DNS request more quickly when it is received again.
With respect to recursion-free queries, which may also be referred to as iterative queries, which are also a DNS resolution process, are typically used to query DNS data between different DNS servers. The difference between the recursion-free query and the recursion-free query is that when the recursion-free query is performed, the local domain name server does not continuously send the query request to the upper server, but returns the query request to the client, the address of the next server is provided for the client, and the client automatically sends the query request according to the provided addresses until a complete analysis result is obtained. In general, the processing of a recursively free query can be as follows:
1. the client sends a DNS request to the local domain name server, the request containing the domain name to be queried.
2. After receiving the request, the local domain name server firstly checks its own cache, and detects whether the resolution result of the domain name is stored in the cache. If the resolution result of the domain name exists, the resolution result of the domain name is directly returned to the client. If there is no resolution result of the domain name, the following operation is continued.
3. If the resolution result of the domain name is not in the cache, the local domain name server sends a recursion-free query request to the root domain name server.
4. After receiving the request, the root domain name Server returns the address of the corresponding top domain name Server (TLD Server) to the local domain name Server according to the top domain (e.g. com) of the domain name.
5. The local domain name server provides the address of the top-level domain name server to the client.
6. And the client sends a query request to the top-level domain name server according to the provided address.
7. After receiving the inquiry request of the client, the top-level domain name server returns the address of the authoritative domain name server (Authoritative DNS Server) of the domain name to the client according to the request.
8. The client again sends a query request to the authoritative domain name server.
9. After receiving the request, the authoritative domain name server searches the IP address corresponding to the domain name in the DNS database, and returns the analysis result containing the IP address to the client.
10. After receiving the analysis result, the client side also sends the analysis result to the local domain name server.
11. The local domain name server stores the analysis result in a cache.
The application provides a cloud-edge collaborative distributed domain name resolution system, and the composition of the system can be shown in fig. 1, wherein the system comprises a unified DNS database deployed at a cloud end, an edge data center server and an edge DNS server deployed at each edge data center.
The DNS database is used for storing DNS data of the whole system;
the edge data center servers are deployed in any edge data center and are used for sending DNS query requests to the edge DNS servers deployed in the same edge data center according to the received DNS requests;
and the edge DNS server is arranged in any edge data center and is used for synchronizing the DNS data in a specific range stored in the DNS database to the local, generating local DNS analysis record data, acquiring matched DNS data from the local DNS analysis record data as target DNS data when a DNS query request is received, and responding to the received DNS query request based on the target DNS data.
Aiming at the defects or drawbacks of the prior art, the embodiment of the application adopts the idea of cloud edge collaboration, maintains a unified DNS database at the cloud end, deploys edge DNS servers at all edge data centers, and enables users to manage interaction entries through the DNS database so as to realize unified management of DNS data.
In some embodiments, the DNS database may be deployed in one cloud data center, or may be deployed in a disaster recovery manner in a plurality of cloud data centers, or may be deployed in a cloud independent from the cloud data centers.
In some embodiments, the user needs to set a local DNS server for the edge data center server deployed at each edge data center, that is, when the edge data center server receives an access request from a client, a DNS request for acquiring an IP address of a domain name to be accessed by the client is sent to the local DNS server. The address of the local DNS server is the address of the edge DNS server deployed in the same edge data center as the edge data center server.
Further, regarding the data stored in the DNS database, the stored data may be referred to as cloud DNS data, which refers to resolution data of the whole domain name system stored in the cloud, and may include domain names, resolution records, and other relevant information. Cloud DNS data is maintained uniformly by users (e.g., administrators of DNS data).
The edge DNS server is deployed in any edge data center and is also used for requesting DNS data in a specific range from the DNS database according to the data synchronization configuration information. The edge DNS servers in each edge data center only need to use part of the data in the cloud DNS data when performing DNS query operation, and a user can configure corresponding data synchronization configuration information for each edge DNS server in advance, where the data synchronization configuration information is used to specify a range of DNS data that needs to be synchronized from the cloud database for the edge DNS server, for example, specify which domain names of zones (Zone) need to be synchronized.
In some embodiments, the DNS database is further configured to perform a corresponding DNS data maintenance operation in response to receiving the DNS data maintenance instruction.
The types of the DNS data maintenance instructions comprise a DNS data new instruction, a DNS data deletion instruction and a DNS data modification instruction. Correspondingly, the DNS data maintenance operation corresponding to the DNS data new instruction comprises the step of adding corresponding DNS data according to the received DNS data new instruction; the DNS data maintenance operation corresponding to the DNS data deletion instruction comprises deleting corresponding DNS data according to the received DNS data deletion instruction; the DNS data maintenance operations corresponding to the DNS data modifying instructions include modifying the corresponding DNS data according to the received DNS data modifying instructions.
In some embodiments, the DNS database is further configured to determine a target edge DNS server associated with the DNS data maintenance instructions, and send a data maintenance notification to the target edge DNS server; correspondingly, the edge DNS server deployed in any edge data center is also used for maintaining the local DNS analysis record data according to the received data maintenance notification.
Wherein, according to the different kinds of the DNS data maintenance instructions, the data maintenance notification can be correspondingly classified into a DNS data addition notification, a DNS data deletion notification, and a DNS data modification notification. After receiving the data maintenance notification, the edge DNS server may perform corresponding maintenance processing, for example, adding DNS data, deleting or modifying existing DNS data, and updating local DNS resolution record data accordingly.
In some embodiments, edge DNS servers deployed at any edge data center are provided with a data synchronization service and a domain name resolution service; the data synchronization service is used for synchronizing the DNS data in a specific range stored in the DNS database to the local and serializing the DNS data into Zone data; and the domain name resolution service is used for resolving the Zone data and generating local DNS resolution record data.
In this embodiment, when the edge DNS server synchronizes DNS data from the DNS database, specifically, the data synchronization service synchronizes DNS data in a specific range from the DNS database and sequences the DNS data into Zone data conforming to RFC1035 specifications, then the domain name resolution service resolves the Zone data into local DNS resolution record data, and then when a DNS query request is received, the local DNS resolution record data is used to complete a related action of the DNS resolution query.
In this embodiment, the DNS data synchronization operation and the DNS query resolution operation implemented by the edge DNS server in the foregoing embodiments are split, and are implemented by the data synchronization service and the DNS resolution service in cooperation with each other, so that modularization and maintainability of a system can be improved, where when a certain service has a problem, the relevant service can be adjusted, and the normal operation of other services will not be greatly affected. Furthermore, the cloud DNS data is serialized into Zone data conforming to RFC1035 by using the data synchronization service, and the unification and compatibility of the data formats can be ensured.
Based on the same inventive concept, the application also provides a domain name resolution method. In some embodiments, the method is applied to the edge DNS server provided in the foregoing embodiments, where the edge DNS server is deployed in any one of the edge data centers, as shown in fig. 2, and the method includes the steps of:
s110: and synchronizing the DNS data in a specific range stored in the DNS database deployed in the cloud to the local to generate local DNS analysis record data. The DNS database stores DNS data of the entire system.
S120: when a DNS query request sent by an edge data center server deployed in an edge data center is received, the matched DNS data is obtained from the local DNS analysis record data to serve as target DNS data, and the DNS query request is responded based on the target DNS data.
In some embodiments, synchronizing DNS data of a particular scope stored in a DNS database deployed at a cloud to a local site, generating local DNS resolution record data, includes: synchronizing DNS data in a specific range stored in a DNS database to the local and serializing the DNS data into Zone data; and analyzing the Zone data to generate local DNS analysis record data.
In some embodiments, the above method further comprises: and carrying out maintenance processing on the local DNS analysis record data according to the received data maintenance notification.
For specific limitation of the domain name resolution method, reference may be made to the limitation of the cloud-edge collaborative distributed domain name resolution system hereinabove, and no further description is given here.
It should be noted that, regarding the steps included in the domain name resolution method provided in any of the above embodiments, the steps are not strictly limited to the order of execution unless explicitly described herein, and the steps may be executed in other orders. Moreover, at least some of these steps may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily performed in sequence, but may be performed alternately or alternately with at least a portion of other steps or sub-steps of other steps.
The application also provides a domain name resolution device for realizing the domain name resolution method. In some embodiments, as shown in fig. 3, the transport path determination device includes the following modules:
the data synchronization module 110 is configured to synchronize DNS data in a specific range stored in a DNS database deployed in the cloud to local, and generate local DNS resolution record data; the DNS database stores DNS data of the entire system.
The request response module 120 is configured to, when receiving a DNS query request sent by an edge data center server disposed in an edge data center, obtain, according to the local DNS resolution record data, matched DNS data as target DNS data, and respond to the DNS query request based on the target DNS data.
In some embodiments, the data synchronization module 110 is specifically configured to synchronize DNS data of a specific range stored in a DNS database deployed in a cloud to a local place, and generate local DNS resolution record data, including: synchronizing DNS data in a specific range stored in a DNS database to the local and serializing the DNS data into Zone data; and analyzing the Zone data to generate local DNS analysis record data.
In some embodiments, the apparatus further comprises a maintenance processing module. And the maintenance processing module is used for carrying out maintenance processing on the local DNS analysis record data according to the received data maintenance notification.
For specific limitations of the domain name resolution device, reference may be made to the above limitation of the domain name resolution method, and the description thereof will not be repeated here. The respective modules in the domain name resolution apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
The present application provides, in some embodiments, a computer device whose internal structural diagram may be as shown in fig. 4. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing data such as local DNS resolution record data, and the specific stored data can also be referred to as limitation in the above method embodiment. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a domain name resolution method.
Those skilled in the art will appreciate that the structures shown in FIG. 4 are block diagrams only and do not constitute a limitation of the computer device on which the present aspects apply, and that a particular computer device may include more or less components than those shown, or may combine some of the components, or have a different arrangement of components.
The present embodiment also provides a computer device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor can implement the steps of the domain name resolution method provided in any of the foregoing embodiments when executing the computer program.
In particular, the processor may implement the following steps when executing the computer program:
synchronizing DNS data in a specific range stored in a DNS database deployed in the cloud to the local to generate local DNS analysis record data; the DNS database stores DNS data of the whole system; when a DNS query request sent by an edge data center server deployed in an edge data center is received, the matched DNS data is obtained from the local DNS analysis record data to serve as target DNS data, and the DNS query request is responded based on the target DNS data.
In one embodiment, the processor executes the computer program to synchronize DNS data of a specific range stored in a DNS database deployed in the cloud to the local, and when generating local DNS resolution record data, further implements the following steps:
synchronizing DNS data in a specific range stored in a DNS database to the local and serializing the DNS data into Zone data; and analyzing the Zone data to generate local DNS analysis record data.
In one embodiment, the processor executes a computer program, further implementing the steps of:
and carrying out maintenance processing on the local DNS analysis record data according to the received data maintenance notification.
The present application also provides in some embodiments a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the domain name resolution method provided in any of the embodiments described above.
In particular, the computer program may, when executed by a processor, implement the steps of:
synchronizing DNS data in a specific range stored in a DNS database deployed in the cloud to the local to generate local DNS analysis record data; the DNS database stores DNS data of the whole system; when a DNS query request sent by an edge data center server deployed in an edge data center is received, the matched DNS data is obtained from the local DNS analysis record data to serve as target DNS data, and the DNS query request is responded based on the target DNS data.
In one embodiment, the computer program is executed by the processor to synchronize DNS data of a specific range stored in a DNS database deployed in the cloud to the local, and when generating local DNS resolution record data, further implement the following steps:
synchronizing DNS data in a specific range stored in a DNS database to the local and serializing the DNS data into Zone data; and analyzing the Zone data to generate local DNS analysis record data.
In one embodiment, the computer program is executed by a processor, further implementing the steps of:
and carrying out maintenance processing on the local DNS analysis record data according to the received data maintenance notification.
In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
Those skilled in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the method embodiments described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink), DRAM (SLDRAM), memory bus (Rambus), direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.

Claims (10)

1. The cloud-edge collaborative distributed domain name resolution system is characterized by comprising a DNS database deployed at a cloud end, an edge data center server and an edge DNS server deployed at each edge data center;
the DNS database is used for storing DNS data of the whole system;
the edge data center servers are deployed in any edge data center and are used for sending DNS query requests to the edge DNS servers deployed in the same edge data center according to the received DNS requests;
the edge DNS server is deployed in any edge data center and is used for synchronizing the DNS data in a specific range stored in the DNS database to the local, generating local DNS analysis record data, and when a DNS query request is received, acquiring matched DNS data from the local DNS analysis record data as target DNS data, and responding to the received DNS query request based on the target DNS data.
2. The system of claim 1, wherein the DNS database is deployed at one or more cloud data centers or is deployed independent of cloud data centers.
3. The system of claim 1, wherein edge DNS servers deployed at any edge data center are further configured to request DNS data for the specific range from the DNS database according to data synchronization configuration information.
4. The system of claim 1, wherein edge DNS servers deployed at either edge data center are provided with a data synchronization service and a domain name resolution service;
the data synchronization service is used for synchronizing the DNS data in a specific range stored in the DNS database to the local and serializing the DNS data into Zone data;
the domain name resolution service is used for resolving the Zone data and generating local DNS resolution record data.
5. The system of claim 1, wherein the DNS database is further configured to perform a corresponding DNS data maintenance operation in response to receiving a DNS data maintenance command.
6. The system of claim 5, wherein the categories of DNS data maintenance instructions include DNS data add instructions, DNS data delete instructions, and DNS data modify instructions;
the DNS data maintenance operation corresponding to the DNS data new instruction comprises the step of adding corresponding DNS data according to the received DNS data new instruction;
the DNS data maintenance operation corresponding to the DNS data deletion instruction comprises deleting corresponding DNS data according to the received DNS data deletion instruction;
the DNS data maintenance operations corresponding to the DNS data modifying instructions include modifying the corresponding DNS data according to the received DNS data modifying instructions.
7. The system of claim 6, wherein the DNS database is further configured to determine a target edge DNS server associated with the DNS data maintenance instructions, and send a data maintenance notification to the target edge DNS server;
the edge DNS server is deployed in any edge data center and is also used for maintaining and processing the local DNS analysis record data according to the received data maintenance notification.
8. The domain name resolution method is characterized by being applied to an edge DNS server, wherein the edge DNS server is deployed in an edge data center; the method comprises the following steps:
synchronizing DNS data in a specific range stored in a DNS database deployed in the cloud to the local to generate local DNS analysis record data; the DNS database stores DNS data of the whole system;
when a DNS query request sent by an edge data center server deployed in the edge data center is received, acquiring matched DNS data from the local DNS analysis record data as target DNS data, and responding to the DNS query request based on the target DNS data.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of claim 8 when the computer program is executed by the processor.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of claim 8.
CN202311583057.4A 2023-11-24 2023-11-24 Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment Pending CN117614933A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311583057.4A CN117614933A (en) 2023-11-24 2023-11-24 Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311583057.4A CN117614933A (en) 2023-11-24 2023-11-24 Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment

Publications (1)

Publication Number Publication Date
CN117614933A true CN117614933A (en) 2024-02-27

Family

ID=89957436

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311583057.4A Pending CN117614933A (en) 2023-11-24 2023-11-24 Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment

Country Status (1)

Country Link
CN (1) CN117614933A (en)

Similar Documents

Publication Publication Date Title
US11068449B2 (en) Data migration method, apparatus, and storage medium
RU2425449C2 (en) Tracking state transition data in order to aid computer network security
US8583810B2 (en) Session affinity cache and manager
EP0955761A1 (en) Network directory access mechanism
CN111193744B (en) Firewall strategy inquiry and elastic expansion method, system, equipment and storage medium
CN103685590B (en) Obtain the method and system of IP address
CN111586201A (en) Domain name resolution system, method, device and storage medium
CN114040020A (en) Cross-cluster service calling method and system
CN108595280A (en) Method for interface adaptation, device, computer equipment and storage medium
CN113760461B (en) Version upgrading method and computer readable storage medium
CN110290163B (en) Data processing method and device
CN105812503A (en) Root server address update method and recursive server
CN108804711A (en) A kind of method, apparatus and computer readable storage medium of data processing
CN112532763A (en) Container operation data synchronization method and device
CN117614933A (en) Cloud-edge collaborative distributed domain name resolution system, domain name resolution method and equipment
CN114338502B (en) Gateway data processing method, device, equipment and storage medium
CN115022307A (en) File downloading method and device, storage medium and electronic equipment
CN111866197A (en) Domain name resolution method and system
CN112804313B (en) Data synchronization method, device, equipment and medium based on cross-domain edge node
CN101626365A (en) Directory server and system and method for realizing LDAP extended operation
CN113037885A (en) View matching method, DNS server and computer readable storage medium
CN107959674B (en) Gateway equipment, and method and system for controlling access to third-party LDAP server user
CN112187965B (en) Domain name resolution method and system for hiding manufacturer information
CN107517280B (en) Domain name resolution method and device
CN115242595B (en) Network device discovery method, device, electronic device and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination