Domain name resolution method based on cloud computing technology and cloud management platform

Abstract

The invention discloses a domain name resolution method based on a cloud computing technology and a cloud management platform, and belongs to the technical field of cloud computing. The method is applied to a cloud management platform, and comprises the following steps: grouping a plurality of DNS servers to obtain a plurality of DNS server groups, the plurality of DNS servers being used for analyzing domain names in a target name area in a DNS name space; obtaining a plurality of domain name suffixes, wherein the plurality of domain name suffixes are suffixes of domain names in the target name area; generating a target mapping relation based on the plurality of domain name suffixes and the plurality of DNS server groups; and distributing a plurality of domain name suffixes to the corresponding DNS server group based on the target mapping relationship, so that the DNS server in the corresponding DNS server group analyzes the domain name resolution request when receiving the domain name resolution request. According to the method and the device, the DNS servers are flexibly grouped, and the DNS servers are scheduled by the groups to perform domain name resolution, so that the high availability of the domain name resolution service is ensured.

Description

[0001] This application claims priority to Chinese patent application No. 202311694790.3, filed on December 11, 2023, and entitled “A domain name configuration method and device based on load balancing”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of cloud computing technology, and in particular to a domain name resolution method and a cloud management platform based on cloud computing technology. Background Art

[0003] Domain name resolution is the process of converting a domain name into an Internet Protocol (IP) address, and the resolution work is completed by the Domain Name System (DNS) server. When a client initiates access to a domain name, the client first initiates a domain name query request to the local domain name server. If the local domain name server stores the IP address corresponding to the domain name, the IP address is returned to the client, and the domain name resolution process ends; if the local domain name server does not store the IP address corresponding to the domain name, the local domain name server replaces the client, and queries from the root domain name server to the top-level domain name server, and then to the authoritative domain name server step by step, and finally informs the client of the obtained IP address. From the above domain name resolution process, it can be seen that the authoritative domain name server plays a core role in the domain name resolution process, and it is responsible for resolving the IP address corresponding to the domain name.

[0004] In the related art, in order to ensure the high availability of domain name resolution services, a large number of DNS servers are usually deployed, and these DNS servers back up each other. Domain name resolution services are provided to the outside through these DNS servers. Even a large-scale distributed denial of service (DDoS) attack will not cause damage to the domain name resolution service.

[0005] However, deploying a large number of DNS servers will result in higher costs for domain name resolution services. Summary of the invention

[0006] The present application provides a domain name resolution method and a cloud management platform based on cloud computing technology, which can ensure the high availability of domain name resolution services by dividing DNS server groups when DNS server resources are limited. The technical solution is as follows.

[0007] In a first aspect, a domain name resolution method based on cloud computing technology is provided, which is applied to a cloud management platform. The method includes: grouping the multiple DNS servers to obtain multiple DNS server groups, where each DNS server group includes at least one DNS server, and there is at least one different DNS server between different DNS server groups. The multiple DNS servers are used to resolve domain names in a target name area in the DNS namespace; obtaining multiple domain name suffixes, where the multiple domain name suffixes are the suffixes of domain names in the target name area; generating a target mapping relationship based on the multiple domain name suffixes and the multiple DNS server groups, where the target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the multiple DNS server groups; and allocating the multiple domain name suffixes to the corresponding DNS server groups based on the target mapping relationship, so that when the DNS servers in the corresponding DNS server groups receive a domain name resolution request, they resolve the domain name resolution request.

[0008] It can be seen that for a limited number of DNS servers, the cloud management platform can, through reasonable grouping and generating a target mapping relationship, enable the multiple DNS servers to provide domain name resolution services based on this target mapping relationship and schedule the DNS servers for domain name resolution in groups. This can not only manage the domain name resolution service in a fine-grained manner but also reduce the blast radius of the domain name resolution service and improve the availability of the domain name resolution service.

[0009] Optionally, the grouping of the multiple DNS servers to obtain multiple DNS server groups includes: obtaining the total number of the multiple DNS servers and the server grouping size, where the server grouping size indicates the number of DNS servers divided into the same group; and grouping the multiple DNS servers by using the method of permutation and combination based on the total number of the multiple DNS servers and the server grouping size to obtain the multiple DNS server groups.

[0010] That is to say, by using the method of permutation and combination to group a limited number of multiple DNS servers, more server groups can be obtained. As the number of DNS server groups increases, the blast radius of the limited number of multiple DNS servers providing domain name resolution services becomes smaller.

[0011] Optionally, the cloud management platform is used to manage cloud infrastructure, and the cloud infrastructure includes the multiple DNS servers.

[0012] Optionally, if the multiple DNS servers are located in multiple Availability Zones (AZs) in the cloud infrastructure, and the server group size is greater than or equal to the total number of the multiple AZs, then each DNS server group includes at least one DNS server in each of the AZs.

[0013] That is to say, if multiple DNS servers are distributed in multiple AZs, then when dividing the DNS server groups, each DNS server group includes the DNS servers in each AZ. In this way, when each DNS server group resolves the domain names with the corresponding domain name suffixes, it can flexibly select the corresponding DNS server according to the communication distance, so as to improve the domain name resolution efficiency.

[0014] Optionally, if the multiple DNS servers are located in multiple regions in the cloud infrastructure, then the multiple regions correspond to the same virtual access address, and the domain name suffixes corresponding to the DNS server groups in the multiple regions are the same.

[0015] It can be seen that when resolving the domain names in the target DNS zone, the DNS servers in the multiple regions back up each other. For any domain name resolution request for a domain name belonging to the DNS zone, when it is forwarded to any one of the multiple regions, the DNS server group in that region can resolve the domain name, thus ensuring the high availability of the domain name resolution service in the target DNS zone.

[0016] Optionally, the domain name resolution request carries a target domain name, and the target domain name belongs to the target name area, then the corresponding DNS server group is determined from the multiple DNS server groups based on the target domain name and the target mapping relationship.

[0017] That is to say, when the multiple DNS servers provide domain name resolution externally, the cloud management platform resolves the domain name resolution request by scheduling the DNS server groups, so as to realize the refined management of the domain name resolution in the DNS zone.

[0018] Optionally, the corresponding DNS server is the DNS server group corresponding to the target domain name suffix, and the target domain name suffix is the domain name suffix that is determined from the domain name suffixes corresponding to the multiple DNS server groups by using the longest suffix matching algorithm and matches the target domain name.

[0019] It can be seen that by adopting the longest suffix matching algorithm, the target domain name suffix with the highest similarity to the target domain name (or, the most common part with the target domain name) can be determined, improving the matching accuracy of the domain name suffix, and enabling the target DNS server group corresponding to the target domain name suffix that matches the target domain name to effectively resolve the target domain name.

[0020] Optionally, the DNS server for resolving the domain name resolution request is one DNS server in the corresponding DNS server group.

[0021] Optionally, if the DNS servers included in the corresponding DNS server group are located in at least one Availability Zone (AZ), the DNS server for resolving the domain name resolution request is the DNS server in the corresponding DNS server group located in the first AZ, where the first AZ is the AZ where the initiator of the domain name resolution request is located.

[0022] Optionally, if the DNS server located in the first AZ is unable to resolve the target domain name, the DNS server for resolving the domain name resolution request is one DNS server in other AZs except the first AZ in the corresponding DNS server group.

[0023] It can be seen that for the target domain name carried in the domain name resolution request, when the target DNS server group corresponding to the target domain name includes DNS servers located in multiple AZs, the DNS server in the same AZ as the initiator of the domain name resolution request is preferentially selected from the target DNS server group to resolve the target domain name, so as to improve the domain name resolution efficiency. And when the DNS server in the same AZ as the initiator of the domain name resolution request in the target DNS server group is unable to resolve the target domain name, the domain name can also be resolved by the DNS servers in other AZs in the target DNS server group. In this way, in the case where the DNS server group includes DNS servers in multiple AZs, the high availability of the domain name resolution service is further ensured when resolving a domain name with a certain domain name suffix.

[0024] In a second aspect, a cloud management platform is provided. The cloud management platform has the function of implementing the behavior of the domain name resolution method based on cloud computing technology in the first aspect above. The cloud management platform includes at least one module, and this at least one module is used to implement the steps of the domain name resolution method based on cloud computing technology described in the first aspect above.

[0025] In a third aspect, a cluster of computing devices is provided. The cluster of computing devices includes at least one computing device, and each computing device includes a processor and a memory. The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the cluster of computing devices performs the steps of the domain name resolution method based on cloud computing technology described in the first aspect above.

[0026] Optionally, each computing device may further include a communication bus, which is used to establish a connection between the processor and the memory of each computing device.

[0027] In a fourth aspect, a computer-readable storage medium is provided. The storage medium includes computer program instructions, and when the computer program instructions are executed by a cluster of computing devices, the cluster of computing devices is caused to perform the steps of the domain name resolution method based on cloud computing technology described in the first aspect above.

[0028] In a fifth aspect, a computer program product including instructions is provided. When the instructions are run by a cluster of computing devices, the cluster of computing devices is caused to perform the steps of the domain name resolution method based on cloud computing technology described in the first aspect above.

[0029] The technical effects obtained in the second to fifth aspects above are similar to those obtained by the corresponding technical means in the first aspect, and will not be elaborated here. Description of the Drawings

