Domain name management method and related equipment

Abstract

The invention provides a domain name management method, which is applied to a domain name management system, the domain name management system comprises a domain name system and a scheduling system, and the method comprises the following steps: the scheduling system receives an access request of a user, the access request comprises a service domain name, and the scheduling system sends a service domain name to the user according to the access request; a target device is determined from a plurality of access network devices of a service domain name service, the access request is redirected to the target device in a normal service state, the domain name system receives a domain name resolution request of a user, the domain name resolution request of the user is generated according to redirection information, the domain name resolution request of the user comprises a self-resolution domain name of the target device, and the self-resolution domain name of the target device is sent to the domain name system. The domain name system determines the service address of the target device according to the mapping mode of the self-resolution domain name and the service address and the self-resolution domain name of the target device, and the domain name system returns the service address of the target device so that the user can access the target device. According to the method, the self-resolution domain name is introduced, massive domain name resolution records do not need to be maintained, and the maintenance difficulty and cost are reduced.

Description

[0001] This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on June 15, 2023, with application number 202310714537.3 and invention name “A domain name management method and related equipment”, the entire contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of computer technology, and in particular to a domain name management method, system, computing device cluster, computer-readable storage medium, and computer program product. Background Art

[0003] Content Delivery Network (CDN) is a technology that distributes source site content to nodes in different regions, thereby shortening the latency for users in different regions to obtain objects and improving the response speed and availability of websites. Using CDN will greatly simplify the system maintenance workload of websites. Website maintenance personnel only need to inject website content into the CDN system, and distribute it across the entire network through servers deployed by CDN in various physical locations, thus achieving full network coverage across operators and regions.

[0004] The bandwidth cost of CDN operation is high, usually reaching more than 80% of the total cost. In order to reduce costs, CDN operators can offload high-cost bandwidth traffic by accessing a large number of access network devices close to users, such as optical network terminals (ONTs) and routers.

[0005] Considering security, more and more services use HyperText Transfer Protocol Secure (HTTPS) for data transmission, which generates HTTPS traffic. In order to safely offload the HTTPS traffic of CDN to the access network equipment, the industry has proposed an offloading solution based on a dedicated domain name. When scheduling HTTPS traffic, the scheduling system uses the dedicated domain name of the access network equipment to schedule the user's HTTPS request to the HTTPS service address of the access network equipment.

[0006] However, when the service address of the access network device changes (for example, the operator will trigger a redial change of the service address for dial-up Internet access in about 2 days), the exclusive domain name resolution record of the access network device needs to be updated. The number of exclusive domain names of massive access network devices can reach hundreds of millions. Exclusive domain name resolution records are difficult to maintain and frequently updated, which has a great impact on the authoritative domain name server and is difficult to meet business needs. Summary of the invention

[0007] The present application provides a domain name management method, which introduces a self-resolving domain name instead of a dedicated domain name. Based on the service address (such as an IP address) of the access network device, the self-resolving domain name of the access network device can be automatically converted. Conversely, the self-resolving domain name based on the access network device can be automatically converted to obtain the service address of the access network device. For the self-resolving domain name, there is no need to maintain a large number of domain name resolution records, nor is there a need to update the domain name resolution record when the service address changes, which greatly reduces the maintenance difficulty and maintenance cost, reduces the impact on the domain name system such as the authoritative DNS, and can meet business needs. The present application also provides a domain name system, a scheduling system, a computing device cluster, a computer-readable storage medium, and a computer program product corresponding to the domain name management method.

[0008] In a first aspect, the present application provides a domain name management method. The method can be applied to a domain name management system. The domain name management system can be a software system, which can be deployed in a computing device cluster, and the computing device cluster executes the program code of the software system to execute the domain name management method of the present application. The domain name management system can also be a hardware system, for example, a computing device cluster with domain name management functions (such as domain name resolution, domain name scheduling), and when the computing device cluster is running, the domain name management method of the present application is executed.

[0009] Specifically, the domain name management system includes a domain name system and a scheduling system. The scheduling system receives a user's access request, the access request includes a service domain name, and then determines the target device from multiple access network devices serving the service domain name according to the access request, and redirects the access request to the target device. Among them, the service status of the target device is normal. The user can generate a domain name resolution request based on the redirection information, and the user's domain name resolution request includes the self-resolving domain name of the target device. Correspondingly, the domain name system receives the user's domain name resolution request, determines the service address of the target device according to the mapping method of the self-resolving domain name and the service address and the self-resolving domain name of the target device, and then the domain name system returns the service address of the target device, and the service address of the target device is used to access the target device.

[0010] This method introduces a self-resolving domain name to replace the exclusive domain name. The service address of the access network device can be automatically converted to the self-resolving domain name of the access network device. Conversely, the self-resolving domain name based on the access network device can be automatically converted to the service address of the access network device. For the self-resolving domain name, there is no need to maintain a large number of domain name resolution records, nor is there a need to update the domain name resolution record when the service address changes, which greatly reduces the maintenance difficulty and maintenance cost, reduces the impact on the domain name system such as the authoritative DNS, and can meet business needs. Moreover, after the introduction of the self-resolving domain name, the dispatching system and the authoritative DNS can achieve self-resolving based on the mapping method of the self-resolving domain name and the service address, eliminating the dependence between the dispatching center and the authoritative DNS.

[0011] In some possible implementations, the self-resolving domain name includes a domain name prefix and a fixed domain name suffix, the domain name prefix is ​​generated according to the service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name. Accordingly, the domain name system can extract the domain name prefix from the self-resolving domain name of the target device, and then reversely map the domain name prefix according to the mapping method between the self-resolving domain name and the service address to obtain the service address of the target device.

[0012] In this method, the mapping between the domain name prefix and the service address is reversible, thereby realizing forward resolution of the domain name (domain name resolution to service address) and reverse resolution of the domain name (service address resolution to domain name). There is no need to maintain a large number of domain name resolution records. Instead, real-time self-resolution is achieved through the above mapping, which solves the problems of difficult maintenance of domain name resolution records, high update costs, and a large impact on authoritative DNS.

[0013] In some possible implementations, the mapping method includes at least one of base conversion or string conversion. Base conversion includes but is not limited to decimal conversion and hexadecimal conversion. The above mapping method is reversible, laying the foundation for realizing self-resolution of domain names. Both the domain name system and the dispatching system can realize self-resolution of domain names based on the mapping method, eliminating the dependence between the dispatching center and the authoritative DNS.

[0014] In some possible implementations, before the scheduling system receives the user's access request, it may receive a registration request from the access network device, the registration request including the service address of the access network device. Accordingly, the scheduling system generates a self-resolving domain name for the access network device according to the mapping method between the self-resolving domain name and the service address and the service address of the access network device.

[0015] This helps in scheduling access requests to access network devices to achieve traffic offloading.

[0016] In some possible implementations, the domain name system may also receive a domain name resolution request from the scheduling system, the domain name resolution request from the scheduling system includes the self-resolving domain name of the access network device, and the domain name system returns the service address of the access network device to the scheduling system. The scheduling system detects the service status of the access network device according to the service address of the access network device.

