Overlapping domain name configuration method and system

Abstract

The present invention discloses an overlapping domain name configuration method and system, which are applied to a registration center system. The method comprises: when a network configuration center sends overlapping domain names to corresponding gateway nodes, distinguishing by setting a label in an edge association relationship in a configuration file; the network configuration center calls RAP to obtain the edge association relationship and sends it to a central registration center; the central registration center instantly synchronizes to a local registration center through an internal synchronization mechanism; when an edge acceleration gateway is restarted or an overlapping domain name is hot-loaded, the local registration center is called to obtain the edge association relationship and cache it to the local of the edge acceleration gateway; when a user device sends an Internet access request, searching in the local cache of the edge acceleration gateway whether there is an overlapping domain name; when there is an overlapping domain name, processing is performed according to the overlapping domain name scenario; when there is no overlapping domain name, processing is performed according to the original domain name scenario.

Description

Technical Field

[0001] The invention belongs to the technical field of network configuration, and in particular relates to a method and system for configuring overlapping domain names. Background Art

[0002] In the actual application of CDN gateway, there is a relatively special customer demand scenario. The original customer A provides bandwidth to multiple CDN manufacturers. Due to cooperation or resource sharing, multiple CDN manufacturers may merge with each other. For example, both manufacturers B and C receive the volume provided by manufacturer A. Then manufacturer B shares the volume merged with manufacturer A with manufacturer C. At this time, manufacturer C will encounter overlapping domain names.

[0003] In order to solve the problem of overlapping domain names, the existing technology usually adopts: the servername of $host.accid is sent by the configuration platform to distinguish different sub-channels, and then the vip|host accid association file is sent to the gateway through ARK. After the gateway is reloaded, when the request of the user device comes in, the accid is found through vip|host matching, and then the corresponding sub-channel is found to follow the internal cache acceleration logic. Under this method, there are the following problems: First, there is a certain coupling between the sub-channels managed by the configuration platform and the public configuration managed by ARK; secondly, when the local vip|host accid association file is placed on each VIP, ARK needs to distinguish different nodes and send different files, and there is a risk of file tampering; in addition, the public configuration sending method requires grayscale verification to take effect, and it strongly relies on manual intervention, and the manpower and time costs are high.

[0004] In the prior art, there are at least the following technical problems in handling overlapping domain names: the association relationship file is at risk of being tampered with during the distribution process, the public configuration distribution method requires grayscale verification to take effect, and it strongly relies on manual intervention, with high manpower and time costs. Summary of the invention

[0005] The purpose of the embodiments of the present invention is to provide a method and system for configuring overlapping domain names, which can solve the technical problems that the existing technical association relationship files are at risk of being tampered with during the issuance process, the public configuration issuance method requires grayscale verification to take effect, and is highly dependent on manual intervention, with high manpower and time costs.

[0006] In order to solve the above-mentioned technical problems, the present invention is achieved as follows:

[0007] First aspect

[0008] An embodiment of the present invention provides an overlapping domain name configuration method, which is applied to a registration center system. The registration center system includes a central registration center and a local registration center. The central registration center and the local registration center establish a communication connection through a long connection. A local registration center and a gateway node are set on a machine corresponding to each edge acceleration gateway. The overlapping domain name configuration method includes:

[0009] S101: When the network configuration center sends overlapping domain names to corresponding gateway nodes, the distinction is achieved by setting a label in the edge association relationship in the configuration file;

[0010] S102: The network configuration center calls RAP to obtain edge association relationships and sends them to the central registration center;

[0011] S103: The central registration center is synchronized to the local registration center corresponding to each gateway node in real time through an internal synchronization mechanism;

[0012] S104: When the edge acceleration gateway is restarted or the overlapping domain name is hot loaded, the local registration center is called to obtain the edge association relationship and cache it locally in the edge acceleration gateway;

[0013] S105: When the user device sends an Internet access request, it searches the local cache of the edge acceleration gateway to see whether there is an overlapping domain name;