[0030] Figure 1 is a schematic diagram of an implementation environment of a domain name resolution method based on cloud computing technology provided by an embodiment of the present application;

[0031] Figure 2 is a schematic flowchart of a domain name resolution method based on cloud computing technology provided by an embodiment of the present application;

[0032] Figure 3 is a schematic flowchart of domain name resolution based on a target mapping relationship provided by an embodiment of the present application;

[0033] Figure 4 is a schematic diagram of selecting a DNS server from a target DNS server group for domain name resolution provided by an embodiment of the present application;

[0034] Figure 5 is another schematic diagram of selecting a DNS server from a target DNS server group for domain name resolution provided by an embodiment of the present application;

[0035] Figure 6 is a schematic diagram of scheduling a DNS server group within multiple regions for domain name resolution provided by an embodiment of the present application;

[0036] Figure 7 It is a schematic diagram of the implementation logic of a domain name resolution method provided by an embodiment of the present application for a cloud management platform;

[0037] Figure 8 It is a schematic diagram of the structure of a cloud management platform provided by an embodiment of the present application;

[0038] Figure 9 It is a schematic diagram of the structure of a computing device provided by an embodiment of the present application;

[0039] Figure 10 It is a schematic diagram of the structure of a computing device cluster provided by an embodiment of the present application;

[0040] Figure 11 It is a schematic diagram of the network connection relationship of a computing device provided by an embodiment of the present application. Detailed implementation manners

[0041] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the following will further describe the embodiments of the present application in detail with reference to the accompanying drawings.

[0042] For ease of understanding, before explaining in detail the domain name resolution method based on cloud computing technology provided by the embodiments of the present application, the terms, application scenarios and implementation environments involved in the embodiments of the present application will be introduced first.

[0043] First, the terms involved in the embodiments of the present application will be introduced.

[0044] 1. Basic services

[0045] Services that provide basic functions for other services, including but not limited to computing services, storage services, load balancing services, domain name system (DNS) services, etc.

[0046] 2. DNS service

[0047] Also known as the domain name resolution service, which is the process of converting a domain name into an Internet Protocol (IP) address. Among them, the domain name resolution process is as follows: when a client initiates an access to a certain domain name, the client first sends a domain name query request to the local domain name server. If the local domain name server stores the IP address corresponding to the domain name, it returns the IP address to the client, and the domain name resolution process ends; if the local domain name server does not store the IP address corresponding to the domain name, the local domain name server replaces the client and performs a hierarchical query from the root domain name server to the top-level domain name server and then to the authoritative domain name server, and finally returns the obtained IP address of the domain name to the client.

[0048] 3. DNS Zone

[0049] A DNS zone is a continuous tree in the DNS domain name space, which divides the domain name space into several smaller management units as needed. A DNS zone is a management unit composed of a single area in the DNS name space or multiple closely adjacent subdomains with a hierarchical relationship.

[0050] It should be noted that DNS servers manage the name space through zones, not by domains. The name of the zone managed by a DNS server corresponds one-to-one with the name of the domain in the DNS name space it manages. Among them, a DNS server can manage one or more DNS zones, and a DNS zone can also be managed by multiple DNS servers.

[0051] 4. Authoritative DNS Server

[0052] A DNS server that can make an authoritative response to a domain name query / parsing request for the DNS zone it manages, that is, a DNS server that can complete IP mapping.

[0053] 5. Recursive Name Server

[0054] An intermediate proxy server between the DNS client and the authoritative DNS server.

[0055] 6. Four-Layer Load Balancing

[0056] A software device that forwards packets to different backend servers according to the packet information of the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP).

[0057] 7. Blast Radius

[0058] In the domain name resolution service, the blast radius refers to the scope of influence on users when a DNS server fails.

[0059] 8. Fault Isolation

[0060] Fault isolation means controlling the scope of influence of a fault within a limited range.

[0061] Secondly, a simple introduction to the application scenario of the embodiments of the present application is given.

[0062] Domain name resolution is the process of converting a domain name into an Internet Protocol (IP) address, and the resolution work is completed by a Domain Name System (DNS) server. Among them, the authoritative DNS server plays a core role in the domain name resolution process. It is responsible for resolving the IP address corresponding to the domain name. In related technologies, to ensure the high availability of the domain name resolution service, a large number of DNS servers need to be deployed as authoritative DNS servers, and these DNS servers are backed up with each other. Through these DNS servers, the domain name resolution service is provided to the outside world. In this way, since the number of DNS servers is large enough, even a large-scale Distributed Denial of Service (DDoS) attack will not cause damage to the domain name resolution service. Although this solution is relatively simple to implement, it requires the deployment of a large number of DNS servers, resulting in a high cost of the domain name resolution service.

[0063] Based on this, the embodiments of the present application provide a domain name resolution method based on cloud computing technology. For the domain names in the target DNS zone, based on limited DNS server resources, multiple DNS servers are reasonably grouped to obtain multiple DNS server groups, and each DNS server group is used to provide resolution services for some of the domain names in the target DNS zone. That is, in the case of limited DNS servers, the embodiments of the present application provide a more fine-grained domain name management solution for the domain names in a single DNS zone or a small number of DNS zones, ensuring the high availability of the domain name resolution service while minimizing the blast radius of the domain name resolution service.

[0064] Among them, the domain name resolution method based on cloud computing technology provided by the embodiments of the present application is applied in a cloud management platform. The cloud management platform can be a server cluster or a distributed system composed of multiple physical servers, etc. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), as well as big data and artificial intelligence platforms, or a cloud computing service center.

[0065] In the embodiments of the present application, the cloud management platform can provide a domain name registration interface and display it to the tenant. The domain name registration interface is used for the tenant to register a domain name, or submit a domain name to be managed, or submit a domain name resolution request for which the IP address needs to be resolved.

[0066] In the embodiments of the present application, the cloud management platform can also provide a domain name management service interface and display it to the users of the cloud management platform. This configuration interface is used for users to input DNS server information such as the domain name information of a certain name area, the total number of multiple DNS servers, the server group size, and the deployment location of the DNS servers, so that the cloud management platform can execute the domain name resolution method based on cloud computing technology provided in the embodiments of the present application, determine multiple domain name suffixes based on the domain name information, group the multiple DNS servers at the same time, and then generate a target mapping relationship between the domain name suffixes and the DNS server groups based on the multiple domain name suffixes and the multiple DNS server groups.

[0067] Among them, the user here can be an administrator of the cloud management platform or a tenant of the cloud management platform.

[0068] In some embodiments, when the user is a tenant of the cloud management platform, the cloud management platform can provide a domain name management solution for the tenant based on the domain name information and DNS server information provided by the tenant. That is to say, the cloud management platform executes the domain name resolution method based on cloud computing technology provided in the embodiments of the present application to generate a target mapping relationship between the domain name suffixes and the DNS server groups for the tenant.

[0069] In this way, after the tenant obtains the target mapping relationship from the cloud management platform, it can manage the domain name resolution services provided by its own multiple DNS servers in a fine-grained manner based on this target mapping relationship.

[0070] In some embodiments, when the user is an administrator of the cloud management platform, the cloud management platform is also used to manage the cloud infrastructure, and the cloud infrastructure includes multiple DNS servers. In this case, the cloud management platform determines the target mapping relationship between the domain name suffixes and the DNS server groups by executing the domain name resolution method based on cloud computing technology provided in the embodiments of the present application based on the domain name information and DNS server information input by the administrator.

[0071] Optionally, in the case where the cloud management platform generates the target mapping relationship, the administrator can configure the target mapping relationship to the management device of the cloud infrastructure, so that the management device of the cloud infrastructure schedules multiple DNS servers in the cloud infrastructure to perform domain name resolution based on this target mapping relationship.

[0072] In this case, the cloud management platform is only used to generate the target mapping relationship, and the management device of the cloud infrastructure manages the domain name resolution services provided by multiple DNS servers in the cloud infrastructure in a fine-grained manner based on this target mapping relationship.

[0073] Optionally, when the cloud management platform generates the target mapping relationship, if the cloud management platform directly manages the cloud infrastructure, the cloud management platform may also store the target mapping relationship, and upon receiving a domain name resolution request, based on the target mapping relationship, schedule the DNS servers within the corresponding DNS server group to resolve the domain name.

[0074] In this case, the cloud management platform is not only used to generate the target mapping relationship, but also directly schedules the DNS servers within the cloud infrastructure it manages to perform domain name resolution based on the target mapping relationship.

[0075] It can be seen that in the embodiments of the present application, the cloud management platform can provide domain name management services externally, providing a DNS server grouping scheme and a domain name suffix allocation scheme for users, that is, generating a target mapping relationship between the domain name suffix and the DNS server group according to the domain name information and DNS server information managed by the user. The cloud management platform can also provide domain name resolution services externally. Based on the situation of multiple DNS servers within the cloud infrastructure managed by the cloud management platform and the domain name information within the target name area, generate a target mapping relationship between the domain name suffix and the DNS server group, and based on this target mapping relationship, schedule the DNS servers in the corresponding DNS server group to resolve the domain name resolution request. The embodiments of the present application do not limit this.