[0017] In this method, the scheduling system can provide a reference for subsequent access request scheduling by sensing the service status of the access network device, ensuring that the access request is scheduled to the access network device with normal service status, thereby ensuring service quality while achieving traffic offloading.

[0018] In some possible implementations, the service status includes a domain name resolution service DNS status. The scheduling system may compare the service address of the access network device returned by the domain name system with the current service address of the access network device. When the service address of the access network device returned by the domain name system is consistent with the current service address of the access network device, the scheduling system determines that the DNS status of the access network device is normal; when the service address of the access network device returned by the domain name system is inconsistent with the current service address of the access network device, the scheduling system determines that the DNS status of the access network device is abnormal.

[0019] In this method, the scheduling system can determine the DNS service status by comparing the resolution result of the domain name system with the current service address of the access network device, providing a basis for subsequent scheduling decisions.

[0020] In some possible implementations, the service status includes the HTTPS service status. The dispatching system initiates an HTTPS service dial test request to the access network device. When the dial test response is successful, the dispatching system determines that the HTTPS service of the access network device is normal; when the dial test response fails, the dispatching system determines that the HTTPS service of the access network device is abnormal.

[0021] In this method, the scheduling system analyzes the HTTPS service status through the dial test response corresponding to the HTTPS service dial test request, providing a basis for subsequent scheduling decisions.

[0022] In some possible implementations, the scheduling system can also receive a heartbeat message from the access network device. The scheduling system checks whether the service address of the access network device has changed according to the heartbeat message, and if so, updates the self-resolving domain name of the access network device according to the mapping method between the self-resolving domain name and the service address.

[0023] In this way, when the service address of the access network device changes, the self-resolving domain name of the access network device can be updated in real time, avoiding redirection anomalies caused by untimely updating of the self-resolving domain name, thereby ensuring service quality.

[0024] In a second aspect, the present application provides a domain name management system. The domain name management system comprises:

[0025] The scheduling system is used to receive an access request from a user, the access request including a service domain name, determine a target device from a plurality of access network devices serving the service domain name according to the access request, and redirect the access request to the target device, wherein the service status of the target device is normal;

[0026] A domain name system, used to receive a domain name resolution request of the user, the domain name resolution request of the user is generated according to the redirection information, and the domain name resolution request of the user includes a self-resolvable domain name of the target device;

[0027] The domain name system is also used to determine the service address of the target device according to the mapping method of the self-resolving domain name and the service address and the self-resolving domain name of the target device, and return the service address of the target device, and the service address of the target device is used to access the target device.

[0028] In some possible implementations, the self-resolving domain name includes a domain name prefix and a fixed domain name suffix, the domain name prefix is ​​generated according to the service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name;

[0029] The domain name system is specifically used for:

[0030] Extracting the domain name prefix from the self-resolvable domain name of the target device;

[0031] The domain name prefix is ​​reverse mapped according to the mapping method of the self-resolving domain name and the service address to obtain the service address of the target device.

[0032] In some possible implementations, the mapping method includes at least one of base conversion or string conversion.

[0033] In some possible implementations, the scheduling system is further used to:

[0034] receiving a registration request of the access network device, wherein the registration request includes a service address of the access network device;

[0035] A self-resolving domain name of the access network device is generated according to a mapping method between the self-resolving domain name and the service address and the service address of the access network device.

[0036] In some possible implementations, the domain name system is also used to:

[0037] receiving a domain name resolution request of the scheduling system, wherein the domain name resolution request of the scheduling system includes a self-resolvable domain name of the access network device;

[0038] Returning the service address of the access network device to the scheduling system;

[0039] The scheduling system is also used to:

[0040] The service status of the access network device is detected according to the service address of the access network device.

[0041] In some possible implementations, the service status includes a domain name resolution service DNS status, and the scheduling system is specifically used to:

[0042] Comparing the service address of the access network device returned by the domain name system with the current service address of the access network device;

[0043] When the service address of the access network device returned by the domain name system is consistent with the current service address of the access network device, it is determined that the DNS status of the access network device is normal; when the service address of the access network device returned by the domain name system is inconsistent with the current service address of the access network device, it is determined that the DNS status of the access network device is abnormal.

[0044] In some possible implementations, the service status includes a Hypertext Transfer Protocol Secure HTTPS service status, and the scheduling system is specifically used to:

[0045] Initiate an HTTPS service dial test request to the access network device;

[0046] When the dial test response is successful, it is determined that the HTTPS service of the access network device is normal; when the dial test response fails, it is determined that the HTTPS service of the access network device is abnormal.

[0047] In some possible implementations, the scheduling system is further used to:

[0048] Receiving a heartbeat message from the access network device;

[0049] Check whether the service address of the access network device has changed according to the heartbeat message, and if so, update the self-resolving domain name of the access network device according to the mapping method between the self-resolving domain name and the service address.

[0050] In a third aspect, the present application provides a computing device cluster. The computing device cluster includes at least one computing device, and the at least one computing device includes at least one processor and at least one memory. The at least one processor and the at least one memory communicate with each other. The at least one processor is used to execute instructions stored in the at least one memory, so that the computing device or the computing device cluster executes the domain name management method as described in the first aspect or any implementation of the first aspect.

[0051] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, wherein the instructions instruct a computing device or a computing device cluster to execute the domain name management method described in the first aspect or any one of the implementations of the first aspect.

[0052] In a fifth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computing device or a computing device cluster, enables the computing device or the computing device cluster to execute the domain name management method described in the first aspect or any one of the implementations of the first aspect.

[0053] Based on the implementations provided in the above aspects, this application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical method of the embodiments of the present application, the drawings required for use in the embodiments are briefly introduced below.

[0055] Figure 1 A schematic diagram of domain name scheduling and resolution based on a domain name exclusive to an access network device provided in an embodiment of the present application;

[0056] Figure 2 A schematic diagram of the architecture of a domain name management system provided in an embodiment of the present application;

[0057] Figure 3 A schematic diagram of a device registration process provided in an embodiment of the present application;

[0058] Figure 4 A schematic diagram of a process flow for detecting the service status of a device provided in an embodiment of the present application;

[0059] Figure 5 A flowchart of a domain name management method provided in an embodiment of the present application;

[0060] Figure 6 A schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0061] Figure 7 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0062] Figure 8 A schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application;

[0063] Fig. 9 A schematic diagram of the structure of another computer cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0064] The terms "first" and "second" in the embodiments of the present application are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features.

[0065] First, some technical terms involved in the embodiments of the present application are introduced.

[0066] A domain name, also known as a domain name (Domain Name, abbreviated as Domain) or a domain, is the name of a computer or a group of computers on the Internet consisting of a string of characters separated by dots, which is used to identify the electronic location of the computer during data transmission. A domain name can be regarded as a synonym for a service address, such as an Internet protocol (IP) address, to facilitate memorization of the latter. For example, abc.org or xyz.com is a domain name. Users can directly access abc.org or xyz.com instead of an IP address, and then the Domain Name System (DNS) can convert the domain name in the access request into an IP address that is easy for the machine to recognize. In this way, users only need to remember abc.org or xyz.com, a string of characters with special meanings, instead of meaningless numbers.

