Domain name management method and related device

Abstract

Provided in the present application is 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. The method comprises: a scheduling system receiving an access request of a user, wherein the access request comprises a service domain name; according to the access request, the scheduling system determining a target device from a plurality of access network devices served by the service domain name, and redirecting the access request to the target device having a normal service state; a domain name system receiving a domain name resolution request of the user, wherein the domain name resolution request of the user is generated according to redirection information and comprises a self-resolving domain name of the target device; the domain name system determining a service address of the target device according to the manner in which the self-resolving domain name and the service address are mapped, and the self-resolving domain name of the target device; and the domain name system returning the service address of the target device for the user to access the target device. In the method, the self-resolving domain name is introduced, without the need to maintain massive domain name resolution records, thus reducing the maintenance difficulty and costs.

Description

Domain name management method and related equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on June 15, 2023, with application number 202310714537.3, and with the invention name “A domain name management method and related equipment”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 8, 2023, with application number 202311162888.4, and with the invention name “A domain name management method and related equipment”, the entire contents of which are incorporated by reference into 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] A Content Delivery Network (CDN) is a technology that distributes source site content to nodes in different regions, thereby reducing latency for users in different regions to access content and improving website responsiveness and availability. Using a CDN greatly simplifies website system maintenance. Website maintainers simply inject website content into the CDN system, which then distributes it across the entire network using servers deployed in various physical locations. This allows for full network coverage across carriers and regions.

[0004] CDN operators have high bandwidth costs, often accounting for over 80% of total costs. To reduce costs, CDN operators can offload high-cost bandwidth traffic by integrating a large number of access network devices close to users, such as optical network terminals (ONTs) and routers.

[0005] For security reasons, more and more services are adopting Hypertext Transfer Protocol Secure (HTTPS) for data transmission, generating HTTPS traffic. To securely offload HTTPS traffic from CDNs to access network devices, the industry has proposed an offload solution based on dedicated domain names. When dispatching HTTPS traffic, the dispatch system uses the dedicated domain name of the access network device to dispatch user HTTPS requests to the HTTPS service address of the access network device.

[0006] However, when the service address of an access network device changes (for example, operators typically trigger a redial change every two days for dial-up Internet access), the dedicated domain name resolution records for the access network device need to be updated. The number of dedicated domain names for massive access network devices can reach hundreds of millions, making dedicated domain name resolution records difficult to maintain and frequently updated. This significantly impacts the authoritative domain name server, making it difficult to meet business needs.

[0007] Summary of the Invention

[0008] The present application provides a domain name management method that introduces self-resolving domain names instead of dedicated domain names. Based on the service address (such as the IP address) of the access network device, the self-resolving domain name of the access network device can be automatically converted. Conversely, based on the self-resolving domain name of the access network device, the service address of the access network device can be automatically converted. 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 domain name resolution records when the service address changes. This greatly reduces the maintenance difficulty and maintenance cost, reduces the impact on domain name systems such as authoritative DNS, and can meet business needs. The present application also provides a domain name system, scheduling system, computing device cluster, computer-readable storage medium, and computer program product corresponding to the domain name management method.

[0009] In a first aspect, the present application provides a domain name management method. This method can be applied to a domain name management system. The domain name management system can be a software system that can be deployed in a computing device cluster. The computing device cluster executes the program code of the software system to implement 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 domain name management functions (such as domain name resolution and domain name scheduling). When the computing device cluster is running, it executes the domain name management method of the present application.

[0010] Specifically, the domain name management system includes a domain name system and a dispatching system. The dispatching system receives a user's access request, which includes a service domain name. Based on the access request, the dispatching system determines the target device from multiple access network devices serving the service domain name and redirects the access request to the target device. The target device's service status is normal. Based on the redirection information, the user can generate a domain name resolution request, which includes the target device's self-resolvable domain name. In response, the domain name system receives the user's domain name resolution request and, based on the mapping between the self-resolvable domain name and the service address and the target device's self-resolvable domain name, determines the target device's service address. The domain name system then returns the target device's service address, which is used to access the target device.

