Domain name configuration and configuration file acquisition method and device, equipment and storage medium

Abstract

The present disclosure relates to a domain name configuration method and a configuration file acquisition method, device, equipment and storage medium. The domain name configuration method comprises: generating a configuration file corresponding to each domain name for each domain name of a customer website served by each edge node in a content distribution network, wherein the configuration file comprises a service configuration file; determining a shared domain name and a shared domain name based on the service configuration file, wherein the shared domain name and the shared domain name share the same service configuration file; determining a first configuration file corresponding to the shared domain name and a second configuration file corresponding to the shared domain name; and downloading the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name to the edge node to enable the edge node to be configured. In the present disclosure, the shared domain name and the shared domain name share the same service configuration file, the same domain name shares the same service configuration file, the complexity of customer service configuration is reduced, and a large number of repeated domain name configurations are eliminated.

Description

Technical Field

[0001] This disclosure relates to the field of information processing technology, and in particular to a method, apparatus, device and storage medium for domain name configuration and configuration file acquisition. Background Technology

[0002] A Content Delivery Network (CDN) is a new type of network architecture. CDN networks rely on edge nodes (i.e., edge servers) deployed in various locations, and through the load balancing, content distribution, and scheduling functions of the central server, they enable users to obtain the content they need from the nearest location, reducing network congestion and improving user access response speed and hit rate.

[0003] During the operation of a CDN network, it is necessary to configure and manage the domain names of the clients served by each edge node. This includes configurations such as CDN origin pull configuration, caching policy configuration, and log recording and return configuration to ensure efficient operation of each edge node. Existing domain name configuration methods typically rely on configuration file distribution. This involves distributing pre-written configuration files to each edge node for configuration. For example, edge nodes may retrieve the configuration file from a server storing the file using P2P (peer-to-peer) or FTP (File Transfer Protocol) technology, and then use the configuration information within the configuration file for further configuration.

[0004] As users expand their CDN product offerings, clients often use different domains for different business lines to differentiate them into more granular product lines. However, for ease of maintenance, the CDN logic employs a completely consistent business model. In most cases, each time a client adds a new service domain, it needs to copy the existing domain configuration as the new domain's configuration file. This process is tedious and error-prone. For the CDN, even if the domain business configuration files are completely identical under the same user ID, the CDN still needs to maintain the full configuration for each domain, which impacts CDN system performance to some extent. For example, it affects domain loading efficiency and memory usage. Summary of the Invention

[0005] This disclosure provides a method, apparatus, device, and storage medium for domain name configuration and configuration file acquisition, enabling the same domain name to share the same business configuration file, reducing the complexity of customer business configuration, eliminating a large number of duplicate domain name configurations, and improving CDN domain name configuration loading efficiency and system stability.

[0006] In a first aspect, embodiments of this disclosure provide a domain name configuration method, the method being applied to a central server, comprising:

[0007] For each domain name of the customer website served by each edge node in the content delivery network, a configuration file corresponding to the domain name is generated, and the configuration file includes a business configuration file.

[0008] The shared domain name and the shared domain name are determined based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file;

[0009] Determine the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name;

[0010] The first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name are distributed to the edge nodes so that the edge nodes can be configured.

[0011] In one implementation, determining the shared domain name and the domain name to be shared based on the business configuration file includes:

[0012] For domains with identical business configuration files, arbitrarily select one of them as the shared domain, and use the remaining domains with identical business configuration files as the shared domains.

[0013] In one implementation, determining the first configuration file corresponding to the shared domain name includes:

[0014] The business configuration file and the certificate configuration file corresponding to the shared domain name are used as the first configuration file of the shared domain name.

[0015] In one implementation, determining the second configuration file corresponding to the shared domain name includes:

[0016] Establish a sharing relationship between the shared domain name and the shared domain name;

[0017] The shared relationship and the certificate configuration file corresponding to the shared domain name are used as the second configuration file corresponding to the shared domain name.

[0018] In one embodiment, the method further includes:

[0019] After terminating the sharing relationship between the shared domain name and the shared domain name, determine whether the change in the business configuration file exceeds the change threshold.

[0020] If the limit is exceeded, delete all configuration files for the shared domain name and publish the shared domain name as a new domain name;

[0021] If the limit is not exceeded, the business configuration file corresponding to the shared domain name is copied to the second configuration file, and the second configuration file is re-distributed to the edge node.