[0067] Domain Name System (DNS) is a service of the Internet. It is usually a distributed database that maps domain names and IP addresses to each other, enabling users to access the Internet more conveniently. DNS can usually provide resolution services, including forward resolution or reverse resolution. Among them, forward resolution can be the process of finding the IP address corresponding to a domain name, and reverse resolution can be the process of finding the domain name corresponding to an IP address. DNS can include authoritative DNS (or authoritative DNS server) and recursive DNS (also called local DNS, local DNS server).

[0068] Authoritative DNS is a system on the DNS server side that stores authoritative information about the corresponding domain name and has authoritative records for a specific domain. Authoritative DNS is unique within a specific region and is responsible for the correspondence between domain names and IP addresses within that region. Authoritative DNS is a reference point for IP addresses and other DNS data, and can provide answers to local DNS about the location of a website.

[0069] The local DNS is responsible for receiving the user's domain name query request (domain name resolution request) and returning the result to the user. The local DNS can cache the result to avoid repeated upward queries (such as repeated queries to the authoritative DNS). The local DNS can usually obtain the result through recursive query. Recursive query means that when the result is not cached locally, the result is obtained by querying other servers and then returning the result to the user.

[0070] In order to provide a better access experience, some websites also use CDN for acceleration. Specifically, website maintenance personnel only need to inject website content into the CDN system, and distribute it across the entire network through servers deployed by CDN in various physical locations, so as to achieve full network coverage across operators and regions. The bandwidth cost of CDN is relatively high. CDN operators can usually access a large number of access network devices (such as ONTs, routers, etc.) close to users. The bandwidth cost of access network devices is relatively low and can be used to offload high-cost bandwidth traffic from CDN. As customers pay more and more attention to network security, the proportion of HTTPS traffic on CDN is also gradually increasing. How to offload the HTTPS traffic of CDN to access network devices with equal security is also a key point currently faced.

[0071] In order to ensure that the entire user service link is covered by HTTPS transmission, the relevant technology applies for a wildcard domain name and its related certificates, assigns a dedicated domain name to all access network devices based on the wildcard domain name, and registers the dedicated domain name resolution to the service address (usually an IP address) of the access network device with the authoritative DNS server. When the service address of the access network device changes (the operator system generally triggers a redial to change the service IP address for dial-up Internet access in about 2 days), the dedicated domain name resolution record of the access network device is updated.

[0072] Figure 1 The schematic diagram shows a domain name scheduling and resolution based on the exclusive domain name of the access network device. When scheduling HTTPS traffic (such as HTTPS requests), the scheduling system uses the exclusive domain name of the access network device to schedule the user's HTTPS request to the HTTPS service address of the access network device. Specifically, the user first queries the IP address corresponding to the exclusive domain name of the access network device through the Local DNS proxy to the authoritative DNS, and then securely obtains content from the access network device through the HTTPS channel based on the IP address.

[0073] However, the number of exclusive domain names of massive access network devices can reach hundreds of millions, which increases the difficulty and cost of maintaining exclusive domain name resolution records. In addition, due to changes in IP addresses, exclusive domain name resolution records need to be updated frequently, which further increases the difficulty and cost of maintaining exclusive domain name resolution records. This has a great impact on authoritative DNS and is difficult to meet business needs.

[0074] In view of this, the present application provides a domain name management method. The method is executed by a domain name management system. The domain name management system can be a software system, which can be deployed in a computing device cluster, and the computing device cluster executes the program code of the software system to execute the domain name management method of the present application. The domain name management system can also be a hardware system, such as a computing device cluster with a domain name management function, and when the computing device cluster is running, the domain name management method of the present application is executed.

[0075] Specifically, the domain name management system includes a domain name system and a scheduling system. The scheduling system receives an access request from a user, and the access request includes a service domain name. Then, the scheduling system determines a target device from multiple access network devices serving the service domain name based on the access request, and redirects the access request to the target device. The service status of the target device is normal. The domain name system receives a domain name resolution request from the user, and the domain name resolution request from the user is generated based on the redirection information. The domain name resolution request from the user includes a self-resolvable domain name of the target device. Then, the domain name system determines the service address of the target device based on a mapping method between the self-resolvable domain name and the service address (for example, an IP address) and the self-resolvable domain name of the target device. Then, the domain name system returns the service address of the target device, and the service address of the target device is used to access the target device.

[0076] This method introduces a self-resolving domain name to replace the exclusive domain name. The service address (such as IP address) of the access network device can be automatically converted to obtain the self-resolving domain name of the access network device. Conversely, the self-resolving domain name based on the access network device can be automatically converted to obtain the service address of the access network device. For the self-resolving domain name, there is no need to maintain a large number of domain name resolution records, nor is there a need to update the domain name resolution record when the service address changes, which greatly reduces the maintenance difficulty and maintenance cost, reduces the impact on the domain name system such as the authoritative DNS, and can meet business needs. Moreover, after the introduction of the self-resolving domain name, the dispatching system and the authoritative DNS can achieve self-resolution based on the mapping method of the self-resolving domain name and the service address (also known as the self-resolving domain name rule), eliminating the dependence between the dispatching center and the authoritative DNS.

[0077] In order to make the technical solution of the present application clearer and easier to understand, the system architecture of the present application is introduced below with reference to the accompanying drawings.

[0078] See also Figure 2 The schematic diagram of the architecture of a domain name management system is shown, and the domain name management system 10 includes a domain name system 100 and a scheduling system 200. The domain name system 100 includes an authoritative DNS and a local DNS.

[0079] The scheduling system 200 is used to receive an access request from a user (such as a browser or client), and the access request includes a business domain name. Among them, the business domain name may include a uniform resource locator (URL). The access request is used to access the content corresponding to the URL (for example, a network resource). In a specific implementation, the access request may be a request based on HTTPS to access the content corresponding to the URL, that is, an HTTPS request. It should be noted that an HTTPS request is only an example of an access request. In other possible implementations of the present application, the access request may also be other types of requests for accessing network resources, such as an HTTP request.

[0080] Furthermore, the user can send an access request to the CDN edge node. The CDN edge node can send the access request to the scheduling system 200 for scheduling query, thereby querying the access network device that can be scheduled to achieve traffic unloading. Traffic unloading can be to schedule the access request (such as an HTTPS request) to the access network device, and the access network device responds.

[0081] The scheduling system 200 is also used to determine the target device from multiple access network devices serving the business domain name according to the access request, and redirect the access request to the target device. The service status of the target device is normal. The scheduling system 200 redirects the access request to the target device by returning redirection information to the user. Redirection means that when a user (such as a browser or client) requests a network resource corresponding to a URL, the server (such as the scheduling system 200) returns a redirection instruction, indicating that the URL has changed, and the user can resend a new request using the new URL. The redirection information may include the above-mentioned redirection instruction, and the redirection information may indicate the self-resolving domain name of the target device.

[0082] The domain name system 100 is used to receive a domain name resolution request from a user. The domain name resolution request from a user may be generated based on redirection information. For example, the domain name resolution request from a user includes a self-resolving domain name of a target device. Specifically, a user may first send a domain name resolution request to a local DNS in the domain name system 100. The local DNS queries the cache. When the cache does not include the service address corresponding to the self-resolving domain name, the local DNS sends the domain name resolution request from the user to the authoritative DNS in the domain name system 100. In this way, the domain name system 100 may receive the domain name resolution request from the user.