[0011] This method introduces self-resolving domain names to replace dedicated domain names. The service address of the access network device can be automatically converted to the self-resolving domain name of the access network device. Similarly, the self-resolving domain name of the access network device can be automatically converted to 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 domain name resolution records when the service address changes. This greatly reduces the maintenance difficulty and cost, reduces the impact on domain name systems such as authoritative DNS, and can meet business needs. Moreover, after the introduction of self-resolving domain names, the dispatching system and authoritative DNS can achieve self-resolution based on the mapping method of self-resolving domain names and service addresses, eliminating the dependence between the dispatching center and the authoritative DNS.

[0012] In some possible implementations, a self-resolving domain name includes a domain prefix and a fixed domain suffix. The domain prefix is ​​generated based on the service address mapping of the access network device, and the domain suffix is ​​a wildcard domain name. Accordingly, the domain name system can extract the domain prefix from the target device's self-resolving domain name and then perform a reverse mapping on the domain prefix based on the mapping between the self-resolving domain name and the service address to obtain the target device's service address.

[0013] 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 massive 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.

[0014] 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. This mapping method is reversible, laying the foundation for self-resolution of domain names. Both the domain name system and the dispatch system can implement self-resolution of domain names based on this mapping method, eliminating the need for the dispatch center to rely on the authoritative DNS.

[0015] In some possible implementations, before receiving the user's access request, the scheduling system 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 based on the mapping between the self-resolving domain name and the service address and the service address of the access network device.

[0016] This helps dispatch access requests to access network devices to achieve traffic offloading.

[0017] In some possible implementations, the domain name system may further receive a domain name resolution request from the scheduling system, the domain name resolution request from the scheduling system including the self-resolvable 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 based on the service address of the access network device.

[0018] 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.

[0019] 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.

[0020] 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.

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

[0022] 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.

[0023] In some possible implementations, the scheduling system may also receive heartbeat messages from the access network device. The scheduling system verifies whether the service address of the access network device has changed based on the heartbeat message. If so, the scheduling system updates the self-resolving domain name of the access network device based on the mapping method between the self-resolving domain name and the service address.

[0024] 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 updates of the self-resolving domain name and ensuring service quality.

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

[0026] a scheduling system configured 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 based on the access request, and redirect the access request to the target device, wherein the service status of the target device is normal;

[0027] A domain name system, configured to receive a domain name resolution request from the user, the domain name resolution request from the user being generated according to the redirection information, the domain name resolution request from the user including a self-resolvable domain name of the target device;

[0028] The domain name system is further used to determine the service address of the target device based on 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. The service address of the target device is used to access the target device.

[0029] 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 a service address mapping of the access network device, and the domain name suffix is ​​a wildcard domain name;

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

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

[0032] 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.

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

[0034] In some possible implementations, the scheduling system is further configured to:

[0035] receiving a registration request from the access network device, the registration request including a service address of the access network device;

[0036] 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.

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

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

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

[0040] The scheduling system is also used to:

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

[0042] In some possible implementations, the service status includes a domain name resolution service (DNS) status, and the scheduling system is specifically configured to:

[0043] 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;

[0044] 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.

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

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

[0047] 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.

[0048] In some possible implementations, the scheduling system is further configured to:

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

[0050] Check whether the service address of the access network device has changed according to the heartbeat message. 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.

[0051] In a third aspect, the present application provides a computing device cluster. The computing device cluster includes at least one computing device, each of which 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 configured to execute instructions stored in the at least one memory, causing the computing device or computing device cluster to perform the domain name management method described in the first aspect or any implementation of the first aspect.

[0052] 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 implementation of the first aspect.

[0053] In a fifth aspect, the present application provides a computer program product comprising instructions, which, when run on a computing device or a computing device cluster, enables the computing device or 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.

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

[0055] In order to more clearly illustrate the technical methods of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments.

[0056] FIG1 is a schematic diagram of domain name scheduling and resolution based on a dedicated domain name of an access network device according to an embodiment of the present application;

[0057] FIG2 is a schematic diagram of the architecture of a domain name management system provided in an embodiment of the present application;

[0058] FIG3 is a schematic diagram of a device registration process according to an embodiment of the present application;

[0059] FIG4 is a schematic diagram of a process for detecting the service status of a device according to an embodiment of the present application;

[0060] FIG5 is a flow chart of a domain name management method provided in an embodiment of the present application;

[0061] FIG6 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0062] FIG7 is a schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0063] FIG8 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application;