[0022] Secondly, embodiments of this disclosure provide a configuration file acquisition method, the method being applied to an edge server, comprising:

[0023] Receive request information sent by a client, wherein the request information carries a domain name corresponding to the client;

[0024] If the domain name is a shared domain name, then determine the shared domain name corresponding to the shared domain name;

[0025] Obtain the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name.

[0026] In one embodiment, the method further includes:

[0027] If the domain name is a shared domain name, then obtain the first configuration file corresponding to the shared domain name, wherein the first configuration file includes the business configuration file corresponding to the shared domain name and the certificate configuration file corresponding to the shared domain name.

[0028] In one implementation, if the domain name is a shared domain name, then determining the shared domain name corresponding to the shared domain name includes:

[0029] If the domain name is a shared domain name, read the second configuration file corresponding to the shared domain name, wherein the second configuration file includes: the sharing relationship between the shared domain name and the shared domain name;

[0030] The shared domain name corresponding to the shared domain name is determined based on the sharing relationship.

[0031] In one embodiment, the second configuration file further includes: a certificate configuration file; the method further includes:

[0032] Use the certificate configuration file in the second configuration file as the certificate configuration file for the shared domain name.

[0033] Thirdly, embodiments of this disclosure provide a domain name configuration device, the device being configured on a central server, comprising:

[0034] The configuration file generation module is used to generate a configuration file corresponding to each domain name of the customer websites served by each edge node in the CDN network. The configuration file includes a business configuration file.

[0035] The domain name category determination module is used to determine the shared domain name and the shared domain name based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file;

[0036] The configuration file determination module is used to determine the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name;

[0037] The configuration file distribution module is used to distribute the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name to the edge nodes so that the edge nodes can be configured.

[0038] Fourthly, embodiments of this disclosure provide a configuration file acquisition device, the device being configured on an edge server, comprising:

[0039] An information receiving module is used to receive request information sent by a client, wherein the request information carries a domain name corresponding to the client;

[0040] The domain name category determination module is used to determine the shared domain name corresponding to the shared domain name if the domain name is a shared domain name;

[0041] The configuration file acquisition module is used to acquire the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name.

[0042] Fifthly, embodiments of this disclosure provide an electronic device, including:

[0043] Memory;

[0044] Processor; and

[0045] Computer programs;

[0046] The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in any one of the first or second aspects.

[0047] A sixth aspect is a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method as described in any one of the first or second aspects.

[0048] This disclosure provides a domain name configuration and configuration file acquisition method, apparatus, device, and storage medium. The domain name configuration method includes: generating a configuration file corresponding to each domain name for the domain names of customer websites served by each edge node in a content delivery network (CDN). The configuration file includes a business configuration file. Based on the business configuration file, a shared domain name and a shared domain name are determined, wherein the shared domain name and the shared domain name share the same business configuration file. A first configuration file corresponding to the shared domain name and a second configuration file corresponding to the shared domain name are determined. The first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name are distributed to the edge nodes for configuration. The technical solution provided by this disclosure allows the shared domain name and the shared domain name to share the same business configuration file, reducing the complexity of customer business configuration, eliminating a large number of duplicate domain name configurations, and improving the CDN domain name configuration loading efficiency and system stability. Attached Figure Description

[0049] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0050] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 A flowchart of the domain name configuration method provided in this embodiment of the disclosure;

[0052] Figure 2 A flowchart illustrating the configuration file acquisition method provided in this embodiment of the disclosure;

[0053] Figure 3 This is a schematic diagram of the data back-to-origin structure for a shared domain name provided in an embodiment of this disclosure;

[0054] Figure 4 This is a schematic diagram of the domain name configuration device provided in an embodiment of the present disclosure;

[0055] Figure 5 A schematic diagram of the configuration file acquisition device provided in the embodiments of this disclosure;

[0056] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0057] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0058] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0059] Existing CDN configuration methods and configuration file distribution essentially fall under the category of internet file transfer. With the development of technology, several popular solutions today include P2P (peer-to-peer) technology and FTP (File Transfer Protocol) technology.

[0060] The current CDN domain configuration file maintenance method involves maintaining a full configuration for each domain. When a user changes a domain's configuration information, all corresponding domains require batch configuration file changes, which is prone to errors and omissions. Furthermore, when a user adds a new domain, if the requirements are the same as some existing domains, the user no longer needs to provide a complete requirements document; instead, existing domain configuration files must be copied, which is tedious and error-prone.