[0076] Finally, taking the cloud management platform managing the cloud infrastructure, and the cloud infrastructure including multiple DNS servers as an example, the implementation environment involved in the embodiments of the present application is introduced.

[0077] Please refer to Figure 1 , Figure 1 FIG. is a schematic diagram of an implementation environment provided by an embodiment of the present application. This implementation environment includes a tenant side and a service side (i.e., the cloud platform). On the service side, the cloud management platform 20 is used to manage the cloud infrastructure 1. The cloud infrastructure 1 includes multiple regions (regions), for example, including region 10, region 11, and region 12; each region further includes multiple data centers, for example, including data center 101, data center 102, and data center 103. Each cloud data center further includes multiple DNS servers providing domain name resolution services, for example, including server 1011 and server 1012. On the tenant side, tenant A connects to the Internet through the client 21, and tenant B connects to the Internet through the client 22 and logs in to the cloud management platform 20.

[0078] Among them, the clients 21 and 22 can be terminal devices such as mobile phones with Internet access functions, personal computers, personal digital assistants, or thin clients.

[0079] Optionally, the cloud management platform 20 provides a configuration interface. Tenant A and Tenant B input configuration information of the cloud instance on the configuration interface. The cloud management platform 20 configures and manages the server where the cloud instance is located according to the configuration information. For example, the cloud instance can be created or deleted, and the cloud instance can be managed throughout its life cycle according to the configuration information.

[0080] Optionally, each region includes multiple availability zones (AZs). Figure 1 This is not shown in the figure. Among them, one AZ is a collection of one or more data centers. One AZ has independent water and electricity. Logically within the AZ, resources such as computing, network, and storage are further divided into multiple clusters. Multiple AZs in one region can be connected by high-speed optical fibers to meet the needs of users to build highly available systems across AZs.

[0081] As an example, region 10 may include AZ1 and AZ2, and AZ1 and AZ2 are communicatively connected. Among them, AZ1 includes data center 101 and data center 102, and AZ2 includes data center 103. The embodiments of the present application do not limit this.

[0082] It should be understood that regions and availability zones are used to describe the location of data centers. Tenants can create resources in specific regions and availability zones. And in the embodiments of the present application, regions and availability zones are used to explain the location of DNS servers, so as to determine whether the domain name resolution service provided by multiple DNS servers is deployed within a single data center, deployed within a single AZ, deployed across multiple AZs, or deployed across regions.

[0083] It should be noted that Figure 1 Only two tenants, two clients, and cloud infrastructure 1 including 3 regions are used as examples, which does not constitute a limitation on the number and type of tenant-side clients, cloud infrastructure, regions, AZs, data centers, etc. in this implementation environment.

[0084] In the embodiments of the present application, the cloud management platform 20 can provide a domain name registration interface and display it to the tenant side. The domain name registration interface is used for tenants to register domain names, or submit domain names to be managed, or submit domain name resolution requests for which IP addresses need to be resolved.

[0085] In the embodiments of the present application, the cloud management platform 20 also provides a configuration interface and displays it to the administrator of the cloud management platform. The configuration interface is used for the administrator to input information such as the total number of multiple DNS servers in the cloud infrastructure managed by the administrator, the server grouping size, and the deployment location of the DNS servers, so that the cloud management platform can execute the domain name resolution method based on cloud computing technology provided by the embodiments of the present application to determine the target mapping relationship between the domain name suffix of the target name area and the DNS server group.

[0086] Optionally, when generating the target mapping relationship, the cloud management platform may also, based on the target mapping relationship, call the corresponding DNS server group to resolve the domain names within the target name area.

[0087] Optionally, when generating the target mapping relationship, the cloud management platform may also send the target mapping relationship to the target device, so that the target device can, based on the target mapping relationship, call the corresponding DNS server group to resolve the domain names within the target name area.

[0088] That is to say, the embodiments of the present application do not limit the execution entity that schedules and manages multiple DNS servers to resolve domain names within the target name area based on the target mapping relationship.

[0089] As an example, when the cloud management platform serves as the execution entity to schedule and manage multiple DNS servers to resolve domain names within the target name area, the cloud management platform may further include a management device and a load balancing device. When implementing the domain name resolution method based on cloud computing technology provided in the embodiments of the present application, the management device is used to determine multiple domain name suffixes according to the domain names within the target DNS zone, group the multiple DNS servers to obtain multiple DNS server groups, and then assign the multiple domain name suffixes to the multiple DNS server groups so that each DNS server group corresponds to at least one domain name suffix, obtaining the target mapping relationship between the domain name suffixes and the DNS server groups, and sending the target mapping relationship to the load balancing device corresponding to the data center; the load balancing device is used to receive the domain name resolution request, extract the target domain name therefrom, and then, based on the target domain name and the target mapping relationship, determine the target DNS server group corresponding to the target domain name, and call the DNS servers in the target DNS server group to resolve the target domain name.

[0090] Optionally, the load balancing device may operate at the transport layer (i.e., the fourth network layer), and the load balancing device may also be referred to as a four-layer load balancing device to forward the domain name resolution request sent using TCP or UDP packets, and then, based on the target domain name carried in the domain name resolution request, forward the packet to the corresponding target DNS server group at the back end.

[0091] It should be understood that when the cloud management platform executes the domain name resolution method based on cloud computing technology provided in the embodiments of the present application, only the above-mentioned management device and load balancing device are used for illustration, and it may further include more or fewer devices to jointly implement the domain name resolution method. The embodiments of the present application do not limit the specific implementation manner of the corresponding devices in the cloud management platform.

[0092] Those skilled in the art should understand that the above cloud platform, cloud management platform, and cloud infrastructure are only examples. Other existing or future cloud platforms, cloud management platforms, and cloud infrastructure that are applicable to the embodiments of the present application should also be included within the protection scope of the embodiments of the present application and are hereby incorporated herein by reference.

[0093] It should be noted that the application scenarios and implementation environments described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art know that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0094] Next, a domain name resolution method based on cloud computing technology provided by the embodiments of the present application will be introduced.

[0095] Please refer to Figure 2 , Figure 2 which is a flowchart of a domain name resolution method based on cloud computing technology provided by the embodiments of the present application. This method can be applied to a cloud management platform, and the method includes the following steps.

[0096] Step 201: Group multiple DNS servers to obtain multiple DNS server groups. Each DNS server group includes at least one DNS server, and there is at least one different DNS server between different DNS server groups. These multiple DNS servers are used to resolve domain names in the target name area of the DNS namespace.

[0097] Among them, there is no direct quantitative relationship between the multiple DNS servers and the multiple DNS server groups. The number of DNS server groups can be less than, equal to, or greater than the total number of the multiple DNS servers. In the case of a limited number of DNS servers, the embodiments of the present application obtain as many DNS server groups as possible through reasonable grouping to ensure that the limited number of multiple DNS servers can provide highly available domain name resolution services for the domain names of the target DNS zone.

[0098] In some embodiments, when there is at least one different DNS server between the multiple DNS server groups, each DNS server group includes DNS servers that are not completely the same, that is, the DNS servers included in different DNS server groups can be completely different or partially different.

[0099] As an example, if multiple DNS servers include DNS server a, DNS server b, and DNS server c, after grouping these three DNS servers, multiple DNS server groups can be obtained: the first DNS server group (including DNS server a), the second DNS server group (including DNS server b), the third DNS server group (including DNS server c), the fourth DNS server group (including DNS server a and DNS server b), the fifth DNS server group (including DNS server b and DNS server c), the sixth DNS server group (including DNS server a and DNS server c), and the seventh DNS server group (including DNS server a, DNS server b, and DNS server c).

[0100] It can be seen that when grouping multiple DNS servers, without limiting the number of groups, the number of DNS servers in a DNS server group, etc., the maximum number of DNS server groups can be obtained through flexible grouping. When the number of DNS server groups is the largest, its explosion radius is 1 / the number of DNS server groups, and at this time the explosion radius is the smallest. It can be seen that for a limited number of DNS servers, through reasonable grouping, not only can domain name resolution be performed through different DNS server groups to perform fine-grained management of the domain name resolution service, but also the explosion radius of the domain name resolution service is reduced, and the availability of the domain name resolution service is improved.

[0101] In some embodiments, since different DNS server groups are used to resolve domain names with different domain name suffixes, when a DNS server group fails and cannot resolve the domain name with the corresponding domain name suffix, other DNS server groups need to be used to resolve the domain name with this domain name suffix to ensure the high availability of the domain name resolution service. Based on this, a backup relationship is established between multiple DNS server groups, that is, there are overlapping DNS servers between different DNS server groups.

[0102] After grouping multiple DNS servers, the DNS servers included in the multiple DNS server groups are not completely the same, but the DNS servers included in different DNS server groups can be partially the same, that is, there can be at least one same DNS server between different DNS server groups.

[0103] In this case, after performing step 201 above to group DNS servers a, DNS server b, and DNS server c of the above example, multiple DNS server groups are obtained, including: a fourth DNS server group (including DNS servers a and b), a fifth DNS server group (including DNS servers b and c), a sixth DNS server group (including DNS servers a and c), and a seventh DNS server group (including DNS servers a, b, and c).