[0014] S106: When there are overlapping domain names, the overlapping domain name scenario is used for processing; when there are no overlapping domain names, the original domain name scenario is used for processing.

[0015] Optionally, the overlapping domain name configuration method further includes:

[0016] S107: When the network configuration center sends the original domain name to the corresponding gateway node, the original domain name scenario is processed.

[0017] Optionally, S104 specifically includes:

[0018] Restart the gateway at the preset frequency, call the local registration center, obtain the edge association relationship, and cache it locally on the edge acceleration gateway.

[0019] Optionally, the overlapping domain name configuration method further includes:

[0020] S108: In case of an abnormality in the local registration center, request the central registration center to ensure the accuracy and consistency of the data until the local registration center returns to normal.

[0021] Optionally, the edge association is host.accid and the label is servername.

[0022] Second aspect

[0023] An embodiment of the present invention provides an overlapping domain name configuration system, which is a registration center system. The registration center system includes a central registration center and a local registration center. The central registration center and the local registration center establish a communication connection through a long connection. A local registration center and a gateway node are set on a machine corresponding to each edge acceleration gateway. The overlapping domain name configuration system includes:

[0024] The first sending module is used to distinguish overlapping domain names by setting labels in the edge association relationship in the configuration file when the network configuration center sends overlapping domain names to the corresponding gateway nodes;

[0025] The calling module is used by the network configuration center to call RAP to obtain edge association relationships and send them to the central registration center;

[0026] Synchronization module, which is used for the central registration center to synchronize instantly with the local registration center corresponding to each gateway node through the internal synchronization mechanism;

[0027] The cache module is used to call the local registration center to obtain the edge association relationship and cache it locally in the edge acceleration gateway when the edge acceleration gateway is restarted or the overlapping domain name is hot loaded;

[0028] A search module is used to search for overlapping domain names in the local cache of the edge acceleration gateway when a user device sends an Internet access request;

[0029] The processing module is used to process the overlapping domain names according to the overlapping domain name scenario when there are overlapping domain names; and to process the original domain name scenario when there are no overlapping domain names.

[0030] Optionally, the overlapping domain name configuration system further includes:

[0031] The second sending module is used to process according to the original domain name scenario when the network configuration center sends the original domain name to the corresponding gateway node.

[0032] Optionally, the cache module is specifically used for:

[0033] Restart the gateway at the preset frequency, call the local registration center, obtain the edge association relationship, and cache it locally on the edge acceleration gateway.

[0034] Optionally, the overlapping domain name configuration system further includes:

[0035] The request module is used to request the central registration center to ensure the accuracy and consistency of data when the local registration center is abnormal, until the local registration center returns to normal.

[0036] Optionally, the edge association is host.accid and the label is servername.

[0037] The benefit of the present invention lies in that, in an embodiment of the present invention, by configuring the central registration center and the local registration center, the central registration center and the local registration center establish a communication connection through a long connection. When facing overlapping domain names, the network configuration center will send the edge association relationship to the central registration center, and then the central registration center and the local registration center will keep in sync, cache the edge association relationship locally in the edge acceleration gateway, and when the user device sends an Internet access request, it will search locally in the edge acceleration gateway to see if there is an overlapping domain name, and process it according to the corresponding processing method based on the search result. There is no risk of tampering with the association relationship file when it is synchronously transmitted between the central registration center and the local registration center. By keeping in sync with the central registration center and the local registration center, there is no need to rely on manual intervention, which can save manpower and time costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a flowchart of a method for configuring overlapping domain names provided by an embodiment of the present invention;

[0039] Figure 2 This is a schematic diagram of a process flow of a user device requesting Internet access provided by an embodiment of the present invention;

[0040] Figure 3 It is a structural diagram of an overlapping domain name configuration system provided by an embodiment of the present invention.

[0041] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0043] In conjunction with the accompanying drawings, a method and system for configuring overlapping domain names provided by the embodiment of the present invention will be described in detail through specific embodiments and application scenarios.