[0061] Since CDNs maintain full configurations for all accelerated domains, this can negatively impact the stability of the CDN system to some extent. To address this issue, this disclosure provides a domain configuration method and a configuration file acquisition method, enabling the same domain to share the same business configuration file. This reduces the complexity of customer business configurations, eliminates numerous duplicate domain configurations, and improves CDN domain configuration loading efficiency and system stability.

[0062] In one embodiment, this disclosure provides a domain name configuration method. Figure 1 This is a flowchart of a domain name configuration method provided in an embodiment of the present disclosure. The domain name configuration method is executed by a domain name configuration device and is applied to a central server.

[0063] like Figure 1 As shown, the domain name configuration method provided in this embodiment mainly includes the following steps:

[0064] S101. For the domain names of customer websites served by each edge node in the content delivery network, generate a configuration file corresponding to each domain name, the configuration file including a business configuration file.

[0065] It is understood that different edge nodes in a Content Delivery Network (CDN) can serve different customer websites, and different customer websites can usually correspond to different domain names. Therefore, in this embodiment of the disclosure, the central server can generate corresponding configuration files for different domain names of the customer websites served by each edge node.

[0066] In this context, edge nodes can refer to edge servers in a CDN, which typically provide data transmission services to customers. In this embodiment, the central server generates a configuration file corresponding to the domain name. This configuration file can be used to configure the edge nodes of the served domain name. The configuration file generally contains functional configuration items. The configuration file can include multiple functions, that is, it can be composed of a combination of multiple functions. One configuration file can correspond to one domain name; that is, a complete configuration file corresponding to one domain name can be composed of multiple functions configured and combined as required, but it is not limited to this.

[0067] In this embodiment, the configuration files corresponding to each domain name can be divided into two main categories: business configuration files and certificate configuration files. Business configuration files are generally used to configure business-related aspects of the edge nodes serving the domain name. For example, business configuration files may include server port configuration parameters, cache configuration parameters, origin server configuration parameters, origin server topology configuration parameters, etc. Certificate configuration files are generally used to configure data encryption, authentication, and data integrity verification for edge nodes.

[0068] S102. Determine the shared domain name and the shared domain name based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file;

[0069] In this embodiment, for all domains under the same user ID, it is determined whether the business configuration files corresponding to the domains are the same. All domains with the same business configuration files can share the same business configuration file.

[0070] In one implementation, determining the shared domain name and the domain name to be shared based on the business configuration file includes: for all domain names with the same business configuration file, arbitrarily selecting one of the domain names as the domain name to be shared, and using the remaining domain names with the same business configuration file as the shared domain name.

[0071] In this embodiment, for all domains under the same user ID, it is determined whether the business configuration files corresponding to the domains are the same. From all domains with the same business configuration files, one domain is randomly selected as the shared domain, and the remaining domains with the same business configuration files are the shared domains.

[0072] Furthermore, after determining the shared domain name and the shared domain name, a sharing relationship is established between the shared domain name and the shared domain name. This sharing relationship can be one shared domain name corresponding to one shared domain name, or one shared domain name corresponding to multiple shared domain names. The specific sharing relationship is not limited in this embodiment.

[0073] It should be noted that for a shared domain, all full configuration files for that domain need to be generated, while for a shared domain, only the certificate configuration file for that domain needs to be generated separately.

[0074] S103. Determine the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name.

[0075] The first configuration file corresponding to the shared domain name is used to configure the edge nodes served by the shared domain name after being distributed to the edge nodes. The second configuration file corresponding to the shared domain name is also used to configure the edge nodes served by the shared domain name after being distributed to the edge nodes.

[0076] The first configuration file includes the full configuration file for the shared domain, including all business configuration files and the certificate configuration file corresponding to the shared domain. The second configuration file includes the aforementioned sharing relationship and the certificate configuration file corresponding to the shared domain.

[0077] In one implementation, determining the first configuration file corresponding to the shared domain name includes: using the business configuration file corresponding to the shared domain name and the certificate configuration file corresponding to the shared domain name as the first configuration file of the shared domain name.

[0078] In this embodiment, the business configuration file and certificate configuration file of the shared domain name generated in S101 above are used as the first configuration file of the shared domain name and distributed to the edge node corresponding to the shared domain name.