[0083] The domain name system 100 is also used to determine the service address of the target device according to the mapping method of the self-resolving domain name and the service address and the self-resolving domain name of the target device. The mapping method of the self-resolving domain name and the service address can be characterized by a self-resolving domain name conversion rule. In some examples, the mapping method of the self-resolving domain name and the service address (self-resolving domain name conversion rule) includes at least one of base conversion or string conversion. Base conversion includes but is not limited to decimal integer conversion or hexadecimal integer conversion.

[0084] The domain name system 100 is also used to return the service address of the target device, and the service address of the target device is used to access the target device. The domain name system 100 can return the service address of the target device to the user, so that the user can access the network resources of the target device according to the service address (such as IP address) of the target device. In specific implementation, the authoritative DNS in the domain name system 100 can send the service address of the target device to the local DNS, and the local DNS returns the service address of the target device to the user. The service address is used to access the target device. Figure 2 As shown, the user can re-initiate an access request (such as an HTTPS request) to the target device according to the service address of the target device returned by the domain name system 100 to obtain the corresponding resources.

[0085] In some possible implementations, the scheduling system 200 is also used to register or manage the access network device to schedule the access request to the access network device. For example, the scheduling system 200 can receive a registration request from the access network device, and can obtain the service address (such as IP address) of the access network device according to the registration request. Based on the mapping method of the self-resolving domain name and the service address (self-resolving domain name conversion rule) and the above service address, the self-resolving domain name of the access network device can be generated. Furthermore, the scheduling system 200 can also receive the heartbeat message of the access network device to detect the health status of the access network device or detect whether the service address of the access network device has changed.

[0086] The above describes the overall architecture from the perspectives of the domain name system 100 and the scheduling system 200. The following describes the domain name management system from the perspective of functional modularization.

[0087] like Figure 1As shown, the domain name management system 10 includes a configuration module 1002 and a domain name resolution module 1004. The configuration module 1002 and the domain name resolution module 1004 can be modules in the domain name system 100, or modules deployed in the domain name system 100 (for example, modules deployed in an authoritative DNS). Among them, the configuration module 1002 is used to configure the mapping method of the self-resolving domain name and the service address, for example, to configure the self-resolving domain name conversion rule, and the domain name resolution module 1004 is used to determine the service address of the access network device according to the mapping method of the self-resolving domain name and the service address and the self-resolving domain name of the access network device.

[0088] The domain name management system 10 may further include a configuration module 2002 and a domain name scheduling module 2004. Similarly, the configuration module 2002 and the domain name scheduling module 2004 may be modules in the scheduling system 200, or modules deployed in the scheduling system 200. The configuration module 2002 is used to configure a mapping method between a self-resolving domain name and a service address, such as configuring a self-resolving domain name conversion rule, and the domain name scheduling module 2004 is used to return a self-resolving domain name of an access network device to schedule an access request to the access network device.

[0089] In the technical solution of the present application, the domain name system 100 does not need to maintain a large number of dedicated device domain name resolution records, but can achieve real-time self-resolution based on the mapping method of the self-resolving domain name and the service address. Even if the service address changes, the scheduling system 200 can also update the self-resolving domain name in real time according to the above mapping method, and the domain name system 100 can perform real-time resolution based on the updated self-resolving domain name, thereby solving the problem of difficult maintenance of domain name resolution records, high update costs, and a large impact on authoritative DNS. Moreover, the self-resolving domain name introduced in the present application is generated according to the service address, is unique, and avoids domain name redundancy.

[0090] In addition, when the IP address of the access network device changes, the solution based on the exclusive domain name requires the access network device to remain silent for a period of time. Even if the authoritative DNS resolution record is updated in real time, the access network device still cannot provide services before the Local DNS cache expires. The access network device of the solution of this application does not need to be silent and can continue to provide services.

[0091] Based on the domain name management system 10 of the aforementioned embodiment, the domain name management method of the present application is introduced in combination with the embodiment. Among them, domain name management includes domain name scheduling and domain name resolution. Among them, the access network device can be registered first to enable the domain name system to schedule the access request to the access network device.

[0092] See also Figure 3 The schematic diagram of a device registration process shown includes the following steps:

[0093] S302, the scheduling system 200 configures a mapping method between a self-resolving domain name and a service address.

[0094] A self-resolving domain name is a domain name that can achieve self-resolving. In some possible implementations, the self-resolving domain name includes a domain name prefix and a fixed domain name suffix. The domain name prefix is ​​generated according to the service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name, such as a self-resolving wildcard domain name. Equipment scheduling, resolution, and services (including certificates) are all based on this wildcard domain name. This application provides an example of a self-resolving wildcard domain name, such as *.self-resolve.com. Among them, * can be a wildcard.

[0095] The mapping method of the self-resolving domain name and the service address is a reversible mapping method. In other words, based on the mapping method, the service address corresponding to the self-resolving domain name can be determined, and based on the mapping method, the self-resolving domain name corresponding to the service address can also be determined. In some possible implementations, the mapping method of the self-resolving domain name and the service address includes but is not limited to base conversion or string conversion. Among them, the base conversion can be a decimal integer conversion, or a hexadecimal integer conversion.

[0096] For ease of understanding, an example is given below. As shown in the following table:

[0097] Table 1

[0098]

[0099] Among them, the scheduling system 200 can receive the mapping method of the self-resolving domain name and the service address configured by the administrator or operation and maintenance personnel, such as the decimal integer conversion, hexadecimal integer conversion or string conversion in Table 1. Among them, the string conversion in Table 1 is to replace the character "." with "-". In other possible implementation methods of the embodiment of the present application, it can also be other characters, or the "." can be directly removed to achieve the string conversion.

[0100] S304 . The access network device sends a registration request to the scheduling system 200 .

[0101] The registration request is used to register the access network device in the scheduling system so that the traffic of the CDN can be unloaded. The registration request may carry the service address of the access network device. Specifically, the message header or message header of the registration request carries the source address, which may include the service address of the access network device. The service address of the access network device includes but is not limited to the IP address.

[0102] S306. The scheduling system 200 generates a self-resolvable domain name for the access network device according to the mapping method between the self-resolvable domain name and the service address and the service address of the access network device.

[0103] The scheduling system 200 can map the service address of the access network device according to the mapping method of the self-resolving domain name and the service address, thereby generating a self-resolving domain name of the access network device. In some possible implementations, the domain name suffix of the self-resolving domain name is fixed, and the scheduling system 200 can map the service address of the access network device according to the mapping method of the self-resolving domain name and the service address, obtain the domain name prefix, and then concatenate the domain name prefix and the domain name suffix to obtain the self-resolving domain name.

[0104] For example, the mapping method of the self-resolving domain name and service address configured by the scheduling system 200 is decimal integer conversion. The scheduling system 200 resolves the registration request to obtain the service address (IP address) of the access network device as 120.233.179.117, and performs a decimal integer conversion on the above service address to obtain the domain name prefix, specifically 2028581749. The scheduling system can assemble the domain name prefix and the domain name suffix to obtain the self-resolving domain name "2028581749.self-resolve.com".