[0104] That is, for multiple DNS server groups, when there is a same DNS server among different DNS servers, it can not only ensure the largest number of groups, but also enable a backup relationship between the server groups, improving the availability of the domain name resolution service.

[0105] In some embodiments, when it is limited that there is at least one different DNS server between DNS service groups, the size of the server groups can also be limited so that the scales of the obtained multiple DNS server groups are the same, that is, the number of DNS servers included in each DNS server group is the same.

[0106] In a possible implementation manner, the implementation process of step 201 above can be: obtaining the total number of multiple DNS servers and the size of the server groups, where the size of the server groups indicates the number of DNS servers divided into the same group; based on the total number of multiple DNS servers and the size of the server groups, grouping the multiple DNS servers in a permutation and combination manner to obtain multiple DNS server groups.

[0107] In some embodiments, as Figure 1 shown, when the cloud management platform is used to manage the cloud infrastructure and the cloud infrastructure includes multiple DNS servers, the cloud management platform can provide a configuration interface for the administrator of the cloud management platform to input the total number of multiple DNS servers and the size of the server groups in the configuration interface according to the specific situation of the cloud infrastructure.

[0108] Among them, the size of the server groups can be any positive integer greater than or equal to 1.

[0109] It should be understood that after grouping multiple DNS servers in a permutation and combination manner, for the obtained multiple DNS server groups, the scales of the multiple DNS server groups are the same, and there is at most one same DNS server between any two DNS server groups.

[0110] As an example, if multiple DNS servers include DNS server a, DNS server b, DNS server c, and DNS server d, and the server grouping size is 2, then after grouping these multiple DNS servers in a permutation and combination manner, 6 DNS server groups can be obtained: the first DNS server group (including DNS server a and DNS server b), the second DNS server group (including DNS server a and DNS server c), the third DNS server group (including DNS server a and DNS server d), the fourth DNS server group (including DNS server b and DNS server c), the fifth DNS server group (including DNS server b and DNS server d), and the sixth DNS server group (including DNS server c and DNS server d).

[0111] It can be seen that in the embodiment of the present application, by grouping multiple DNS servers with a limited number in a permutation and combination manner, more server groups can be obtained. As the number of DNS server groups increases, the blast radius when multiple DNS servers provide domain name resolution services externally becomes smaller.

[0112] Moreover, when resolving domain names within the target name area, in the embodiment of the present application, the target DNS server group is used to schedule DNS servers to resolve the target domain name. Therefore, when a certain DNS server group fails, it only affects the domain name resolution service for domain names with the domain name suffix corresponding to this DNS server group, and does not affect the domain name resolution services of other DNS server groups. Therefore, for the domain name resolution method based on cloud computing technology provided in the embodiment of the present application, when multiple DNS servers provide domain name resolution services externally, the blast radius of the domain name resolution service is 1 / the number of DNS server groups, greatly reducing the blast radius when providing domain name resolution services for domain names in a single or small number of DNS zones.

[0113] As described above, in the cloud infrastructure managed by the cloud management platform, multiple DNS servers can be located in one availability zone (AZ) or in multiple AZs. Next, these two situations will be introduced separately.

[0114] In the first case, if multiple DNS servers are located in one AZ, then based on the total number of DNS servers and the server grouping size, the multiple DNS servers can be directly grouped in a permutation and combination manner to obtain multiple DNS server groups, and the AZ information of the DNS servers included in each DNS server group is the same.

[0115] As an example, assume that the total number of DNS servers is N, and the server group size is R. Table 1 below shows the cases of DNS server groups obtained by grouping multiple DNS servers when multiple DNS servers are located in one AZ, and the explosion radii corresponding to different grouping cases.

[0116] Table 1

[0117] Total number of DNS servers (N) R＝2 R＝3 R＝4 4 1 / 6 1 / 4 1 6 1 / 15 1 / 20 1 / 15 8 1 / 28 1 / 56 1 / 70 16 1 / 120 1 / 560 1 / 1820 32 1 / 496 1 / 4960 1 / 35960 64 1 / 2016 1 / 41664 1 / 6353766

[0118] Referring to Table 1 above, the calculation method of the explosion radius is 1 / C(N, R), where C represents permutation and combination. For example, when the total number of DNS servers is 6 and the server group size is 2, then every two DNS servers are grouped into one group. By performing permutation and combination on these 6 DNS servers, C(6, 2) = 15 DNS server groups can be obtained. In this grouping case, when these 6 DNS servers provide domain name resolution services for the target DNS zone, the corresponding explosion radius is 1 / 15.

[0119] In the second case, if in the cloud infrastructure managed by the cloud management platform, multiple DNS servers are respectively located in multiple AZs, and the server group size is greater than or equal to the total number of AZs, then each DNS server group includes at least one DNS server in each AZ.

[0120] As an example, assume that the total number of DNS servers is N, the server group size is R, and the number of AZs is K. Table 2 below shows the cases of DNS server groups obtained by grouping multiple DNS servers when multiple DNS servers are located in two AZs, and the explosion radii corresponding to different grouping cases.

[0121] Table 2

[0122] Total number of DNS servers (N) / Number of DNS servers in a single AZ R = 2, K = 1 R = 4, K = 2 8 / 4 1 / 16 1 / 36 12 / 6 1 / 36 1 / 225 16 / 8 1 / 64 1 / 784 32 / 16 1 / 256 1 / 14400 64 / 32 1 / 1024 1 / 246016

[0123] Referring to Table 2 above, the calculation method of the explosion radius is 1 / C(N / 2, K) 2 , where C represents permutation and combination, and K = R / 2. For example, when the total number of DNS servers is 16 and each AZ includes 8 DNS servers, if the server group size is 4, then the DNS servers in each DNS server group are selected from two AZs respectively, that is, each DNS server group includes DNS servers from two AZs. At this time, by performing permutation and combination on 16 DNS servers, C(16 / 2, 2) 2 = 784 DNS server groups can be obtained. In this grouping case, when these 16 DNS servers provide domain name resolution services for the target DNS zone, the corresponding explosion radius is 1 / 784.

[0124] As an example, it is also assumed that the total number of DNS servers is N, the server group size is R, and the number of AZs is K. Table 3 below shows the situation of DNS server groups obtained after grouping multiple DNS servers when multiple DNS servers are located in three AZs, and the explosion radius corresponding to different grouping situations.

[0125] Table 3

[0126] Total number of DNS servers (N) / Number of DNS servers in a single AZ R = 2, K = 1 R = 4, K = 2 9 / 3 1 / 27 1 / 729 12 / 4 1 / 64 1 / 216 15 / 5 1 / 125 1 / 1000 24 / 8 1 / 512 1 / 21952 30 / 10 1 / 1000 1 / 91125

[0127] Referring to Table 3 above, the calculation method of the explosion radius is 1 / C(N / 2, K) 3 , where C represents permutation and combination, and K = R / 3. For example, when the total number of DNS servers is 15 and each AZ includes 5 DNS servers, if the server group size is 4, then the DNS servers in each DNS server group are selected from three AZs respectively, that is, each DNS server group includes DNS servers from three AZs. At this time, by performing permutation and combination on 15 DNS servers, C(15 / 3, 2) 3 = 1000 DNS server groups can be obtained. In this grouping situation, when these 15 DNS servers provide domain name resolution services for the target DNS zone, the corresponding explosion radius is 1 / 1000.

[0128] Step 202: Obtain multiple domain name suffixes, where the multiple domain name suffixes are the suffixes of domain names within the target name area.

[0129] In a possible implementation manner, the implementation process of step 202 can be: based on the domain name suffix extraction rule, perform suffix extraction processing on the domain names within the target name area to obtain multiple domain name suffixes; where the domain name suffix extraction rule indicates extracting the domain name suffix from the domain name according to the specified domain name level.

[0130] It should be noted that the above domain name suffix extraction rule can be configured by the administrator, and the domain name level can be the top-level domain name, that is, extracting the top-level domain name in each domain name as the suffix; the domain name level can also be the second-level domain name or the third-level domain name, etc., that is, indicating to extract the second-level domain name or the third-level domain name as the suffix, and the embodiments of the present application do not limit this. In addition, for the domain names within the target name area, the embodiments of the present application also do not limit the number of the extracted domain name suffixes.

[0131] Step 203: Generate a target mapping relationship based on the multiple domain name suffixes and the multiple DNS server groups, where the target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the multiple DNS server groups.

[0132] In a possible implementation, the implementation process of step 203 may be as follows: Determine the corresponding relationship between the domain name suffix and the DNS server group according to the quantitative relationship between the domain name suffix and the DNS server group, so as to obtain the target mapping relationship.

[0133] Among them, in this target mapping relationship, the domain name suffix and the DNS server group may be in one-to-one correspondence, or many-to-one, or one-to-many. The embodiments of the present application do not limit this.

[0134] In some embodiments, considering that there may be a dependency relationship between domain name suffixes, in order to avoid mutual influence during domain name resolution corresponding to two domain name suffixes, for domain name suffixes with a dependency relationship, different DNS server groups need to be assigned to them, that is, there are no identical DNS servers in the DNS server groups corresponding to two domain name suffixes with a dependency relationship. Therefore, there is no domain name corresponding to two domain name suffixes with a dependency relationship stored on one DNS server.