[0044] Embodiment 1

[0045] Reference Figure 1 , shows a flow chart of an overlapping domain name configuration method provided by an embodiment of the present invention.

[0046] An overlapping domain name configuration method provided by an embodiment of the present invention is applied to a registration center system. The registration center system includes a central registration center and a local registration center. The central registration center and the local registration center establish a communication connection through a long connection. A local registration center and a gateway node are set on a machine corresponding to each edge acceleration gateway.

[0047] Using a persistent connection to establish a communication connection between the central registry and the local registry can ensure the efficiency and latency of gateway requests.

[0048] A local registration center and gateway node are set up on the machine corresponding to each edge acceleration gateway. This distributed deployment can ensure the efficiency and performance of user requests.

[0049] At the same time, the high scalability of the registration center system can provide architectural support for subsequent solutions to problems such as public configuration management, unified configuration of different configuration levels of gateways, containerization, and dynamic scaling.

[0050] Overlapping domain name configuration methods include:

[0051] S101: When the network configuration center sends overlapping domain names to corresponding gateway nodes, the distinction is achieved by setting labels in the edge association relationship in the configuration file.

[0052] Among them, the edge association relationship is host.accid and the label is servername.

[0053] For example, the configuration center sends bg0.market.xiaomi.com.accid1 to the edge node 121.2.1.2.

[0054] S102: The network configuration center calls RAP to obtain edge association relationships and sends them to the central registration center.

[0055] For example, call RAP through the bg0.market.xiaomi.com accid resource pool to obtain the vip|host accid relationship.

[0056] Specifically, the network configuration center calls RAP through the host accid resource pool to obtain the vip|host accid relationship. It should be understood that only the data of the edge vip is obtained at this time.

[0057] S103: The central registration center is instantly synchronized to the local registration center corresponding to each gateway node through an internal synchronization mechanism.

[0058] On the one hand, there is no risk of tampering with the association relationship files when they are synchronously transmitted between the central registration center and the local registration center; on the other hand, by keeping the central registration center and the local registration center synchronized, there is no need to rely on manual intervention, which can save manpower and time costs.

[0059] S104: When the edge acceleration gateway is restarted or the overlapping domain name is hot loaded, the local registration center is called to obtain the edge association relationship and cache it locally in the edge acceleration gateway.

[0060] Among them, caching locally can improve the response performance of user requests.

[0061] In a possible implementation, S104 specifically includes: restarting the gateway at a preset frequency, calling a local registration center, obtaining edge association relationships, and caching them locally at the edge acceleration gateway.

[0062] The preset frequency is synchronized once every 1 ms. Those skilled in the art can set the specific size of the preset frequency according to actual needs.

[0063] Reference Figure 2 , shows a schematic diagram of a process flow of a user device Internet access request provided by an embodiment of the present invention.

[0064] S105: When the user device sends an Internet access request, it searches the local cache for overlapping domain names.

[0065] Specifically, the accid (overlapping domain name) is searched through the vip host in the local cache.

[0066] For example, the normal request domain name bg0.market.xiaomi.com resolves to 121.2.1.2.

[0067] S106: When there are overlapping domain names, the overlapping domain name scenario is used for processing; when there are no overlapping domain names, the original domain name scenario is used for processing.

[0068] For example, when the customer ID of accid1 can be found by searching the local cache through the IP and host, it is processed according to the overlapping domain name scenario; if the user ID does not exist, it is processed according to the original domain name scenario.

[0069] In a possible implementation, the overlapping domain name configuration method further includes:

[0070] S107: When the network configuration center sends the original domain name to the corresponding gateway node, the original domain name scenario is processed.

[0071] It should be understood that when the network configuration center sends down domain names, there are two situations: one is sending down overlapping domain names, that is, using S101; the other is sending down original domain names, in this case, using S107.

[0072] In a possible implementation, the overlapping domain name configuration method further includes:

[0073] S108: In case of an abnormality in the local registration center, request the central registration center to ensure the accuracy and consistency of the data until the local registration center returns to normal.

[0074] Maintaining data accuracy and consistency through a central registration center can avoid errors in data transmission.

[0075] In an embodiment of the present invention, by configuring the central registration center and the local registration center, the central registration center and the local registration center establish a communication connection through a long connection. When facing overlapping domain names, the network configuration center will send the edge association relationship to the central registration center, and then the central registration center and the local registration center will keep in sync, cache the edge association relationship locally in the edge acceleration gateway, and when the user device sends an Internet access request, it will search locally in the edge acceleration gateway to see if there is an overlapping domain name, and process it according to the corresponding processing method based on the search result. There is no risk of the association relationship file being tampered with when it is transmitted between the central registration center and the local registration center. By keeping in sync with the central registration center and the local registration center, there is no need to rely on manual intervention, which can save manpower and time costs.

[0076] Embodiment 2

[0077] Reference Figure 3 , showing a structural diagram of an overlapping domain name configuration system provided by an embodiment of the present invention.

[0078] The overlapping domain name configuration system 30 is a registration center system, which includes a central registration center and a local registration center. The central registration center and the local registration center establish a communication connection through a long connection. A local registration center and a gateway node are set on the machine corresponding to each edge acceleration gateway.

[0079] The overlapping domain name configuration system 30 includes:

[0080] The first sending module 301 is used for distinguishing overlapping domain names by setting labels in edge association relationships in a configuration file when the network configuration center sends overlapping domain names to corresponding gateway nodes;

[0081] The calling module 302 is used for the network configuration center to call RAP to obtain edge association relationship and send it to the central registration center;

[0082] Synchronization module 303, used for the central registration center to synchronize instantly with the local registration center corresponding to each gateway node through the internal synchronization mechanism;

[0083] The cache module 304 is used to call the local registration center to obtain the edge association relationship and cache it locally in the edge acceleration gateway when the edge acceleration gateway is restarted or the overlapping domain name is hot loaded;

[0084] A search module 305 is used to search for overlapping domain names in the local cache of the edge acceleration gateway when a user device sends an Internet access request;

[0085] The processing module 306 is used to process according to the overlapping domain name scenario when there are overlapping domain names; and to process according to the original domain name scenario when there are no overlapping domain names.

[0086] In a possible implementation, the overlapping domain name configuration system 30 further includes:

[0087] The second sending module 307 is used to process according to the original domain name scenario when the network configuration center sends the original domain name to the corresponding gateway node.

[0088] In a possible implementation, the cache module 304 is specifically configured to:

[0089] Restart the gateway at the preset frequency, call the local registration center, obtain the edge association relationship, and cache it locally on the edge acceleration gateway.

[0090] In a possible implementation, the overlapping domain name configuration system 30 further includes:

[0091] The request module 308 is used to request the central registration center to ensure the accuracy and consistency of data when the local registration center is abnormal, until the local registration center returns to normal.

[0092] In a possible implementation, the edge association relationship is host.accid, and the label is servername.

[0093] The overlapping domain name configuration system provided in the embodiment of the present invention can implement each process implemented in the above method embodiment, and will not be described again here to avoid repetition.

[0094] In an embodiment of the present invention, by configuring the central registration center and the local registration center, the central registration center and the local registration center establish a communication connection through a long connection. When facing overlapping domain names, the network configuration center will send the edge association relationship to the central registration center, and then the central registration center and the local registration center will keep in sync, cache the edge association relationship locally in the edge acceleration gateway, and when the user device sends an Internet access request, it will search locally in the edge acceleration gateway to see if there is an overlapping domain name, and process it according to the corresponding processing method based on the search result. There is no risk of tampering with the association relationship file when it is synchronously transmitted between the central registration center and the local registration center. By keeping in sync with the central registration center and the local registration center, there is no need to rely on manual intervention, which can save manpower and time costs.