[0064] FIG9 is a schematic diagram of the structure of another computer cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] The terms "first" and "second" in the embodiments of this application are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. Therefore, features specified as "first" or "second" may explicitly or implicitly include one or more of the features.

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

[0067] A domain name, also known as a domain name (Domain Name, abbreviated as Domain) or a domain, is the name of a computer or group of computers on the Internet consisting of a string of characters separated by dots, used to identify the electronic location of the computer during data transmission. A domain name can be regarded as a alias 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 machines to recognize. In this way, users only need to remember a string of characters with special meanings, such as abc.org or xyz.com, instead of meaningless numbers.

[0068] The Domain Name System (DNS) is an internet service that typically serves as a distributed database that maps domain names to IP addresses, making internet access more convenient for users. DNS typically provides resolution services, including forward and reverse resolution. Forward resolution is the process of finding the IP address corresponding to a domain name, while reverse resolution is the process of finding the domain name corresponding to an IP address. DNS can include authoritative DNS (or authoritative DNS servers) and recursive DNS (also known as local DNS or local DNS servers).

[0069] An authoritative DNS is a system on the DNS server side that stores authoritative information about domain names and holds authoritative records for a specific domain. An authoritative DNS is unique within a specific region and is responsible for matching domain names with IP addresses within that region. The authoritative DNS serves as a reference point for IP addresses and other DNS data, providing answers to local DNS about website locations.

[0070] The local DNS is responsible for receiving domain name query requests (domain name resolution requests) from users and returning the results. The local DNS can cache the results to avoid repeated upward queries (for example, repeated queries to the authoritative DNS). The local DNS can typically obtain results through recursive queries. Recursive queries involve querying other servers for results when the local DNS doesn't have a cached result, and then returning the result to the user.

[0071] In order to provide a better access experience, some websites also use CDN for acceleration. Specifically, website maintenance personnel only need to inject the website content into the CDN system, and distribute it across the entire network through CDN servers deployed 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 the high-cost bandwidth traffic of 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.

[0072] To ensure HTTPS transmission coverage throughout the user service link, the relevant technology applies for a wildcard domain name and its associated certificate, assigns a dedicated domain name to all access network devices based on the wildcard domain name, and registers the dedicated domain name resolution with the authoritative DNS server to point to the service address of the access network device (usually an IP address). When the service address of the access network device changes (the operator system generally triggers a redial change of the service IP address every two days for dial-up Internet access), the dedicated domain name resolution record of the access network device is updated.

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

[0074] 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 frequently updated, 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.

[0075] In view of this, the present application provides a domain name management method. This method is performed by a domain name management system. The domain name management system can be a software system that can be deployed in a computing device cluster. The computing device cluster executes the program code of the software system to perform 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 domain name management capabilities. When the computing device cluster is running, it executes the domain name management method of the present application.

[0076] Specifically, the domain name management system includes a domain name system and a scheduling system. The scheduling system receives the user's access request, which includes the service domain name. Then, the scheduling system determines the 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 the user's domain name resolution request. The user's domain name resolution request is generated based on the redirection information. The user's domain name resolution request includes the self-resolving domain name of the target device. Then, the domain name system determines the service address of the target device based on the mapping method of the self-resolving domain name and the service address (for example, the IP address) and the self-resolving 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.