[0105] S308 . The access network device sends a heartbeat message to the scheduling system 200 .

[0106] Considering that the service address of the access network device may change, for example, in a dial-up Internet access scenario, the operator may update the service address of the access network device periodically or irregularly. Based on this, the access network device may send a heartbeat message to the scheduling system 200. The access network device may periodically report the heartbeat message to the scheduling system 200, for example, the access network device may maintain a timer and periodically report the heartbeat message based on the timer.

[0107] S310, the scheduling system 200 checks whether the service address of the access network device has changed according to the heartbeat message. If yes, execute S312.

[0108] Specifically, the scheduling system 200 can parse the heartbeat message, for example, parse the message header of the heartbeat message, obtain the current service address of the access network device, and then compare the current service address with the service address of the access network device obtained most recently (from the registration request or the most recent heartbeat message), thereby determining whether the service address has changed. If the current service address is inconsistent with the service address of the access network device obtained most recently, it means that the service address of the access network device has changed.

[0109] S312. The scheduling system 200 updates the self-resolvable domain name of the access network device according to the mapping method between the self-resolvable domain name and the service address.

[0110] The scheduling system can map the current service address of the access network device according to the mapping method of the self-resolving domain name and the service address to update the self-resolving domain name of the access network device. The specific implementation of the scheduling system 200 updating the self-resolving domain name can refer to the description of the related content of generating the self-resolving domain name, which will not be repeated here.

[0111] It should be noted that the above S302 is a pre-processing step. After the configuration is completed, domain name resolution services can be provided for different users based on the configured mapping method, or domain name resolution services can be provided for multiple domain name resolution requests of the same user. In addition, the above S308 to S312 are optional steps of the embodiment of the present application, and the method of the present application may not perform S308 to S312.

[0112] Based on the above method steps, the access network device can be registered with the scheduling system 200, and the scheduling system 200 can schedule access requests to access CDN edge nodes to the access network device, thereby reducing CDN bandwidth costs.

[0113] In order to ensure the scheduling effect, the scheduling system 200 can perceive the service status (also called service health status) of the access network device in real time, including at least one of the domain name resolution service DNS status and HTTPS service status, so as to provide a scheduling decision during service scheduling, and the scheduling decision indicates to which access network device the access request (such as HTTPS request) is scheduled. Among them, the scheduling system 200 can perform health dialing tests on the access network device at regular intervals to perceive the service health status of the access network device.

[0114] See also Figure 4 The schematic diagram of a process flow of detecting the service status of a device shown includes the following steps:

[0115] S402: The domain name system 100 configures a mapping method between a self-resolving domain name and a service address.

[0116] Specifically, the authoritative DNS in the domain name system can configure the mapping method of the self-resolving domain name and the service address, that is, the self-resolving domain name conversion rule. In specific implementation, the authoritative DNS can receive the above self-resolving domain name conversion rules configured by the administrator or operation and maintenance personnel, thereby configuring the mapping method of the self-resolving domain name and the service address.

[0117] It should be noted that the configuration of the mapping method of the self-resolving domain name and the service address in the authoritative DNS precedes the configuration of the mapping method of the self-resolving domain name and the service address in the scheduling system 200. Similar to S302, the above S402 is a preprocessing step. After the configuration is completed, domain name resolution can be performed for different access network devices based on the configured mapping method of the self-resolving domain name and the service address, thereby realizing service status detection of different access network devices, or for the same access network device, domain name resolution can be performed for it in different time periods based on the configured mapping method of the self-resolving domain name and the service address, thereby realizing service status detection of the access network device in different time periods.

[0118] S404: The scheduling system 200 sends a domain name resolution request to the domain name system 100.

[0119] Specifically, the scheduling system 200 may send a domain name resolution request to the authoritative DNS of the domain name system 100. The domain name resolution request includes a self-resolving domain name generated by the scheduling system 200 according to the service address of the access network device.

[0120] S406: The domain name system 100 determines the service address corresponding to the self-resolvable domain name based on the mapping method between the self-resolvable domain name and the service address.

[0121] Specifically, the authoritative DNS in the domain name system 100 can map the self-resolving domain name according to the mapping method of the self-resolving domain name and the service address, so as to obtain the service address corresponding to the self-resolving domain name. Among them, the self-resolving domain name includes a domain name prefix and a fixed domain name suffix. The domain name system 100 (for example, the authoritative DNS) can extract the domain name prefix from the self-resolving domain name of the access network device, reversely map the domain name prefix according to the mapping method of the self-resolving domain name and the service address, and obtain the service address of the access network device.

[0122] For ease of understanding, an example is provided below. In this example, the self-resolving domain name may be 2028581749.self-resolve.com, and the mapping method between the self-resolving domain name and the service address configured by the domain name system 100 may be a decimal integer conversion. The authoritative DNS of the domain name system 100 may extract the domain name prefix "2028581749" from the self-resolving domain name, and then reversely map the domain name prefix "2028581749" based on the decimal integer conversion to obtain the service address "120.233.179.117".

[0123] In actual application, in order to facilitate reverse mapping, the domain name system 100 can also first convert the above decimal into binary, and then obtain the binary representation of each segment address through bit shifting. The domain name system 100 can also convert the binary representation of each segment address into a decimal representation, thereby obtaining a service address represented in dotted decimal form.

[0124] S408 : The domain name system 100 returns the resolved service address to the scheduling system 200 .

[0125] S410, the scheduling system 200 verifies the service address obtained by resolution and obtains the domain name resolution service status.

[0126] Specifically, the scheduling system 200 can compare the service address obtained by resolution (i.e., the service address of the access network device returned by the domain name system) with the current service address of the access network device (e.g., the service address obtained by resolving the heartbeat message reported by the access network device). When the service address of the access network device returned by the domain name system is consistent with the current service address of the access network device, it means that the domain name resolution service status of the access network device is normal, that is, the domain name resolution service is in a healthy state. When the service address of the access network device returned by the domain name system is inconsistent with the current service address of the access network device, it means that the domain name resolution service status is abnormal, that is, the domain name resolution service is in an unhealthy state.

[0127] S412: The scheduling system 200 sends an HTTPS service dial test request to the access network device.

[0128] The HTTPS service dialing request may be a heartbeat message based on HTTPS, which is used to detect the status of the HTTPS service. The scheduling system 200 may periodically send a heartbeat message based on HTTPS to the access network device to perceive the service status of the HTTPS service in real time.

[0129] S414. The scheduling system 200 receives a dialing test response returned by the access network device.

[0130] The dial test response can be a heartbeat response based on HTTPS. The dial test response can include different response types, and different response types can represent different service states of the HTTPS service. For example, a successful dial test response represents that the service state of the HTTPS service is normal; a failed dial test response represents that the service state of the HTTPS service of the access network device is abnormal.

[0131] S416. The scheduling system 200 records the service status of the HTTPS service.

[0132] Specifically, the scheduling system 200 can determine the service status of the HTTPS service based on the reception of the heartbeat response. When the scheduling system 200 receives a heartbeat response based on HTTPS returned by the access network device within a set time, it indicates that the service status of the HTTPS service is normal, that is, the HTTPS service is in a healthy state. When the scheduling system 200 does not receive a heartbeat response based on HTTPS returned by the access network device within a set time (for example, S414 is not executed), it indicates that the service status of the HTTPS service is abnormal, that is, the HTTPS service is in an unhealthy state.