[0079] In one implementation, determining the second configuration file corresponding to the shared domain name includes: establishing a sharing relationship between the shared domain name and the shared domain name; and using the sharing relationship and the certificate configuration file corresponding to the shared domain name as the second configuration file corresponding to the shared domain name.

[0080] In this embodiment, the certificate configuration file corresponding to the above-mentioned sharing relationship and shared domain name is used as the second configuration file corresponding to the shared domain name and is sent to the edge node corresponding to the shared domain name.

[0081] It should be noted that nested sharing is not allowed; that is, you cannot simply use one port configuration file from the business configuration file as the shared configuration file. The shared domain name and the topology corresponding to the shared domain name must be exactly the same. Configuration files related to topology and hierarchical policies can be configured separately, or they can share configuration files for the topology and hierarchical policies of other domain names.

[0082] Furthermore, the access method for the shared domain name can be the same as or different from that of the shared domain name. The access method for the shared domain name can also be modified according to the actual situation.

[0083] Furthermore, shared domain names support shared billing and shared tiered strategies.

[0084] In this embodiment, for domains with the same business configuration file, if the business configuration file is updated or modified, only the business configuration file corresponding to the shared file needs to be modified. It is not necessary to modify the business configuration files corresponding to all domains. This enables the same domain to share the same business configuration file, reduces the complexity of customer business configuration, eliminates a large number of duplicate domain configurations, and improves the CDN domain configuration loading efficiency and system stability.

[0085] S104. The first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name are sent to the edge nodes so that the edge nodes can be configured.

[0086] The configuration files can be distributed to edge nodes using P2P (peer-to-peer) technology and FTP (File Transfer Protocol) technology.

[0087] Furthermore, for domains in a shared topology, if the business configuration file is modified, the modified business configuration file must be distributed across the shared topology. For a separate hierarchical topology, if the business configuration file is modified, the modified business configuration file must be distributed across all devices in the hierarchical topology.

[0088] The domain name configuration method provided in this disclosure includes: generating a configuration file corresponding to each domain name of the customer websites served by each edge node in the content delivery network, the configuration file including a business configuration file; determining a shared domain name and a shared domain name based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file; determining a first configuration file corresponding to the shared domain name and a second configuration file corresponding to the shared domain name; and distributing the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name to the edge nodes for configuration. The technical solution provided in this disclosure, where the shared domain name and the shared domain name share the same business configuration file, enables the same domain name to share the same business configuration file, reducing the complexity of customer business configuration, eliminating a large number of duplicate domain name configurations, and improving CDN domain name configuration loading efficiency and system stability.

[0089] In one embodiment, the method further includes: after terminating the sharing relationship between the shared domain name and the shared domain name, determining whether the change amount of the business configuration file exceeds the change amount threshold; if it exceeds, deleting all configuration files of the shared domain name and publishing the shared domain name as a new domain name; if it does not exceed, copying the business configuration file corresponding to the shared domain name into a second configuration file and re-distributing the second configuration file to the edge node.

[0090] In this embodiment, the threshold for the amount of change can be set according to the actual situation, and the specific value of the threshold for the amount of change is not limited in this embodiment.

[0091] In this embodiment, after the sharing relationship between the shared domain name and the shared domain name is terminated, the shared domain name needs to be configured with a full configuration file.

[0092] In this embodiment, a method for determining the full configuration file of a shared domain is provided. The method assesses the amount of change (modification) in the business configuration file of the shared domain. If the change is minor, the business configuration file of the shared domain is copied to a second configuration file corresponding to the shared domain. The sharing relationship in the second configuration file is deleted, and the copied business configuration file is modified. The modified business configuration file and the certificate configuration file in the second configuration file are then redistributed to the edge node corresponding to the shared domain.

[0093] If the changes are too large, delete all configuration files in the second configuration file corresponding to the shared domain name, and publish the shared domain name as a new domain name.

[0094] In one embodiment, a configuration file retrieval method is provided, which is applied to an edge server, such as... Figure 2 As shown, the configuration file acquisition method provided in this embodiment mainly includes the following steps:

[0095] S201. Receive request information sent by the client, wherein the request information carries a domain name corresponding to the client.

[0096] In this embodiment, when the client sends a request to the edge node to request data, it needs to parse the configuration information corresponding to the domain name and configure the edge node according to the configuration information.

[0097] After receiving the request information, it can be parsed to obtain the domain name corresponding to the client. The method for parsing the request information to obtain the client's domain name is not limited in this embodiment.