[0135] As an example, for the obs domain name suffix and the ecs domain name suffix, the DNS server group corresponding to the obs domain name suffix is the first DNS server group, and the DNS server group corresponding to the ecs domain name suffix is the second DNS server group, and the DNS servers included in the first DNS server group and the second DNS server group are completely different.

[0136] Based on this, for domain name suffixes with a dependency relationship, since their corresponding DNS server groups are completely different, when a DNS server in the DNS server group corresponding to one of the domain name suffixes fails, it will not affect the domain name resolution service of the DNS server group of other domain name suffixes with a dependency relationship. The scope of the impact of the domain name resolution service failure can be controlled within a single DNS service group, achieving refined fault isolation.

[0137] It should be noted that when assigning multiple domain name suffixes to multiple DNS servers, the DNS server groups corresponding to each domain name suffix can be coordinately determined according to the relationship between the domain name suffixes, and / or the overlap situation of the DNS servers in the DNS server group, etc. The embodiments of the present application do not limit this. The above-mentioned dependency relationship between domain name suffixes is only an example and does not constitute a limitation on the specific implementation manner of step 203.

[0138] Step 204: Based on the target mapping relationship, assign multiple domain name suffixes to the corresponding DNS server groups, so that when the DNS servers in the corresponding DNS server groups receive a domain name resolution request, they resolve the domain name resolution request.

[0139] Among them, after allocating multiple domain name suffixes, for each DNS server group, it may correspond to one domain name suffix or multiple domain name suffixes. This application embodiment does not limit this.

[0140] In some embodiments, when a domain name resolution request carries a target domain name that belongs to a target name area, the corresponding DNS server group is determined from multiple DNS server groups based on the target domain name and a target mapping relationship.

[0141] In a possible implementation manner, the corresponding DNS server can be the DNS server group corresponding to the target domain name suffix. Among them, the target domain name suffix is the domain name suffix that is determined from the domain name suffixes corresponding to multiple DNS server groups by using the longest suffix matching algorithm and matches the target domain name.

[0142] That is to say, for the DNS server group that resolves the target domain name, the domain name suffix corresponding to this DNS server group has the highest similarity with the suffix of the target domain name.

[0143] In some embodiments, the DNS server that resolves the domain name resolution request is a DNS server in the corresponding DNS server group.

[0144] In other words, after selecting the DNS server group that receives the domain name resolution request from multiple DNS server groups, the domain name resolution request is resolved by a DNS server in this DNS server group, rather than by all DNS servers in the DNS server group, so as to improve the resource utilization rate of the DNS server.

[0145] In some embodiments, if the DNS servers included in the corresponding DNS server group are located in at least one AZ, the DNS server that resolves the domain name resolution request is the DNS server in the corresponding DNS server group that is located in the first AZ.

[0146] Among them, the first AZ is the AZ where the initiator of the domain name resolution request is located.

[0147] Optionally, if the DNS server located in the first AZ is unable to resolve the target domain name, the DNS server that resolves the domain name resolution request is a DNS server in other AZs except the first AZ in the corresponding DNS server group.

[0148] It can be seen that in the embodiments of the present application, the cloud management platform reasonably groups multiple DNS servers to obtain the maximum number of DNS server groups; at the same time, it determines multiple domain name suffixes based on the domain names in the target name area, and then generates a target mapping relationship based on the multiple domain name suffixes and the multiple DNS server groups, and distributes the multiple domain name suffixes to the corresponding DNS server groups based on the target mapping relationship, so that each DNS server group can resolve the domain names with the corresponding domain name suffixes. That is, for a limited number of DNS servers, the cloud management platform can, through reasonable grouping and generating a target mapping relationship, when multiple DNS servers provide domain name resolution services, schedule the DNS servers for domain name resolution in groups based on the target mapping relationship, which can not only perform fine-grained management of the domain name resolution service, but also reduce the blast radius of the domain name resolution service and improve the availability of the domain name resolution service.

[0149] Based on the domain name resolution method based on cloud computing technology shown in the above embodiments, next, taking the cloud management platform managing cloud infrastructure, and the cloud infrastructure including multiple DNS servers as an example, after the cloud management platform generates a target mapping relationship for multiple DNS servers and the domain names in the target name area in the DNS name space in the manner shown in the above embodiments, the cloud management platform can also schedule the corresponding DNS server groups to resolve the corresponding domain names based on the target mapping relationship.

[0150] Among them, the target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the multiple DNS server groups.

[0151] See Figure 3 , when the cloud management platform executes the domain name resolution method based on cloud computing technology provided in the embodiments of the present application based on the target mapping relationship, the following steps may also be included:

[0152] Step 301: Receive a domain name resolution request, where the domain name resolution request carries a target domain name, and the target domain name belongs to the target name area.

[0153] It should be noted that after the cloud management platform generates the above target mapping relationship, it can first store the target mapping relationship and then execute this step 301 when receiving a domain name resolution request subsequently.

[0154] That is, after the cloud management platform receives a domain name resolution request sent from the tenant side, it first resolves the target domain name from the domain name request, and when the target domain name belongs to the target DNS zone, it executes the following step 302 based on the target domain name.

[0155] Step 302: Resolve the target domain name based on the target mapping relationship.

[0156] In some embodiments, the implementation process of step 302 may include the following steps (1)-(2):

[0157] (1) Based on the target mapping relationship, determine the target DNS server group corresponding to the target domain name from multiple DNS server groups.

[0158] In a possible implementation manner, the implementation process of step (1) may be: adopt the longest suffix matching algorithm to determine the target domain name suffix matched by the target domain name from the domain name suffixes corresponding to multiple DNS server groups; determine the DNS server group corresponding to the target domain name suffix as the target DNS server group.

[0159] It should be noted that the domain name suffix may be the top-level domain name, second-level domain name, third-level domain name, etc. of the target domain name. The longest suffix matching algorithm means that when the suffix of the target domain name is the same as multiple domain name suffixes in the target mapping relationship, the domain name suffix with the highest domain name level is used as the target domain name suffix.

[0160] As an example, if the target domain name is aaa.xxx.yyy.example.com, and the domain name suffixes in the target mapping relationship include example.com, yyy.example.com, and xxx.yyy.example.com, where example.com is the second-level domain name suffix, yyy.example.com is the third-level domain name suffix, and xxx.yyy.example.com is the fourth-level domain name suffix, then by using the longest suffix matching algorithm, xxx.yyy.example.com with the highest domain name level is determined as the target domain name suffix matched by the target domain name.

[0161] It can be seen that by using the longest suffix matching algorithm, the target domain name suffix with the highest similarity (or the most identical parts) to the target domain name can be determined, improving the matching accuracy of the domain name suffix, so that the target DNS server group corresponding to the target domain name suffix matched by the target domain name can effectively resolve the target domain name.

[0162] (2) Resolve the target domain name through the DNS servers in the target DNS server group.

[0163] It should be noted that any DNS server in the target DNS server group can resolve the target domain name, that is, each DNS server in the target DNS server group stores the IP addresses of all domain names corresponding to the corresponding domain name suffix.

[0164] In a possible implementation, the implementation process of the above step (2) may be as follows: select a DNS server from the target DNS server group; send the target domain name to the selected DNS server to instruct the selected DNS server to resolve the target domain name.

[0165] Among them, when selecting a DNS server from the target DNS server group, a DNS server can be randomly selected from the DNS servers by means of random selection, polling, etc. The embodiments of the present application do not limit the selection method.

[0166] As an example, refer to Figure 4 , after determining the second DNS server group as the target DNS server group based on the domain name suffix matched by the target domain name, select a DNS server from the second DNS server group, and then send the target domain name to the selected DNS server to instruct the DNS server to resolve the target domain name.

[0167] Optionally, after selecting a DNS server from the target DNS server group, the cloud management platform can also directly forward the domain name resolution request to the selected DNS server to instruct the DNS server to resolve the target domain name carried in the domain name resolution request. The embodiments of the present application do not limit this.

[0168] In some embodiments, when multiple DNS servers are located in multiple AZs, when dividing the DNS server group, each DNS server may include DNS servers in multiple AZs. Therefore, the DNS servers included in the target DNS server group determined by the cloud management platform are located in at least one AZ. At this time, the implementation method of selecting a DNS server from the target DNS server group may be: determine the first AZ where the initiator of the domain name resolution request is located; select a DNS server located in the first AZ from the target DNS server group. The first AZ is any one of the multiple AZs.

[0169] That is, when the initiator of the domain name resolution request is located in the first AZ, the DNS server in the first AZ is preferentially selected to provide domain name resolution services. In this way, when using the DNS server in the same AZ to provide domain name resolution services, the communication route between the initiator of the domain name resolution request and the DNS server is shorter, the latency of domain name resolution is shorter, and the domain name resolution efficiency is high.

[0170] Optionally, if the DNS server located in the first AZ cannot resolve the target domain name, then select a DNS server in other AZs except the first AZ from the target DNS server group and continue to resolve the target domain name.

[0171] As an example, refer to Figure 5, after the cloud management platform determines the target DNS server group based on the domain name suffix matched by the target domain name, if the initiator of the domain name resolution request is located in AZ1, then select DNS server p or DNS server q in AZ1 from the target DNS server group to resolve the target domain name. If DNS server p or DNS server q in AZ1 fails and cannot resolve the target domain name, then select DNS server m or DNS server n in AZ2 from the target DNS server group to resolve the target domain name.