[0133] It should be noted that the above S404 to S410 are used to detect the service status of the domain name resolution service, and the above S412 to S416 are used to detect the service status of the HTTPS service. The above process can be decoupled. Based on this, the above S404 to S410 and S412 to S416 can be executed in parallel, or S404 to S410 and S412 to S416 can be executed in sequence according to the set order. In some possible implementations, if the service status of the domain name resolution service is detected to be abnormal, the service status detection of the HTTPS service can be terminated. Similarly, if the service status of the HTTPS service is detected to be abnormal, the service status detection of the domain name resolution service can also be terminated.

[0134] Based on the above embodiments, the present application provides a domain name management method, which supports domain name scheduling and domain name resolution. The domain name management method of the present application is described below in conjunction with the embodiments.

[0135] See also Figure 5 A flowchart of a domain name management method is shown, the method comprising:

[0136] S502: The scheduling system 200 receives an access request from a user.

[0137] The access request is used to request access to resources. The resources include but are not limited to text, images, tables, audio or video. The access request can be generated based on an access protocol or a data transmission protocol. In some possible implementations, the access request can use the HTTPS protocol to ensure security. In other words, the access request can be an HTTPS request. Among them, the access request can include a business domain name. Specifically, the access request includes a URL, which indicates the path of the content (network resource) requested to be accessed.

[0138] In some possible implementations, a user may send an access request to a CDN edge node to request access to resources of the CDN edge node. The CDN edge node may send the access request to the scheduling system 200 to schedule the access request to the access network device, thereby offloading traffic of the CDN edge node.

[0139] S504: The scheduling system 200 determines a target device from a plurality of access network devices serving the service domain name according to the access request.

[0140] In specific implementation, the scheduling system 200 can determine multiple access network devices serving the business domain name according to the access request, and detect the service status of at least one access network device among the multiple access network devices, including the service status of the domain name resolution or the service status of the HTTPS service. The scheduling system 200 can filter the access network devices with abnormal service status and determine the target device from the access network devices with normal service status. The service status of the target device is normal.

[0141] In some possible implementations, the scheduling system 200 may randomly select an access network device from the access network devices in normal service status as the target device. In other possible implementations, the scheduling system 200 may also determine the first access network device in normal service status detected as the target device.

[0142] S506: The scheduling system 200 redirects the access request to the target device.

[0143] Specifically, when the access request is an HTTPS request, the scheduling system 200 can redirect the access request to the above-mentioned target device through HTTPS 302.

[0144] In some possible implementations, the scheduling system 200 may return a redirection address, such as a redirection URL, to the CDN edge node. The CDN edge node returns a redirection instruction to the user, the redirection instruction including the redirection URL.

[0145] S508: The user sends a domain name resolution request to the domain name system 100.

[0146] Specifically, the user can obtain the self-resolving domain name of the target device according to the redirected URL. The user can send a domain name resolution request to the domain name system 100 according to the self-resolving domain name. The domain name resolution request includes the self-resolving domain name of the target device, which is used to request the service address corresponding to the self-resolving domain name.

[0147] S510: The domain name system 100 determines the service address of the target device according to the configured mapping method between the self-resolvable domain name and the service address and the self-resolvable domain name of the target device.

[0148] In specific implementation, the domain name resolution request may first reach the local DNS of the domain name system 100. When the local DNS does not cache the service address corresponding to the self-resolving domain name, the local DNS may send a domain name resolution request to the authoritative DNS. The authoritative DNS may map the self-resolving domain name in the domain name resolution request according to the configured mapping method of the self-resolving domain name and the service address, and determine the service address corresponding to the self-resolving domain name. The service address corresponding to the self-resolving domain name is the service address of the target device.

[0149] The specific implementation of the domain name system 100 determining the service address corresponding to the self-resolvable domain name according to the configured mapping method between the self-resolvable domain name and the service address can be found in the description of the related contents of the aforementioned embodiment, which will not be repeated here.

[0150] S512: The domain name system 100 returns the service address of the target device to the user.

[0151] Specifically, when the local DNS of the domain name system 100 has a service address (service address of the target device) corresponding to the self-resolving domain name in the cache, the local DNS can return the service address corresponding to the self-resolving domain name to the user; when the local DNS of the domain name system 100 does not have a service address corresponding to the self-resolving domain name in the cache, the local DNS can receive the service address corresponding to the self-resolving domain name returned by the authoritative DNS, and then return the service address corresponding to the self-resolving domain name to the user.

[0152] S514: The user sends an access request to the target device according to the service address.

[0153] S516: The target device returns an access response to the user.

[0154] Specifically, users can establish an HTTPS connection with the service address returned by the authoritative DNS to securely obtain content.

[0155] The above S502 to S506 are optional steps of the embodiment of the present application, and the domain name management method of the embodiment of the present application may not perform the above steps. For example, when the user knows the self-resolving domain name of the access network device, he can directly send a domain name resolution request to the domain name system 100 to perform domain name resolution. Similarly, the above S514 and S516 are optional steps of the embodiment of the present application, and the domain name management method of the embodiment of the present application may not perform the above steps.

[0156] Based on the above description, it can be known that the domain name management method of the present application introduces a self-resolving domain name to replace the exclusive domain name. The service address (such as IP address) of the access network device can be automatically converted to obtain the self-resolving domain name of the access network device. Conversely, the self-resolving domain name based on the access network device can be automatically converted to obtain the service address of the access network device. For self-resolving domain names, there is no need to maintain a large number of domain name resolution records, nor is there a need to update the domain name resolution records when the service address changes, which greatly reduces the maintenance difficulty and maintenance cost, reduces the impact on domain name systems such as authoritative DNS, and can meet business needs. Moreover, when the service address of the access network device changes, the access network device does not need to be silent and can provide services continuously and stably. In addition, this method can solve the problem of exclusive domain name redundancy and has high scalability.

[0157] Based on the aforementioned method embodiment, the present application also provides a domain name management system 10, such as Figure 2 As shown, the domain name management system 10 includes a domain name system 100 and a scheduling system 200 .

[0158] The scheduling system 200 is used to receive an access request from a user, the access request including a service domain name, and then determine a target device from multiple access network devices serving the service domain name according to the access request, and redirect the access request to the target device, and the service status of the target device is normal;

[0159] The domain name system 100 is used to receive a domain name resolution request from a user, the domain name resolution request from the user is generated according to the redirection information, and the domain name resolution request from the user includes a self-resolvable domain name of a target device;

[0160] The domain name system 100 is also used to determine the service address of the target device according to the mapping method between the self-resolving domain name and the service address and the self-resolving domain name of the target device, and return the service address of the target device, which is used to access the target device.

[0161] Exemplarily, the above-mentioned domain name system 100 and scheduling system 200 may be implemented by hardware or by software.