[0098] S202. If the domain name is a shared domain name, then determine the shared domain name corresponding to the shared domain name.

[0099] In this context, a shared domain name can be understood as a business configuration file that is identical to the business configuration file of the shared domain name.

[0100] Furthermore, after resolving the domain name, you can check whether the domain name carries a sharing identifier. If it does, then the domain name is determined to be a shared domain name.

[0101] In one implementation, if the domain name is a shared domain name, determining the shared domain name corresponding to the shared domain name includes: if the domain name is a shared domain name, reading the second configuration file corresponding to the shared domain name, wherein the second configuration file includes: the sharing relationship between the shared domain name and the shared domain name; and determining the shared domain name corresponding to the shared domain name based on the sharing relationship.

[0102] The second configuration file corresponding to the shared domain name is sent from the central server to the edge node. The sharing relationship between the shared domain name and the shared domain name in the second configuration file is read, and the shared domain name is determined based on the sharing relationship.

[0103] S203. Obtain the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name.

[0104] The business configuration file corresponding to the shared domain name is stored in the first configuration file corresponding to the shared domain name, which is configured and distributed by the central server.

[0105] Obtain the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name.

[0106] Furthermore, the second configuration file also includes: a certificate configuration file; the certificate configuration file in the second configuration file is used as the certificate configuration file for the shared domain name.

[0107] The shared domain name is configured on the edge nodes based on the obtained business configuration file and certificate configuration file.

[0108] In one embodiment, the method further includes: if the domain name is a shared domain name, then obtaining a first configuration file corresponding to the shared domain name, wherein the first configuration file includes a business configuration file corresponding to the shared domain name and a certificate configuration file corresponding to the shared domain name.

[0109] Furthermore, after resolving the domain name, you can check whether the domain name carries a shared identifier. If it does, then the domain name is confirmed to be a shared domain name.

[0110] Among them, the first configuration file corresponding to the shared domain name is the full configuration file. The business configuration file and certificate configuration file in the first configuration file are directly obtained to configure the edge nodes.

[0111] The configuration file acquisition method provided in this disclosure includes: receiving request information sent by a client, wherein the request information carries a domain name corresponding to the client; if the domain name is a shared domain name, determining the shared domain name corresponding to the shared domain name based on the sharing relationship, using the business configuration file corresponding to the shared domain name as the business configuration file corresponding to the shared domain name, using the certificate configuration file in the second configuration file as the certificate configuration file of the shared domain name, and configuring the edge node corresponding to the shared domain name according to the above business configuration file and certificate configuration file. The technical solution provided in this disclosure allows the shared domain name and the shared domain name to share the same business configuration file, reducing the complexity of customer business configuration, eliminating a large number of duplicate domain name configurations, and improving CDN domain name configuration loading efficiency and system stability.

[0112] This embodiment provides a method for returning a shared domain name to its origin server. For example... Figure 3 As shown, the methods for returning a shared domain name to its origin server mainly include the following steps:

[0113] 1. The central controller sends the second configuration file of a.com and the first configuration file of b.com to the configuration loading module.

[0114] Here, a.com is the shared domain, and b.com is the domain being shared. The second configuration file of a.com includes the sharing relationship between a.com and b.com and a.com's certificate configuration file. The first configuration file of b.com includes b.com's business configuration file and b.com's certificate configuration file. The configuration loading module is the module that stores configuration files in the edge nodes.

[0115] 2. The client sends a data request to the gateway via the domain name a.com.

[0116] 3. The gateway loads the second configuration file of a.com into the configuration loading module to obtain the sharing relationship between a.com and b.com and the certificate configuration file of a.com.

[0117] 4. The gateway loads the business configuration file of b.com.

[0118] 5. The storage module returns to the corresponding middle layer through the certificate configuration file of a.com and the business configuration file of b.com respectively.

[0119] 6. Each intermediate layer sends a data transfer signal to the source station.

[0120] This disclosure provides a domain name configuration device 40, which is configured on a central server, such as... Figure 4 As shown, the domain name configuration device 40 includes: a configuration file generation module 41, a domain name category determination module 42, a configuration file determination module 43, and a configuration file distribution module 44.

[0121] The configuration file generation module is used to generate a configuration file corresponding to each domain name for the domain names of customer websites served by each edge node in the CDN network. The configuration file includes a business configuration file.

[0122] The domain name category determination module is used to determine the shared domain name and the shared domain name based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file;