[0172] It should be understood that Figure 5 Taking only the selection of DNS server q in AZ1 to resolve the target domain name, or the selection of DNS server m in AZ2 to resolve the target domain name as an example, in actual applications, it is also possible to select DNS server p in AZ1 to resolve the target domain name. In the case where DNS server p cannot resolve the target domain name, select DNS server n in AZ2 to resolve the target domain name. The embodiments of the present application do not limit this.

[0173] Thus, for the target domain name carried in the domain name resolution request, when the target DNS server group corresponding to the target domain name includes DNS servers located in multiple AZs, preferentially select the DNS server in the same AZ as the initiator of the domain name resolution request from the target DNS server group to resolve the target domain name, so as to improve the domain name resolution efficiency. And when the DNS server in the same AZ as the initiator of the domain name resolution request in the target DNS server group cannot resolve the target domain name, it is also possible to resolve the domain name through the DNS servers in other AZs in the target DNS server group. In this way, in the case where the DNS server group includes DNS servers in multiple AZs, when resolving a domain name with a certain domain name suffix, the high availability of the domain name resolution service is further ensured.

[0174] In some embodiments, when multiple DNS servers are located in multiple regions, the multiple regions correspond to the same virtual access address, and the domain name suffixes corresponding to the DNS server groups in the multiple regions are the same.

[0175] Since the virtual access addresses of each region are the same, during the domain name resolution process, the cloud management platform can select one region from the multiple regions based on the virtual access address, and forward the domain name resolution request carrying the target domain name to the target DNS server group in the selected region to instruct the DNS servers in the selected target DNS server group to resolve the target domain name.

[0176] As an example, refer to Figure 6, multiple DNS servers (i.e., DNS Server 11 - DNS Server 1n, and DNS Server 21 - DNS Server 2n) are used to resolve domain names within the target DNS zone. When a domain name resolution request carries a domain name within the DNS zone, the DNS servers in both region1 and region2 can provide domain name resolution services. Based on this, both region1 and region2 publish the same virtual access address externally.

[0177] Among them, the virtual access address can be an internal network IP address, such as 10.10.10.10. In practical applications, a public network IP address can also be used as the virtual access address, and the embodiments of this application do not limit this.

[0178] It should be noted that since multiple DNS servers are used to resolve domain names within the target DNS zone, the overall domain name suffix corresponding to the DNS server group deployed within each region is the same; however, since the number of DNS servers in each region may be different, the number of DNS server groups obtained after grouping may also be different. Therefore, the mapping relationship between the domain name suffix of each region and the DNS server group may be slightly different.

[0179] For example, region1 includes 10 DNS server groups, and region2 includes 5 DNS server groups. If 10 domain name suffixes are determined based on the domain names within the target DNS zone, the target mapping relationship stored in region1 can be the mapping relationship between 10 domain name suffixes and 10 DNS server groups, while the target mapping relationship stored in region2 can be the mapping relationship between 10 domain name suffixes and 5 DNS server groups.

[0180] It can be seen that when multiple DNS servers are located in different regions and are used to resolve domain names within the target DNS zone, the same virtual access address can be set for multiple regions, and the same domain name suffix can be configured for the DNS server groups within multiple regions based on the domain names within the target name area. In this way, for any domain name resolution request for a domain name belonging to the DNS zone, when it is forwarded to any one of the multiple regions, the DNS server group within that region can resolve the domain name. In other words, when resolving domain names within the target DNS zone, the DNS servers in multiple regions back up each other, thus ensuring the high availability of the domain name resolution service within the target DNS zone.

[0181] In summary, in the embodiments of the present application, the cloud management platform, based on multiple DNS servers included in the cloud infrastructure, obtains multiple DNS server groups with the maximum number by reasonably grouping the multiple DNS servers; and combines the domain name suffixes of the domain names in the target DNS zone to generate a target mapping relationship between the domain name suffixes and the DNS server groups. Based on this target mapping relationship, when a domain name resolution request is received, the target DNS server group corresponding to the target domain name can be determined based on the domain name suffix of the target domain name carried in the domain name resolution request and the target mapping relationship, and then the target domain name is resolved by the DNS servers in the target DNS server group. It can be seen that when the cloud management platform in the embodiments of the present application performs domain name resolution based on the target mapping relationship, domain names with the same domain name suffix can be resolved by the DNS servers in the same DNS server group, and since there is at least one different DNS server between different DNS server groups, when a certain DNS server group fails, it only affects the domain name suffix corresponding to that DNS server group and does not affect the domain name resolution service of domain names with other domain name suffixes. In this way, by scheduling DNS server groups to provide domain name resolution services for domain names in the target name area based on the target mapping relationship, not only can the domain name resolution service be managed in a fine-grained manner based on DNS servers, but also the blast radius of the domain name resolution service is reduced, and the availability of the domain name resolution service is improved.

[0182] Based on the domain name resolution method based on cloud computing technology shown in the above embodiments, for the sake of easy understanding, next, taking the cloud management platform as the execution subject, combined with the following Figure 7 , an exemplary explanation of the domain name resolution method based on cloud computing technology will be given.

[0183] Please refer to Figure 7 , the cloud management platform is used to manage the cloud infrastructure, and the cloud infrastructure includes DNS servers B1 - DNS servers Bm. When the cloud management platform executes the domain name resolution method based on cloud computing technology provided in the embodiments of the present application, the cloud management platform first groups multiple DNS servers (i.e., DNS servers B1 - DNS servers Bm) based on the total number of multiple DNS servers and the server grouping size to obtain multiple DNS server groups; then, assigns the domain name suffixes of the domain names in the target DNS zone to the multiple DNS server groups so that each DNS server group corresponds to at least one domain name suffix, obtains the target mapping relationship between the domain name suffixes and the DNS server groups, and stores the target mapping relationship.

[0184] Further, after receiving a domain name resolution request, the cloud management platform determines a target DNS server group corresponding to the target domain name based on the target domain name and the target mapping relationship carried in the domain name resolution request, and then selects a DNS server from the target DNS server group to resolve the target domain name.

[0185] It can be seen that for multiple DNS servers capable of resolving domain names within a DNS zone, the cloud management platform first groups the multiple DNS servers to obtain multiple DNS server groups, and assigns the domain name suffixes of the domain names in the DNS zone to the multiple DNS server groups to generate a target mapping relationship between the domain name suffixes and the DNS server groups. In this way, when multiple DNS servers provide domain name resolution services externally, the domain name resolution requests can be forwarded by scheduling the DNS server groups to achieve refined management of the domain name resolution within the DNS zone.

[0186] Moreover, dividing the limited DNS servers into multiple DNS server groups can minimize the blast radius of the domain name resolution service. When a DNS server group fails, it only affects the resolution of the domain names with the domain name suffix corresponding to this DNS server group, and does not affect the domain name resolution services of other domain name suffixes. At the same time, since multiple DNS servers included in a DNS server group can all resolve the domain names with the corresponding domain name suffix, when a single DNS server in a certain DNS server group fails, other DNS servers within this DNS server group can still provide domain name resolution services externally, improving the availability of the domain name resolution service.

[0187] In addition, when resolving the domain names within a target DNS zone, the embodiments of the present application can perform scheduling in units of DNS server groups. In the case of maximizing the number of DNS server groups, the blast radius of the domain name resolution service can be ensured to be minimized, improving the availability of the domain name resolution service.

[0188] Figure 8 It is a schematic structural diagram of a cloud management platform provided by the embodiments of the present application. Refer to Figure 8 As shown in the figure, the cloud management platform includes: a grouping module 801, a suffix obtaining module 802, a mapping relationship generating module 803, and a suffix assignment module 804.

[0189] The grouping module 801 is configured to group multiple DNS servers to obtain multiple DNS server groups. Each DNS server group includes at least one DNS server, and there is at least one different DNS server between different DNS server groups. The multiple DNS servers are used to resolve the domain names within the target name area in the DNS namespace;

[0190] A suffix acquisition module 802, configured to acquire a plurality of domain name suffixes, where the plurality of domain name suffixes are suffixes of domain names within a target name area;

[0191] A mapping relationship generation module 803, configured to generate a target mapping relationship based on the plurality of domain name suffixes and a plurality of DNS server groups, where the target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the plurality of DNS server groups;

[0192] A suffix allocation module 804, configured to allocate the plurality of domain name suffixes to the corresponding DNS server groups based on the target mapping relationship, so that when the DNS servers in the corresponding DNS server groups receive a domain name resolution request, they resolve the domain name resolution request.

[0193] Optionally, the grouping module 801 includes:

[0194] A parameter acquisition unit, configured to acquire the total number of a plurality of DNS servers and a server grouping size, where the server grouping size indicates the number of DNS servers divided into the same group;

[0195] A grouping unit, configured to group the plurality of DNS servers by using permutation and combination based on the total number of the plurality of DNS servers and the server grouping size, to obtain a plurality of DNS server groups.

[0196] Optionally, the cloud management platform is used to manage cloud infrastructure, and the cloud infrastructure includes a plurality of DNS servers.