[0162] When implemented by software, the domain name system 100 and the scheduling system 200 may be applications running on a computing device. The application may be provided to users in the form of virtualized services. Virtualized services may include virtual machine (VM) services, bare metal server (BMS) services, and container services. Among them, VM services may be services that use virtualization technology to virtualize virtual machine (VM) resource pools on multiple physical hosts (such as computing devices) to provide users with VMs on demand for use. BMS services are services that virtualize BMS resource pools on multiple physical hosts to provide users with BMS on demand for use. Container services are services that virtualize container resource pools on multiple physical hosts to provide users with containers on demand for use. VM is a simulated virtual computer, that is, a logical computer. BMS is a high-performance computing service that can be elastically scalable, with computing performance that is no different from that of traditional physical machines, and has the characteristics of secure physical isolation. Containers are a kernel virtualization technology that can provide lightweight virtualization to achieve the purpose of isolating user space, processes, and resources. It should be understood that the VM service, BMS service and container service in the above-mentioned virtualization services are merely specific examples. In actual applications, the virtualization service may also be other lightweight or heavyweight virtualization services, which are not specifically limited here.

[0163] When implemented by hardware, the domain name system 100 and the scheduling system 200 may include at least one computing device, such as a server, etc. Alternatively, the domain name system 100 and the scheduling system 200 may also be implemented by using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0164] Similarly, the configuration module 1002 and the domain name resolution module 1004 in the domain name system 100 and the configuration module 2002 and the domain name scheduling module 2004 in the scheduling system 200 can also be implemented by software or by hardware. Among them, the configuration module 1002, the domain name resolution module 1004, the configuration module 2002, and the domain name scheduling module 2004 can be applications running on a computing device, such as a VM service or a container service. In some examples, the configuration module 1002, the domain name resolution module 1004, the configuration module 2002, and the domain name scheduling module 2004 can be hardware, such as a server.

[0165] In some possible implementations, the self-resolving domain name includes a domain name prefix and a fixed domain name suffix, the domain name prefix is ​​generated according to the service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name;

[0166] The domain name system 100 is specifically used for:

[0167] Extracting the domain name prefix from the self-resolvable domain name of the target device;

[0168] The domain name prefix is ​​reverse mapped according to the mapping method of the self-resolving domain name and the service address to obtain the service address of the target device.

[0169] In some possible implementations, the mapping method includes at least one of base conversion or string conversion.

[0170] In some possible implementations, the scheduling system 200 is further used to:

[0171] receiving a registration request of the access network device, wherein the registration request includes a service address of the access network device;

[0172] A self-resolving domain name of the access network device is generated according to a mapping method between the self-resolving domain name and the service address and the service address of the access network device.

[0173] In some possible implementations, the domain name system 100 is further used to:

[0174] Receiving a domain name resolution request of the scheduling system 200, wherein the domain name resolution request of the scheduling system 200 includes a self-resolvable domain name of the access network device;

[0175] Returning the service address of the access network device to the scheduling system 200;

[0176] The scheduling system 200 is also used for:

[0177] The service status of the access network device is detected according to the service address of the access network device.

[0178] In some possible implementations, the service status includes a domain name resolution service DNS status, and the scheduling system 200 is specifically used to:

[0179] Comparing the service address of the access network device returned by the domain name system 100 with the current service address of the access network device;

[0180] When the service address of the access network device returned by the domain name system 100 is consistent with the current service address of the access network device, it is determined that the DNS status of the access network device is normal; when the service address of the access network device returned by the domain name system is inconsistent with the current service address of the access network device, it is determined that the DNS status of the access network device is abnormal.

[0181] In some possible implementations, the service status includes a Hypertext Transfer Protocol Secure HTTPS service status, and the scheduling system is specifically used to:

[0182] Initiate an HTTPS service dial test request to the access network device;

[0183] When the dial test response is successful, it is determined that the HTTPS service of the access network device is normal; when the dial test response fails, it is determined that the HTTPS service of the access network device is abnormal.

[0184] In some possible implementations, the scheduling system 200 is further used to:

[0185] Receiving a heartbeat message from the access network device;

[0186] Check whether the service address of the access network device has changed according to the heartbeat message, and if so, update the self-resolving domain name of the access network device according to the mapping method between the self-resolving domain name and the service address.

[0187] The above describes the domain name management system 10 from the perspective of functional modularization. The following describes the domain name management system 10 of the present application from the perspective of hardware entity.

[0188] The present application also provides a computing device 600, which is used to implement the functions of the domain name management system 10, or to implement part of the functions of the domain name management system 10, such as implementing the functions of the domain name system 100, or implementing the functions of the scheduling system 200. Figure 6As shown, computing device 600 includes: bus 602, processor 604, memory 606 and communication interface 608. Processor 604, memory 606 and communication interface 608 communicate through bus 602. Computing device 600 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in computing device 600.

[0189] The bus 602 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 The bus 602 may include a path for transmitting information between various components of the computing device 600 (eg, the memory 606, the processor 604, and the communication interface 608).

[0190] The processor 604 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0191] The memory 606 may include a volatile memory, such as a random access memory (RAM). The memory 606 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD). The memory 606 stores executable program code, and the processor 604 executes the executable program code to implement the aforementioned domain name management method. Specifically, the memory 606 stores instructions for the domain name management system 10 to execute the domain name management method. In some examples, the memory 606 may store some instructions for the domain name management system 10 to execute the domain name management method, such as instructions for storing the method steps of the domain name management method executed by the domain name system 100, or instructions for storing the method steps of the domain name management method executed by the scheduling system 200.

[0192] The communication interface 608 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 600 and other devices or communication networks.

[0193] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0194] like Figure 7 As shown, the computing device cluster includes at least one computing device 600. The memory 606 in one or more computing devices 600 in the computing device cluster may store the same domain name management system 10 for executing the domain name management method.

[0195] In some possible implementations, one or more computing devices 600 in the computing device cluster may also be used to execute some instructions of the domain name management system 10 for executing the domain name management method. In other words, a combination of one or more computing devices 600 may jointly execute instructions of the domain name management system 10 for executing the domain name management method.

[0196] It should be noted that the memory 606 in different computing devices 600 in the computing device cluster may store different instructions for executing partial functions of the domain name management system 10 .

[0197] Figure 8 A possible implementation is shown. Figure 8 As shown, two computing devices 600A and 600B are connected via a communication interface 608. The memory in computing device 600A stores instructions for executing the functions of domain name system 100. The memory in computing device 600B stores instructions for executing the functions of scheduling system 200. In other words, the memories 606 of computing devices 600A and 600B jointly store instructions for domain name management system 10 to execute the domain name management method.

[0198] Figure 8 The connection mode between the computing device clusters shown can be considered that the domain name management method provided by the present application requires computing power to maintain the access network device and dispatch the access request to the access network device. Therefore, it is considered that the functions implemented by the scheduling system 200 are handed over to the computing device 600B for execution.

[0199] It should be understood that Figure 8The functions of the computing device 600A shown in FIG. 6A may also be completed by multiple computing devices 600. Similarly, the functions of the computing device 600B may also be completed by multiple computing devices 600.

[0200] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig. 9 A possible implementation is shown. Fig. 9 As shown, two computing devices 600C and 600D are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 606 in the computing device 600C stores instructions for executing the functions of the domain name system 100. At the same time, the memory 606 in the computing device 600D stores instructions for executing the functions of the scheduling system 200.