[0123] The configuration file determination module is used to determine the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name.

[0124] The configuration file distribution module is used to distribute the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name to the edge nodes so that the edge nodes can be configured.

[0125] In one implementation, determining the shared domain name and the domain name to be shared based on the business configuration file includes: for all domain names with the same business configuration file, arbitrarily selecting one of the domain names as the domain name to be shared, and using the remaining domain names with the same business configuration file as the shared domain name.

[0126] In one implementation, determining the first configuration file corresponding to the shared domain name includes: using the business configuration file corresponding to the shared domain name and the certificate configuration file corresponding to the shared domain name as the first configuration file of the shared domain name.

[0127] In one implementation, determining the second configuration file corresponding to the shared domain name includes: establishing a sharing relationship between the shared domain name and the shared domain name; and using the sharing relationship and the certificate configuration file corresponding to the shared domain name as the second configuration file corresponding to the shared domain name.

[0128] In one embodiment, the apparatus further includes: a relationship termination module, configured to, after terminating the sharing relationship between the shared domain name and the shared domain name, determine whether the change in the business configuration file exceeds a change threshold; if it exceeds, delete all configuration files of the shared domain name and publish the shared domain name as a new domain name; if it does not exceed, copy the business configuration file corresponding to the shared domain name to a second configuration file and re-distribute the second configuration file to the edge node.

[0129] Figure 4 The domain name configuration device shown in the embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0130] This disclosure provides a configuration file acquisition device 50, which is configured on an edge server, such as... Figure 5 As shown, the configuration file acquisition device 50 includes: an information receiving module 51, a domain name category determination module 53, and a configuration file acquisition module 54.

[0131] The information receiving module 51 is used to receive request information sent by the client, wherein the request information carries a domain name corresponding to the client;

[0132] Domain category determination module 52 is used to determine the shared domain corresponding to the shared domain if the domain is a shared domain;

[0133] The configuration file acquisition module 53 is used to acquire the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name.

[0134] In one embodiment, the configuration file acquisition module 53 is further configured to acquire a first configuration file corresponding to the shared domain name if the domain name is a shared domain name, wherein the first configuration file includes a business configuration file corresponding to the shared domain name and a certificate configuration file corresponding to the shared domain name.

[0135] In one implementation, if the domain name is a shared domain name, determining the shared domain name corresponding to the shared domain name includes: if the domain name is a shared domain name, reading the second configuration file corresponding to the shared domain name, wherein the second configuration file includes: the sharing relationship between the shared domain name and the shared domain name; and determining the shared domain name corresponding to the shared domain name based on the sharing relationship.

[0136] In one embodiment, the second configuration file further includes: a certificate configuration file; the configuration file acquisition module 53 is further configured to use the certificate configuration file in the second configuration file as the certificate configuration file of the shared domain name.

[0137] Figure 5 The configuration file acquisition device shown in the embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0138] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. The electronic device in this disclosure can be a domain name configuration device or a configuration file acquisition device. The domain name configuration device provided in this disclosure can execute the processing flow provided in the domain name configuration method embodiment, and the configuration file acquisition device provided in this disclosure can execute the processing flow provided in the configuration file acquisition method embodiment.

[0139] like Figure 6 As shown, the electronic device 60 includes: a memory 61, a processor 62, a computer program, and a communication interface 63; wherein, the computer program is stored in the memory 61 and is configured to be executed by the processor 62 as described above, using the domain name configuration method or the configuration file acquisition method.

[0140] In addition, this disclosure also provides a computer-readable storage medium storing a computer program thereon, which is executed by a processor to implement the service alarm method or configuration file acquisition method described in the above embodiments.

[0141] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0142] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A domain name configuration method, characterized in that, The method is applied to a central server and includes: For each domain name of the customer website served by each edge node in the content delivery network, a configuration file corresponding to the domain name is generated, and the configuration file includes a business configuration file. The shared domain name and the shared domain name are determined based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file; Determine the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name; The first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name are distributed to the edge nodes so that the edge nodes can be configured. The step of determining the shared domain name and the domain name to be shared based on the business configuration file includes: for all domain names with the same business configuration file, arbitrarily selecting one of the domain names as the domain name to be shared, and using the remaining domain names with the same business configuration file as the shared domain name; After determining the shared domain name and the domain name being shared, the method further includes: establishing a sharing relationship between the shared domain name and the domain name being shared; The first configuration file includes: the business configuration file corresponding to the shared domain name and the certificate configuration file corresponding to the shared domain name; the second configuration file includes: the sharing relationship and the certificate configuration file corresponding to the shared domain name.