[0095] The virtual system in the embodiment of the present invention may be a system, or a component, an integrated circuit, or a chip in a terminal.

[0096] The above are only embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. A method for configuring overlapping domain names, characterized in that: Applied to a registration center system, the registration center system includes a central registration center and a local registration center, the central registration center and the local registration center establish a communication connection through a long connection, and a local registration center and a gateway node are set on a machine corresponding to each edge acceleration gateway, and the overlapping domain name configuration method includes: S101: When the network configuration center sends overlapping domain names to corresponding gateway nodes, the distinction is achieved by setting a label in the edge association relationship in the configuration file; S102: The network configuration center calls RAP to obtain the edge association relationship and sends it to the central registration center; S103: The central registration center is synchronized to the local registration center corresponding to each gateway node in real time through an internal synchronization mechanism; S104: When the edge acceleration gateway is restarted or the overlapping domain name is hot-loaded, the local registration center is called to obtain the edge association relationship and cache it locally on the edge acceleration gateway; S105: When the user device sends an Internet access request, searching the local cache of the edge acceleration gateway for overlapping domain names; S106: When there are overlapping domain names, the overlapping domain name scenario is used for processing; when there are no overlapping domain names, the original domain name scenario is used for processing.

2. The overlapping domain name configuration method according to claim 1, characterized in that: Also includes: S107: When the network configuration center sends the original domain name to the corresponding gateway node, processing is performed according to the original domain name scenario.

3. The overlapping domain name configuration method according to claim 1, characterized in that: The S104 is specifically as follows: Restart the gateway at a preset frequency, call the local registration center, obtain the edge association relationship, and cache it locally in the edge acceleration gateway.

4. The overlapping domain name configuration method according to claim 1, characterized in that: Also includes: S108: In the case where the local registration center is abnormal, request the central registration center to ensure the accuracy and consistency of the data until the local registration center returns to normal.

5. The overlapping domain name configuration method according to claim 1, characterized in that: The edge association relationship is host.accid, and the label is server name.

6. A system for configuring overlapping domain names, characterized in that: The overlapping domain name configuration system is a registration center system, which includes a central registration center and a local registration center. The central registration center establishes a communication connection with the local registration center through a long connection. A local registration center and a gateway node are set on the machine corresponding to each edge acceleration gateway. The overlapping domain name configuration system includes: The first sending module is used to distinguish overlapping domain names by setting labels in the edge association relationship in the configuration file when the network configuration center sends overlapping domain names to the corresponding gateway nodes; A calling module, used for the network configuration center to call RAP to obtain the edge association relationship and send it to the central registration center; A synchronization module, used for the central registration center to instantly synchronize to the local registration center corresponding to each gateway node through an internal synchronization mechanism; A cache module, used to call the local registration center to obtain the edge association relationship and cache it locally on the edge acceleration gateway when the edge acceleration gateway is restarted or the overlapping domain name is hot loaded; A search module, used to search for overlapping domain names in the local cache of the edge acceleration gateway when a user device sends an Internet access request; The processing module is used to process the overlapping domain names according to the overlapping domain name scenario when there are overlapping domain names; and to process the original domain name scenario when there are no overlapping domain names.

7. The overlapping domain name configuration system according to claim 6, characterized in that: Also includes: The second sending module is used to process according to the original domain name scenario when the network configuration center sends the original domain name to the corresponding gateway node.

8. The overlapping domain name configuration system according to claim 6, characterized in that: The cache module is specifically used for: Restart the gateway at a preset frequency, call the local registration center, obtain the edge association relationship, and cache it locally in the edge acceleration gateway.

9. The overlapping domain name configuration system according to claim 6, characterized in that: Also includes: The request module is used to request the central registration center to ensure the accuracy and consistency of data when the local registration center is abnormal, until the local registration center returns to normal.

10. The overlapping domain name configuration system according to claim 6, characterized in that: The edge association relationship is host.accid, and the label is server name.

Images