[0201] Fig. 9 The connection method between the computing device clusters shown can be considered to be that the domain name management method provided in this application requires computing power to maintain the access network equipment and schedule access requests to the access network equipment, so it is considered to hand over the functions implemented by the scheduling system 200 to the computing device 600D for execution.

[0202] It should be understood that Fig. 9 The functions of the computing device 600C shown in FIG. 6A may also be completed by multiple computing devices 600. Similarly, the functions of the computing device 600D may also be completed by multiple computing devices 600.

[0203] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned domain name management method applied to the domain name management system 10.

[0204] The embodiment of the present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computer device, the at least one computer device executes the above domain name management method.

[0205] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

1. A domain name management method, characterized in that: Applied to a domain name management system, the domain name management system includes a domain name system and a scheduling system, the method includes: The scheduling system receives an access request from a user, wherein the access request includes a business domain name; The scheduling system determines a target device from a plurality of access network devices serving the business domain name according to the access request, and redirects the access request to the target device, and the service status of the target device is normal; The domain name system receives a domain name resolution request of the user, the domain name resolution request of the user is generated according to the redirection information, and the domain name resolution request of the user includes a self-resolvable domain name of the target device; The domain name system determines the service address of the target device according to the mapping mode between the self-resolvable domain name and the service address and the self-resolvable domain name of the target device; The domain name system returns a service address of the target device, where the service address of the target device is used to access the target device.

2. The method according to claim 1, characterized in that: The self-resolving domain name includes a domain name prefix and a fixed domain name suffix, the domain name prefix is ​​generated according to the service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name; The domain name system determines the service address of the target device according to the mapping mode between the self-resolving domain name and the service address and the self-resolving domain name of the target device, including: The domain name system extracts the domain name prefix from the self-resolvable domain name of the target device; The domain name system reversely maps the domain name prefix according to the mapping method of the self-resolving domain name and the service address to obtain the service address of the target device.

3. The method according to claim 1 or 2, characterized in that: The mapping method includes at least one of base conversion and string conversion.

4. The method according to any one of claims 1 to 3, characterized in that: Before the scheduling system receives the user's access request, the method further includes: The scheduling system receives a registration request from the access network device, where the registration request includes a service address of the access network device; The scheduling system generates a self-resolving domain name of the access network device according to a mapping method between the self-resolving domain name and the service address and the service address of the access network device.

5. The method according to claim 4, characterized in that The method further comprises: The domain name system receives a domain name resolution request from the scheduling system, where the domain name resolution request from the scheduling system includes a self-resolvable domain name of the access network device; The domain name system returns the service address of the access network device to the scheduling system; The scheduling system detects the service status of the access network device according to the service address of the access network device.

6. The method according to claim 5, characterized in that The service status includes a domain name resolution service DNS status, and the scheduling system detects the service status of the access network device according to the service address of the access network device, including: The scheduling system compares the service address of the access network device returned by the domain name system with the current service address of the access network device; When the service address of the access network device returned by the domain name system is consistent with the current service address of the access network device, the scheduling system determines that the DNS status of the access network device is normal; when the service address of the access network device returned by the domain name system is inconsistent with the current service address of the access network device, the scheduling system determines that the DNS status of the access network device is abnormal.

7. The method according to claim 5, characterized in that The service status includes a Hypertext Transfer Protocol Security (HTTPS) service status, and the scheduling system detects the service status of the access network device according to the service address of the access network device, including: The scheduling system initiates an HTTPS service dial test request to the access network device; When the dial test response is successful, the scheduling system determines that the HTTPS service of the access network device is normal; when the dial test response fails, the scheduling system determines that the HTTPS service of the access network device is abnormal.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The scheduling system receives the heartbeat message of the access network device; The scheduling system checks whether the service address of the access network device has changed according to the heartbeat message, and if so, updates the self-resolving domain name of the access network device according to the mapping method between the self-resolving domain name and the service address.

9. A domain name management system, characterized in that: The domain name management system comprises: The scheduling system is used to receive an access request from a user, the access request including a service domain name, determine a target device from a plurality of access network devices serving the service domain name according to the access request, and redirect the access request to the target device, wherein the service status of the target device is normal; A domain name system, used to receive a domain name resolution request of the user, the domain name resolution request of the user is generated according to the redirection information, and the domain name resolution request of the user includes a self-resolvable domain name of the target device; The domain name system is also used to determine the service address of the target device according to the mapping method of the self-resolving domain name and the service address and the self-resolving domain name of the target device, and return the service address of the target device, and the service address of the target device is used to access the target device.

10. The system according to claim 9, characterized in that The self-resolving domain name includes a domain name prefix and a fixed domain name suffix, the domain name prefix is ​​generated according to the service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name; The domain name system is specifically used for: Extracting the domain name prefix from the self-resolvable domain name of the target device; The domain name prefix is ​​reverse mapped according to the mapping method of the self-resolving domain name and the service address to obtain the service address of the target device.

11. The system according to claim 9 or 10, characterized in that: The mapping method includes at least one of base conversion and string conversion.

12. The system according to any one of claims 9 to 11, characterized in that The scheduling system is also used to: receiving a registration request of the access network device, wherein the registration request includes a service address of the access network device; A self-resolving domain name of the access network device is generated according to a mapping method between the self-resolving domain name and the service address and the service address of the access network device.

13. The system according to claim 12, characterized in that The Domain Name System is also used for: receiving a domain name resolution request of the scheduling system, wherein the domain name resolution request of the scheduling system includes a self-resolvable domain name of the access network device; Returning the service address of the access network device to the scheduling system; The scheduling system is also used to: The service status of the access network device is detected according to the service address of the access network device.

14. The system according to claim 13, characterized in that The service status includes a domain name resolution service DNS status, and the scheduling system is specifically used for: Comparing the service address of the access network device returned by the domain name system with the current service address of the access network device; When the service address of the access network device returned by the domain name system is consistent with the current service address of the access network device, it is determined that the DNS status of the access network device is normal; When the service address of the access network device returned by the domain name system is inconsistent with the current service address of the access network device, it is determined that the DNS state of the access network device is abnormal.

15. The system according to claim 13, characterized in that The service status includes a Hypertext Transfer Protocol Secure HTTPS service status, and the scheduling system is specifically used for: Initiate an HTTPS service dial test request to the access network device; When the dial test response is successful, it is determined that the HTTPS service of the access network device is normal; when the dial test response fails, it is determined that the HTTPS service of the access network device is abnormal.

16. The system according to any one of claims 9 to 15, characterized in that The scheduling system is also used to: Receiving a heartbeat message from the access network device; Check whether the service address of the access network device has changed according to the heartbeat message, and if so, update the self-resolving domain name of the access network device according to the mapping method between the self-resolving domain name and the service address.

17. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, and the at least one computing device includes at least one processor and at least one memory, wherein the at least one memory stores computer-readable instructions; the at least one processor executes the computer-readable instructions so that the computing device cluster executes the method as described in any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that: The method comprises computer-readable instructions; the computer-readable instructions are used to implement the method according to any one of claims 1 to 8.

19. A computer program product, characterized in that The method comprises computer-readable instructions; the computer-readable instructions are used to implement the method according to any one of claims 1 to 8.

Images