2. The method according to claim 1, characterized in that, Determining the first configuration file corresponding to the shared domain name includes: The business configuration file and the certificate configuration file corresponding to the shared domain name are used as the first configuration file of the shared domain name.

3. The method according to claim 1, characterized in that, Determine the second configuration file corresponding to the shared domain name, including: Establish a sharing relationship between the shared domain name and the shared domain name; The shared relationship and the certificate configuration file corresponding to the shared domain name are used as the second configuration file corresponding to the shared domain name.

4. The method according to claim 1, characterized in that, The method further includes: After terminating the sharing relationship between the shared domain name and the shared domain name, determine whether the change in the business configuration file exceeds the change threshold. If the limit is exceeded, delete all configuration files for the shared domain name and publish the shared domain name as a new domain name; If the limit is not exceeded, the business configuration file corresponding to the shared domain name is copied to the second configuration file, and the second configuration file is re-distributed to the edge node.

5. A method for obtaining a configuration file, characterized in that, The method is applied to an edge server and includes: Receive request information sent by a client, wherein the request information carries a domain name corresponding to the client; If the domain name is a shared domain name, then determine the shared domain name corresponding to the shared domain name; Obtain the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name; Wherein, if the domain name is a shared domain name, determining the shared domain name corresponding to the shared domain name includes: If the domain name is a shared domain name, read the second configuration file corresponding to the shared domain name, wherein the second configuration file includes: the sharing relationship between the shared domain name and the shared domain name; The shared domain name corresponding to the shared domain name is determined based on the sharing relationship.

6. The method according to claim 5, characterized in that, The method further includes: If the domain name is a shared domain name, then obtain the first configuration file corresponding to the shared domain name, wherein the first configuration file includes the business configuration file corresponding to the shared domain name and the certificate configuration file corresponding to the shared domain name.

7. The method according to claim 5, characterized in that, The second configuration file also includes: a certificate configuration file; The method further includes: Use the certificate configuration file in the second configuration file as the certificate configuration file for the shared domain name.

8. A domain name configuration device, characterized in that, The device is configured on a central server and includes: The configuration file generation module is used to generate a configuration file corresponding to each domain name of the customer websites served by each edge node in the CDN network. The configuration file includes a business configuration file. The domain name category determination module is used to determine the shared domain name and the shared domain name based on the business configuration file, wherein the shared domain name and the shared domain name share the same business configuration file; The configuration file determination module is used to determine the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name; The configuration file distribution module is used to distribute the first configuration file corresponding to the shared domain name and the second configuration file corresponding to the shared domain name to the edge nodes so that the edge nodes can be configured. The step of determining the shared domain name and the domain name to be shared based on the business configuration file includes: for all domain names with the same business configuration file, arbitrarily selecting one of the domain names as the domain name to be shared, and using the remaining domain names with the same business configuration file as the shared domain name; After determining the shared domain name and the domain name being shared, the method further includes: establishing a sharing relationship between the shared domain name and the domain name being shared; The first configuration file includes: the business configuration file corresponding to the shared domain name and the certificate configuration file corresponding to the shared domain name; the second configuration file includes: the sharing relationship and the certificate configuration file corresponding to the shared domain name.

9. A configuration file acquisition device, characterized in that, The device is configured on an edge server and includes: An information receiving module is used to receive request information sent by a client, wherein the request information carries a domain name corresponding to the client; The domain name category determination module is used to determine the shared domain name corresponding to the shared domain name if the domain name is a shared domain name; The configuration file acquisition module is used to acquire the business configuration file corresponding to the shared domain name as the business configuration file of the shared domain name; Wherein, if the domain name is a shared domain name, determining the shared domain name corresponding to the shared domain name includes: If the domain name is a shared domain name, read the second configuration file corresponding to the shared domain name, wherein the second configuration file includes: the sharing relationship between the shared domain name and the shared domain name; The shared domain name corresponding to the shared domain name is determined based on the sharing relationship.

10. An electronic device, comprising: Memory; processor; as well as Computer programs; The computer program is stored in the memory and configured to be executed by the processor to implement the method as described in any one of claims 1-7.

11. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method as described in any one of claims 1-7.

Images