[0197] Optionally, if the plurality of DNS servers are located in multiple AZs in the cloud infrastructure, and the server grouping size is greater than or equal to the total number of the multiple AZs, then each DNS server group includes at least one DNS server in each AZ.

[0198] Optionally, if the plurality of DNS servers are located in multiple regions in the cloud infrastructure, then the multiple regions correspond to the same virtual access address, and the domain name suffixes corresponding to the DNS server groups within the multiple regions are the same.

[0199] Optionally, the domain name resolution request carries a target domain name, where the target domain name belongs to the target name area, and the corresponding DNS server group is determined from the plurality of DNS server groups based on the target domain name and the target mapping relationship.

[0200] Optionally, the corresponding DNS server is the DNS server group corresponding to the target domain name suffix, where the target domain name suffix is determined from the domain name suffixes corresponding to the plurality of DNS server groups by using the longest suffix matching algorithm and is the domain name suffix that matches the target domain name.

[0201] Optionally, the DNS server that resolves the domain name resolution request is one DNS server in the corresponding DNS server group.

[0202] Optionally, if the DNS servers included in the corresponding DNS server group are located in at least one AZ, the DNS server that resolves the domain name resolution request is the DNS server in the corresponding DNS server group that is located in the first AZ, where the first AZ is the AZ where the initiator of the domain name resolution request is located.

[0203] Optionally, if the DNS server located in the first AZ is unable to resolve the target domain name, the DNS server that resolves the domain name resolution request is one DNS server in other AZs except the first AZ in the corresponding DNS server group.

[0204] In the embodiment of the present application, the cloud management platform, based on multiple DNS servers included in the cloud infrastructure, obtains multiple DNS server groups with the maximum number by reasonably grouping the multiple DNS servers; and combines the domain name suffixes of the domain names in the target DNSzone to generate a target mapping relationship between the domain name suffixes and the DNS server groups. That is, for a limited number of DNS servers, the cloud management platform, through reasonable grouping and generating the target mapping relationship, enables the multiple DNS servers to provide domain name resolution services. Based on this target mapping relationship, the DNS servers can be scheduled in groups for domain name resolution, which not only enables fine-grained management of the domain name resolution service, but also reduces the blast radius of the domain name resolution service and improves the availability of the domain name resolution service.

[0205] Further, when the cloud management platform schedules the DNS server for domain name resolution, the cloud management platform can, based on the target mapping relationship, enable the domain names with the same domain name suffix to be resolved by the DNS servers in the same DNS server group. And since there is at least one different DNS server between different DNS server groups, when a certain DNS server group fails, it only affects the domain name suffix corresponding to the DNS server group and does not affect the domain name resolution services of the domain names with other domain name suffixes. Thus, by scheduling the DNS server group based on the target mapping relationship to provide domain name resolution services for the domain names in the target name area, it not only enables fine-grained management of the domain name resolution service based on the DNS server, but also reduces the blast radius of the domain name resolution service and improves the availability of the domain name resolution service.

[0206] It should be noted that when the cloud management platform provided in the above embodiments constructs the target mapping relationship and resolves the domain names in the target DNS zone based on the target mapping relationship, only the division of the above functional modules is used for illustration. In practical applications, the above functions can be assigned to different functional modules according to needs, that is, the internal structure of the cloud management platform can be divided into different functional modules to complete all or part of the functions described above. In addition, the cloud management platform provided in the above embodiments and the above Figure 2 embodiment of the domain name resolution method based on cloud computing technology shown belong to the same concept. For the specific implementation process, please refer to the above method embodiment and will not be elaborated here.

[0207] In the above device embodiments, the grouping module, the suffix acquisition module, the mapping relationship generation module, and the suffix allocation module can all be implemented by software or by hardware. Exemplarily, next, taking the grouping module as an example, the implementation manner of the grouping module will be introduced. Similarly, the implementation manners of the suffix acquisition module, the mapping relationship generation module, and the suffix allocation module can refer to the implementation manner of the grouping module.

[0208] As an example of a software functional unit, the grouping module may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above computing instance may be one or more. For example, the grouping module may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers for running the code may be distributed in the same region, or may be distributed in different regions. Further, the multiple hosts / virtual machines / containers for running the code may be distributed in the same availability zone (AZ), or may be distributed in different AZs, and each AZ includes one data center or multiple geographically proximate data centers. Usually, one region may include multiple AZs.

[0209] Similarly, the multiple hosts / virtual machines / containers for running the code may be distributed in the same virtual private cloud (VPC), or may be distributed in multiple VPCs. Usually, one VPC is set within one region. For cross-region communication between two VPCs within the same region and between VPCs in different regions, a communication gateway needs to be set in each VPC, and the interconnection between VPCs is realized through the communication gateway.

[0210] As an example of a hardware functional unit, the grouping module may include at least one computing device, such as a server or the like. Alternatively, the receiving module may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). Among them, the above PLD may be implemented by a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0211] The multiple computing devices included in the grouping module may be distributed in the same region or in different regions. The multiple computing devices included in the grouping module may be distributed in the same availability zone (AZ) or in different AZs. Similarly, the multiple computing devices included in the grouping module may be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Among them, the multiple computing devices may be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0212] It should be noted that in other embodiments, the grouping module may be used to execute any step in the domain name resolution method based on cloud computing technology. The suffix acquisition module, the mapping relationship generation module, and the suffix allocation module may also be respectively used to execute any step in the domain name resolution method based on cloud computing technology. That is to say, the steps to be implemented by the grouping module, the suffix acquisition module, the mapping relationship generation module, and the suffix allocation module can be specified as needed. The above-mentioned cloud management platform's all functions are realized by respectively implementing different steps in the domain name resolution method based on cloud computing technology through the grouping module, the suffix acquisition module, the mapping relationship generation module, and the suffix allocation module.

[0213] The embodiment of the present application also provides a computing device 100. As Figure 9 shown, the computing device 100 includes: a bus 102, a processor 104, a memory 106, and a communication interface 108. The processor 104, the memory 106, and the communication interface 108 communicate with each other through the bus 102. The computing device 100 may 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 the computing device 100.

[0214] The bus 102 can be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 9 only one line is used in Figure 9 , but it does not mean that there is only one bus or one type of bus. The bus 102 can include a path for transmitting information between various components of the computing device 100 (for example, the memory 106, the processor 104, and the communication interface 108).

[0215] The processor 104 can include any one or more of processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP). An integrated circuit such as an ASIC, a PLD, or a combination thereof. Optionally, the above PLD is a CPLD, an FPGA, a GAL, or any combination thereof.

[0216] The memory 106 can include a volatile memory, such as a random access memory (RAM). The processor 104 can 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), or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 106 exists independently and is connected to the processor 104 through the bus 102, or the memory 106 is integrated with the processor 104.

[0217] The executable program code is stored in the memory 106, and the processor 104 executes the executable program code to respectively implement the functions of the foregoing grouping module, suffix acquisition module, mapping relationship generation module, and suffix allocation module, so as to implement Figure 2 the domain name resolution method based on cloud computing technology shown. That is, the memory 106 stores instructions for executing Figure 2 the domain name resolution method based on cloud computing technology shown.

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

[0219] The embodiments of the present application also provide a cluster of computing devices. The cluster of computing devices 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.

[0220] As Figure 10 shown, the cluster of computing devices includes at least one computing device 100. Instructions for executing a domain name resolution method based on cloud computing technology can be stored in the same manner in the memories 106 of one or more of the computing devices 100 in the cluster of computing devices.

[0221] In some possible implementation manners, partial instructions for executing a domain name resolution method based on cloud computing technology can also be stored separately in the memories 106 of one or more of the computing devices 100 in the cluster of computing devices. In other words, a combination of one or more computing devices 100 can jointly execute the instructions for executing a domain name resolution method based on cloud computing technology.

[0222] In the memories 106 of different computing devices 100 in the cluster of computing devices, different instructions can be stored, respectively for executing Figure 8 partial functions of the cloud management platform shown above. That is, the instructions stored in the memories 106 of different computing devices 100 can implement the functions of one or more of the grouping module, the suffix obtaining module, the mapping relationship generating module, and the suffix allocating module.

[0223] In some possible implementation manners, one or more computing devices in the cluster of computing devices can be connected through a network. Among them, the network can be a wide area network or a local area network, etc. Figure 11 A possible implementation manner is shown. As Figure 11 shown, two computing devices 100A and 100B are connected through a network. Specifically, they are connected to the network through the communication interfaces in each computing device. In this type of possible implementation manner, instructions for executing the functions of the grouping module, the suffix obtaining module, and the suffix matching module are stored in the memory 106 of the computing device 100A. At the same time, instructions for executing the function of the suffix allocating module are stored in the memory 106 of the computing device 100B.

[0224] Figure 11The connection manner between the computing device clusters shown may be that after the cloud management platform generates the target mapping relationship according to the domain name resolution method based on cloud computing technology provided in this application, it is also necessary to analyze and match multiple domain name suffixes in combination with the target mapping relationship to determine the DNS server group corresponding to each domain name suffix. This process may involve a large number of interaction processes and data configuration operations. Therefore, the function of the suffix allocation module related to domain name resolution is separately executed by the computing device 100B.