[0077] This method introduces a self-resolving domain name to replace the dedicated domain name. The service address (such as IP 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. This 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 scheduling 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 scheduling center and the authoritative DNS.

[0078] 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.

[0079] 2 shows a schematic diagram of the architecture of a domain name management system, 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.

[0080] 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. The business domain name may include a uniform resource locator (URL). The access request is used to access the content corresponding to the URL (such as a network resource). In a specific implementation, the access request may be a request to access the content corresponding to the URL based on HTTPS, 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.

[0081] Furthermore, users can send access requests to CDN edge nodes. The CDN edge nodes can send the access requests to the scheduling system 200 for scheduling queries, thereby querying the access network devices that can be scheduled to implement traffic offloading. Traffic offloading can be dispatching the access request (such as an HTTPS request) to the access network device, which then responds.

[0082] The scheduling system 200 is also used to determine the target device from multiple access network devices serving the business domain name based on 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.

[0083] The domain name system 100 is configured to receive domain name resolution requests from users. The domain name resolution requests from users may be generated based on redirection information. For example, the domain name resolution requests from users may include the self-resolvable domain name of the target device. Specifically, the user may first send a domain name resolution request to the local DNS in the domain name system 100. The local DNS queries the cache. If the cache does not contain the service address corresponding to the self-resolvable domain name, the local DNS sends the domain name resolution request to the authoritative DNS in the domain name system 100. In this manner, the domain name system 100 can receive the domain name resolution request from the user.

[0084] The domain name system 100 is further configured to determine the service address of the target device based on the mapping method between the self-resolving domain name and the service address and the self-resolving domain name of the target device. The mapping method between the self-resolving domain name and the service address can be represented by a self-resolving domain name conversion rule. In some examples, the mapping method between the self-resolving domain name and the service address (the 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.

[0085] The domain name system 100 is also used to return the service address of the target device, which is used to access the target device. Specifically, the domain name system 100 can return the service address of the target device to the user, allowing the user to access the network resources of the target device based on the service address (e.g., IP address) of the target device. In a specific implementation, the authoritative DNS in the domain name system 100 can send the service address of the target device to the local DNS, which then returns the service address of the target device to the user. This service address is used to access the target device. As shown in FIG2 , the user can re-initiate an access request (e.g., an HTTPS request) to the target device based on the service address of the target device returned by the domain name system 100 to obtain the corresponding resources.

[0086] In some possible implementations, the scheduling system 200 is also used to register or manage access network devices to dispatch access requests to the access network devices. For example, the scheduling system 200 can receive a registration request from an access network device, obtain the service address (e.g., IP address) of the access network device based on the registration request, and generate a self-resolving domain name for the access network device based on the mapping method between the self-resolving domain name and the service address (self-resolving domain name conversion rules) and the service address. Furthermore, the scheduling system 200 can also receive heartbeat messages from 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.

[0087] 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.

[0088] As shown in FIG1 , 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 (e.g., modules deployed in an authoritative DNS). The configuration module 1002 is used to configure the mapping method between the self-resolving domain name and the service address, such as configuring the self-resolving domain name conversion rules, and the domain name resolution module 1004 is used to determine the service address of the access network device based on the mapping method between the self-resolving domain name and the service address and the self-resolving domain name of the access network device.

[0089] 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 the mapping method between the self-resolving domain name and the service address, for example, to configure the self-resolving domain name conversion rules, and the domain name scheduling module 2004 is used to return the self-resolving domain name of the access network device to dispatch the access request to the access network device.

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

[0091] 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 will still not be able to 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.

[0092] Based on the domain name management system 10 of the aforementioned embodiment, the domain name management method of the present application is described below in conjunction with the embodiment. Domain name management includes domain name scheduling and domain name resolution. The access network device can first register so that the domain name system can dispatch access requests to the access network device.

[0093] FIG3 shows a schematic diagram of a device registration process, which includes the following steps:

[0094] S302: The scheduling system 200 configures a mapping method between a self-resolving domain name and a service address.

[0095] 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 based on 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. Device 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 character.

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

[0097] For easier understanding, the following is an example, as shown in the following table:

[0098] Table 1

[0099] The scheduling system 200 may receive a mapping method for a self-resolving domain name and a service address configured by an administrator or operation and maintenance personnel, such as a decimal integer conversion, a hexadecimal integer conversion, or a string conversion as shown in Table 1. The string conversion in Table 1 replaces the character "." with "-." In other possible implementations of the embodiments of the present application, other characters may be used, or the "." may be directly removed to achieve 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 with the dispatch system to offload CDN traffic. The registration request may include the service address of the access network device. Specifically, the registration request message header or packet header includes a 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, an IP address.

[0102] S306: The scheduling system 200 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.

[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 service address, thereby generating a self-resolving domain name for the access network device. In some possible implementations, the domain name suffix of the self-resolving domain name is fixed. 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 service address, obtain the domain name prefix, and then concatenate the domain name prefix and domain name suffix to obtain the self-resolving domain name.

[0104] For example, the scheduling system 200 configures a mapping method for self-resolving domain names and service addresses using decimal integer conversion. The scheduling system 200 resolves the registration request to obtain the service address (IP address) of the access network device, which is 120.233.179.117. The system then performs a decimal integer conversion on the service address to obtain the domain name prefix, specifically 2028581749. The scheduling system can assemble the domain name prefix and 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 an access network device may change, for example, in a dial-up Internet access scenario, the operator may periodically or irregularly update the service address of the access network device. 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 based on which the heartbeat message is periodically reported.

[0107] S310: The scheduling system 200 checks whether the service address of the access network device has changed based on the heartbeat message. If so, S312 is executed.

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

[0109] S312: The scheduling system 200 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.

[0110] The scheduling system can map the current service address of the access network device based on the mapping method between 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 be found in the description of generating the self-resolving domain name, and will not be repeated here.

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

[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 CDN edge nodes to the access network device, thereby reducing CDN bandwidth costs.

[0113] To ensure effective scheduling, the scheduling system 200 can sense the service status (also known as service health status) of access network devices in real time, including at least one of the domain name resolution service (DNS) status and the HTTPS service status, so as to provide scheduling decisions during service scheduling. The scheduling decision indicates to which access network device the access request (such as an HTTPS request) is to be dispatched. The scheduling system 200 can periodically perform health checks on the access network devices to sense the service health status of the access network devices.

[0114] Referring to FIG4 , a flow chart of service status detection of a device is shown, which includes the following steps:

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

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

[0117] It should be noted that the configuration of the mapping method of the self-resolving domain name and service address in the authoritative DNS precedes the configuration of the mapping method of the self-resolving domain name and service address in the scheduling system 200. Similar to S302, the above S402 is a pre-processing 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 service address, thereby realizing service status detection of different access network devices. Alternatively, 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 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 based on the mapping method between the self-resolving domain name and the service address, thereby obtaining the service address corresponding to the self-resolving domain name. The self-resolving domain name includes a domain name prefix and a fixed domain name suffix. The domain name system 100 (e.g., the authoritative DNS) can extract the domain name prefix from the self-resolving domain name of the access network device, and perform a reverse mapping on the domain name prefix based on the mapping method between the self-resolving domain name and the service address to obtain the service address of the access network device.

[0122] For ease of understanding, the following example illustrates this. In this example, the self-resolving domain name may be 2028581749.self-resolve.com. The mapping method between the self-resolving domain name and the service address configured by the domain name system 100 may be 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 perform a reverse mapping on 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 indicates 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 indicates 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 dial test request may be an HTTPS-based heartbeat message, which is used to detect the status of the HTTPS service. The scheduling system 200 may periodically send HTTPS-based heartbeat messages to the access network device to sense the service status of the HTTPS service in real time.

[0129] S414. The scheduling system 200 receives a dial 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, each of which can represent different service states of the HTTPS service. For example, a successful dial test response indicates that the HTTPS service state is normal; a failed dial test response indicates that the HTTPS service state 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 the HTTPS-based heartbeat response returned by the access network device within the 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 the HTTPS-based heartbeat response returned by the access network device within the 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] Referring to the flowchart of a domain name management method shown in FIG5 , the method includes:

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

[0137] An access request is used to request access to a resource. This resource includes, but is not limited to, text, images, tables, audio, or video. The access request may be generated based on an access protocol or a data transmission protocol. In some possible implementations, the access request may utilize the HTTPS protocol for security. In other words, the access request may be an HTTPS request. The access request may include a business domain name. Specifically, the access request includes a URL, which indicates the path to the content (network resource) requested for access.

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

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

[0140] In a specific implementation, the scheduling system 200 can determine multiple access network devices serving the service domain name based on the access request and detect the service status of at least one of the multiple access network devices, including the service status of the domain name resolution service or the service status of the HTTPS service. The scheduling system 200 can filter out 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 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 detected in normal service status 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 based on the redirected URL. The user can send a domain name resolution request to the domain name system 100 based on the self-resolving domain name. The domain name resolution request includes the self-resolving domain name of the target device and 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 a specific implementation, the domain name resolution request may first reach the local DNS of the domain name system 100. If the local DNS does not cache the service address corresponding to the self-resolving domain name, the local DNS may send the domain name resolution request to the authoritative DNS. The authoritative DNS may map the self-resolving domain name in the domain name resolution request based on the configured mapping method between 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 content of the above embodiment and 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 cached, 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 cached, 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] S502 to S506 described above are optional steps in the embodiment of the present application, and the domain name management method according to the embodiment of the present application may not perform these steps. For example, if a user knows the self-resolving domain name of the access network device, they can directly send a domain name resolution request to the domain name system 100 to perform domain name resolution. Similarly, S514 and S516 described above are optional steps in the embodiment of the present application, and the domain name management method according to the embodiment of the present application may not perform these steps.

[0156] Based on the above description, it can be seen 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. This 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 further provides a domain name management system 10 . As shown in FIG2 , the domain name management system 10 includes a domain name system 100 and a scheduling system 200 .

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

[0159] The domain name system 100 is configured to receive a domain name resolution request from a user, the domain name resolution request from the user being generated based on the redirection information, and the domain name resolution request from the user including 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 based on 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. The service address of the target device 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 software.

[0162] When implemented via software, the domain name system 100 and the scheduling system 200 can be applications running on a computing device. These applications can be provided to users as virtualized services. Virtualized services can include virtual machine (VM) services, bare metal server (BMS) services, and container services. VM services can use virtualization technology to create a virtual machine (VM) resource pool on multiple physical hosts (such as computing devices) to provide users with VMs on demand. BMS services use virtualized BMS resource pools on multiple physical hosts to provide users with BMSs on demand. Container services use virtualized container resource pools on multiple physical hosts to provide users with containers on demand. A VM is a simulated virtual computer, or logically a single computer. BMS is a scalable, high-performance computing service with computing performance comparable to traditional physical machines and secure physical isolation. Containers are a kernel virtualization technology that provides lightweight virtualization to isolate 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 through hardware, the domain name system 100 and the scheduling system 200 may include at least one computing device, such as a server. Alternatively, the domain name system 100 and the scheduling system 200 may be implemented 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 via software or hardware. Specifically, 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 a 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 configured to:

[0171] receiving a registration request from the access network device, the registration request including 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 configured to:

[0174] receiving a domain name resolution request from the scheduling system 200, where the domain name resolution request from the scheduling system 200 includes a self-resolving 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 configured 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 configured 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 configured 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. 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 domain name management system 10 is introduced from the perspective of functional modularization. The domain name management system 10 of the present application is introduced from the perspective of hardware implementation.

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

[0189] Bus 602 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG6 shows a single bus line, but this does not imply a single bus or type of bus. Bus 602 may include a path for transmitting information between various components of computing device 600 (e.g., memory 606, processor 604, and communication interface 608).

[0190] The processor 604 may include any one or more processors such as 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 the domain name system 100 to execute the method steps of the domain name management method, or instructions for the scheduling system 200 to execute the method steps of the domain name management method.

[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 a communication network.

[0193] Embodiments of the present application also provide 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 smartphone.

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

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

[0196] It should be noted that the memories 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 illustrates a possible implementation. As shown in Figure 8, 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 collectively store instructions for the domain name management system 10 to execute the domain name management method.

[0198] The connection method between the computing device clusters shown in Figure 8 can be considered to consider that the domain name management method provided by this application requires computing power to maintain access network devices and dispatch access requests to access network devices. Therefore, it is considered to hand over the functions implemented by the scheduling system 200 to the computing device 600B.

[0199] It should be understood that the functionality of the computing device 600A shown in FIG8 may also be implemented by multiple computing devices 600. Similarly, the functionality of the computing device 600B may also be implemented by multiple computing devices 600.

[0200] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network (WAN) or a local area network (LAN), among others. FIG. 9 illustrates one possible implementation. As shown in FIG. 9 , two computing devices 600C and 600D are connected via a network. Specifically, each computing device is connected to the network via a communication interface within the computing device. In this type of possible implementation, the memory 606 in computing device 600C stores instructions for executing the functions of the domain name system 100. Simultaneously, the memory 606 in computing device 600D stores instructions for executing the functions of the scheduling system 200.

[0201] The connection method between the computing device clusters shown in Figure 9 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] 9 may also be implemented by multiple computing devices 600. Similarly, the functionality of computing device 600D may also be implemented by multiple computing devices 600.

[0203] The present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of being 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 magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the domain name management method described above for use in the domain name management system 10.

[0204] The present application also provides a computer program product containing instructions. This computer program product can be software or a program product containing instructions that can be executed on a computing device or stored on any available medium. When executed on at least one computing device, this computer program product causes the at least one computing device to execute the aforementioned 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 deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the various 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 dispatching system verifies whether the service address of the access network device has changed according to the heartbeat message, and if so, The self-resolving domain name of the access network device is updated by mapping the 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