[0225] It should be understood that Figure 10 The functions of the computing device 100A shown in can also be completed by multiple computing devices 100. Similarly, the functions of the computing device 100B can also be completed by multiple computing devices 100.

[0226] This application embodiment also provides another computing device cluster. The connection relationship between the computing devices in this computing device cluster can be similarly referred to Figure 10 and Figure 11 The connection manner of the computing device cluster shown. The difference is that the same instructions for executing the domain name resolution method based on cloud computing technology can be stored in the memory 106 of one or more of the computing devices 100 in this computing device cluster.

[0227] In some possible implementation manners, partial instructions for executing the domain name resolution method can also be separately stored in the memory 106 of one or more of the computing devices 100 in this computing device cluster. In other words, a combination of one or more computing devices 100 can jointly execute the instructions for executing the domain name resolution method based on cloud computing technology.

[0228] It should be noted that the memories 106 in different computing devices 100 in the computing device cluster can store different instructions for executing partial functions of the domain name resolution system based on cloud computing technology. That is, the instructions stored in the memories 106 of different computing devices 100 can implement Figure 8 The functions of one or more devices in the cloud management platform shown.

[0229] In addition, in the application embodiments provided in this application Figures 9 - 11 Only the example where the instructions for executing Figure 2 The domain name resolution method based on cloud computing technology shown is stored in the memory 106 is given, which does not constitute a limitation on the instructions that can be stored in the memory. That is, Figures 9 - 11 The memory shown may also include a grouping module, a suffix acquisition module, a mapping relationship generation module, and a suffix allocation module, and the application embodiments do not limit this.

[0230] The embodiments of the present application also provide 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 containing 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), etc. The computer-readable storage medium includes instructions that direct the computing device to perform the steps of the domain name resolution method based on cloud computing technology shown in the above embodiments.

[0231] The embodiments of the present application also provide a computer program product containing instructions. The computer program product can be software or a program product containing instructions that can run on a computing device or be stored in any available medium. When the computer program product runs on at least one computing device, it causes at least one computing device to perform the steps of the domain name resolution method based on cloud computing technology shown in the above embodiments.

[0232] It should be understood that the "multiple" mentioned herein refers to two or more. In the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B can mean A or B; the "and / or" herein is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the terms "first", "second", etc. do not limit the quantity and execution order, and the terms "first", "second", etc. do not necessarily limit to be different.

[0233] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of the present application are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions. For example, the embodiments of the present application involve obtaining relevant information of multiple domain name suffixes based on domain names within the DNS zone, which are all obtained under full authorization.

[0234] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application and are not intended to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and 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 application.

Claims

1. A domain name resolution method based on cloud computing technology, characterized in that: Applied to a cloud management platform, the method includes: Grouping a plurality of DNS servers to obtain a plurality of DNS server groups, each DNS server group including at least one DNS server, and at least one different DNS server between different DNS server groups, the plurality of DNS servers being used to resolve domain names within a target name zone in a DNS name space; Acquire multiple domain name suffixes, where the multiple domain name suffixes are suffixes of domain names in the target name area; Based on the multiple domain name suffixes and the multiple DNS server groups, generating a target mapping relationship, the target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the multiple DNS server groups; Based on the target mapping relationship, the multiple domain name suffixes are allocated to corresponding DNS server groups, so that the DNS servers in the corresponding DNS server group resolve the domain name resolution request when receiving the domain name resolution request.

2. The method according to claim 1, characterized in that The step of grouping the multiple DNS servers to obtain multiple DNS server groups includes: obtaining a total number of the plurality of DNS servers and a server group size, wherein the server group size indicates the number of DNS servers grouped into the same group; Based on the total number of the multiple DNS servers and the server group size, the multiple DNS servers are grouped in a permutation and combination manner to obtain the multiple DNS server groups.

3. The method according to claim 1 or 2, characterized in that The cloud management platform is used to manage cloud infrastructure, and the cloud infrastructure includes the multiple DNS servers.

4. The method according to claim 3, characterized in that If the multiple DNS servers are located in multiple availability zones AZ in the cloud infrastructure, and the server group size is greater than or equal to the total number of the multiple AZs, each of the DNS server groups includes at least one DNS server in each of the AZs.

5. The method according to claim 3 or 4, characterized in that If the multiple DNS servers are located in multiple regions in the cloud infrastructure, the multiple regions correspond to the same virtual access address, and the domain name suffixes corresponding to the DNS server groups in the multiple regions are the same.

6. The method according to any one of claims 1 to 5, characterized in that: The domain name resolution request carries a target domain name, and the target domain name belongs to the target name zone. The corresponding DNS server group is determined from the multiple DNS server groups based on the target domain name and the target mapping relationship.

7. The method according to claim 6, characterized in that The corresponding DNS server is a DNS server group corresponding to a target domain name suffix, and the target domain name suffix is ​​a domain name suffix determined from domain name suffixes corresponding to the multiple DNS server groups using a longest suffix matching algorithm and matching the target domain name.

8. The method according to claim 6 or 7, characterized in that The DNS server that resolves the domain name resolution request is a DNS server in the corresponding DNS server group.

9. The method according to claim 8, characterized in that If the DNS servers included in the corresponding DNS server group are located in at least one availability zone AZ, the DNS server that resolves the domain name resolution request is the DNS server in the corresponding DNS server group located in the first AZ, and the first AZ is the AZ where the initiator of the domain name resolution request is located.

10. The method according to claim 9, characterized in that If the DNS server in the first AZ cannot resolve the target domain name, the DNS server that resolves the domain name resolution request is a DNS server in another AZ in the corresponding DNS server group except the first AZ.

11. A cloud management platform, characterized in that: The cloud management platform includes: a grouping module, used for grouping a plurality of DNS servers to obtain a plurality of DNS server groups, each DNS server group including at least one DNS server, and at least one different DNS server between different DNS server groups, and the plurality of DNS servers are used for resolving domain names in a target name area in a DNS name space; A suffix acquisition module, used to acquire multiple domain name suffixes, where the multiple domain name suffixes are suffixes of domain names in the target name area; A mapping relationship generating module, used to generate a target mapping relationship based on the multiple domain name suffixes and the multiple DNS server groups, wherein the target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the multiple DNS server groups; The suffix allocation module is used to allocate the multiple domain name suffixes to the corresponding DNS server group based on the target mapping relationship, so that the DNS server in the corresponding DNS server group resolves the domain name resolution request when receiving the domain name resolution request.

12. The cloud management platform according to claim 11, characterized in that: The grouping module comprises: a parameter acquisition unit, configured to acquire a total number of the plurality of DNS servers and a server group size, wherein the server group size indicates a number of DNS servers that are grouped into the same group; The grouping unit is used to group the multiple DNS servers in a permutation and combination manner based on the total number of the multiple DNS servers and the server group size to obtain the multiple DNS server groups.

13. The cloud management platform according to claim 11 or 12, characterized in that: The cloud management platform is used to manage cloud infrastructure, and the cloud infrastructure includes the multiple DNS servers.

14. The cloud management platform according to claim 13, characterized in that: If the multiple DNS servers are located in multiple availability zones AZ in the cloud infrastructure, and the server group size is greater than or equal to the total number of the multiple AZs, each of the DNS server groups includes at least one DNS server in each of the AZs.

15. The cloud management platform according to any one of claims 13 or 14, characterized in that: If the multiple DNS servers are located in multiple regions in the cloud infrastructure, the multiple regions correspond to the same virtual access address, and the domain name suffixes corresponding to the DNS server groups in the multiple regions are the same.

16. The cloud management platform according to any one of claims 11 to 15, characterized in that: The domain name resolution request carries a target domain name, and the target domain name belongs to the target name zone. The corresponding DNS server group is determined from the multiple DNS server groups based on the target domain name and the target mapping relationship.

17. The cloud management platform according to claim 16, characterized in that: The corresponding DNS server is a DNS server group corresponding to a target domain name suffix, and the target domain name suffix is ​​a domain name suffix determined from domain name suffixes corresponding to the multiple DNS server groups using a longest suffix matching algorithm and matching the target domain name.

18. The cloud management platform according to claim 16 or 17, characterized in that: The DNS server that resolves the domain name resolution request is a DNS server in the corresponding DNS server group.

19. The cloud management platform according to claim 18, characterized in that: If the DNS servers included in the corresponding DNS server group are located in at least one availability zone AZ, the DNS server that resolves the domain name resolution request is the DNS server in the corresponding DNS server group located in the first AZ, and the first AZ is the AZ where the initiator of the domain name resolution request is located.

20. The cloud management platform according to claim 19, characterized in that: If the DNS server in the first AZ cannot resolve the target domain name, the DNS server that resolves the domain name resolution request is a DNS server in another AZ in the corresponding DNS server group except the first AZ.

21. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each of which includes a processor and a memory; The processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster performs the steps of the domain name resolution method based on cloud computing technology as described in any one of claims 1-10.

22. A computer-readable storage medium, characterized in that: It includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the steps of the domain name resolution method based on cloud computing technology as described in any one of claims 1 to 10.

23. A computer program product comprising instructions, characterized in that When the instruction is executed by a computing device cluster, the computing device cluster executes the steps of the domain name resolution method based on cloud computing technology as described in any one of claims 1 to 10.

Images