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

Abstract

The present application belongs to the technical field of cloud computing. Disclosed are a domain name resolution method based on cloud computing technology, and a cloud management platform. The method is applied to a cloud management platform. The method comprises: grouping a plurality of DNS servers to obtain a plurality of DNS server groups, wherein the plurality of DNS servers are used for resolving domain names in a target name area in a DNS name space; acquiring a plurality of domain name suffixes, wherein the plurality of domain name suffixes are suffixes of the domain names in the target name area; generating a target mapping relationship on the basis of the plurality of domain name suffixes and the plurality of DNS server groups; and allocating the plurality of domain name suffixes to corresponding DNS server groups on the basis of the target mapping relationship, so that the DNS servers in the corresponding DNS server groups resolve a domain name resolution request upon receiving the domain name resolution request. In the present application, by means of flexibly grouping the DNS servers and scheduling the DNS servers in groups to perform domain name resolution, the high availability of a domain name resolution service is ensured.

Description

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

[0001] This application claims priority to Chinese patent application No. 202311694790.3, filed on December 11, 2023, entitled “A domain name configuration method and device based on load balancing”, and claims priority to Chinese patent application No. 202410390913.2, filed on March 30, 2024, entitled “Domain name resolution method and cloud management platform based on cloud computing technology”, 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 domain names into Internet Protocol (IP) addresses. This resolution is performed by Domain Name System (DNS) servers. When a client requests a domain name, it first sends a domain name query request to the local DNS server. If the local DNS 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 DNS server does not store the IP address corresponding to the domain name, the local DNS server will query the client on its behalf, starting with the root DNS server, then the top-level DNS server, and finally the authoritative DNS server, ultimately notifying the client of the obtained IP address. As can be seen from the above domain name resolution process, the authoritative DNS server plays a core role in the domain name resolution process, being responsible for resolving the IP address corresponding to the domain name.

[0004] In related technologies, to ensure 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 world 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.

[0006] Summary of the Invention

[0007] The present application provides a domain name resolution method and 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.

[0008] 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 comprising: grouping the multiple DNS servers to obtain multiple DNS server groups, each of the DNS server groups including at least one DNS server, and there being at least one different DNS server between different DNS server groups, the multiple DNS servers being used to resolve domain names within a target name area in a DNS namespace; obtaining multiple domain name suffixes, the multiple domain name suffixes being suffixes of domain names within the target name area; generating a target mapping relationship based on the multiple domain name suffixes and the multiple DNS server groups, the target mapping relationship being 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 corresponding DNS server groups based on the target mapping relationship, so that the DNS servers in the corresponding DNS server groups resolve the domain name resolution request when receiving the domain name resolution request.

[0009] It can be seen that for a limited number of DNS servers, the cloud management platform can reasonably group and generate target mapping relationships, so that when multiple DNS servers provide domain name resolution services to the outside world, they can schedule DNS servers for domain name resolution in groups based on the target mapping relationships. This not only allows for fine-grained management of domain name resolution services, but also reduces the explosion radius of domain name resolution services and improves the availability of domain name resolution services.

[0010] Optionally, grouping the multiple DNS servers to obtain multiple DNS server groups includes: obtaining the total number of the multiple DNS servers and the server group size, where the server group size indicates the number of DNS servers divided into the same group; and grouping 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.

[0011] That is, by grouping a limited number of DNS servers in a permutation and combination manner, more server groups can be obtained. As the number of DNS server groups increases, the explosion radius of a limited number of DNS servers when providing domain name resolution services to the outside world becomes smaller.

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

[0013] 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, each of the DNS server groups includes at least one DNS server in each of the AZs.

[0014] That is, if multiple DNS servers are distributed across multiple AZs, DNS server groups can be created so that each DNS server group includes DNS servers from every AZ. This allows each DNS server group to flexibly select the appropriate DNS server based on communication distance when resolving domain names with corresponding domain suffixes, improving domain name resolution efficiency.

[0015] Optionally, 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.

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

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

[0018] That is, when multiple DNS servers provide domain name resolution to the outside world, the cloud management platform resolves the domain name resolution request by scheduling the DNS server group to achieve refined management of domain name resolution within the DNS zone.

[0019] Optionally, the corresponding DNS server is a DNS server group corresponding to the target domain name suffix, and the target domain name suffix is ​​a domain name suffix determined from the domain name suffixes corresponding to the multiple DNS server groups using a longest suffix matching algorithm and matching the target domain name.

[0020] It can be seen that the longest suffix matching algorithm can determine the target domain name suffix with the highest similarity to the target domain name (or in other words, the one with the most identical parts with the target domain name), thereby improving the matching accuracy of the domain name suffix, so that the target DNS server group corresponding to the target domain name suffix that matches the target domain name can effectively resolve the target domain name.

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

[0022] Optionally, 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 located in the first AZ in the corresponding DNS server group, and the first AZ is the AZ where the initiator of the domain name resolution request is located.

[0023] Optionally, if the DNS server located 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.

[0024] It can be seen from this 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 located 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 efficiency of domain name resolution. When the DNS server in the target DNS server group that is located in the same AZ as the initiator of the domain name resolution request cannot resolve the target domain name, the domain name can also be resolved through the DNS servers in other AZs in the target DNS server group. In this way, when the DNS server group includes DNS servers in multiple AZs, the high availability of the domain name resolution service is further guaranteed when resolving a domain name with a certain domain name suffix.

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

[0026] In a third aspect, a computing device cluster is provided, wherein the computing device cluster includes at least one computing device, each computing device includes a processor and a memory, and 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 described in the first aspect above.

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

[0028] In a fourth aspect, a computer-readable storage medium is provided, which 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 described in the first aspect above.

[0029] In a fifth aspect, a computer program product comprising instructions is provided. When the 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 described in the first aspect.

[0030] The technical effects obtained in the above-mentioned second to fifth aspects are similar to the technical effects obtained by the corresponding technical means in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] FIG1 is a schematic diagram of an implementation environment of a domain name resolution method based on cloud computing technology provided in an embodiment of the present application;

[0032] FIG2 is a flow chart of a domain name resolution method based on cloud computing technology provided in an embodiment of the present application;

[0033] FIG3 is a schematic diagram of a process for performing domain name resolution based on a target mapping relationship according to an embodiment of the present application;

[0034] 4 is a schematic diagram of selecting a DNS server from a target DNS server group for domain name resolution according to an embodiment of the present application;

[0035] 5 is a schematic diagram of another embodiment of the present application to select a DNS server from the target DNS server group for domain name resolution;

[0036] FIG6 is a schematic diagram of a multi-region scheduling DNS server group for domain name resolution according to an embodiment of the present application;

[0037] FIG7 is a schematic diagram of a logic implementation of a method for performing domain name resolution on a cloud management platform provided in an embodiment of the present application;

[0038] FIG8 is a schematic diagram of the structure of a cloud management platform provided in an embodiment of the present application;

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

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

[0041] FIG11 is a schematic diagram of a network connection relationship of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0043] To facilitate understanding, before explaining in detail the domain name resolution method based on cloud computing technology provided in the embodiment of the present application, the terminology, application scenarios and implementation environment involved in the embodiment of the present application are first introduced.

[0044] First, the terms involved in the embodiments of the present application are introduced.

[0045] 1. Basic Services

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

[0047] 2. DNS service

[0048] Also known as domain name resolution service, it is the process of converting a domain name into an Internet Protocol (IP) address. The domain name resolution process is as follows: when a client initiates an access request for 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, 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 will perform a query on behalf of the client, from the root domain name server to the top-level domain name server, and then to the authoritative domain name server, and finally return the obtained IP address of the domain name to the client.

[0049] 3. DNS zone

[0050] A DNS zone is a continuous tree within the DNS namespace, dividing the domain namespace into smaller administrative units as needed. A DNS zone is an administrative unit consisting of a single area in the DNS namespace or multiple closely adjacent subdomains with a hierarchical relationship.

[0051] It's important to note that DNS servers manage namespaces using zones, not domains. The names of the zones managed by a DNS server correspond one-to-one with the names of the domains in the DNS namespace it manages. A single DNS server can manage one or more DNS zones, and a single DNS zone can be managed by multiple DNS servers.

[0052] 4. Authoritative Domain Name Server

[0053] A DNS server that can authoritatively respond to domain name queries / resolution requests for the DNS zone it manages, that is, a DNS server that can complete IP mapping.

[0054] 5. Recursive Name Server

[0055] An intermediate proxy server between the DNS client and the authoritative domain name server.

[0056] 6. Layer 4 load balancing

[0057] A software device that forwards messages to different back-end servers based on the message information of the Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).

[0058] 7. Blast radius

[0059] In domain name resolution services, the blast radius refers to the range of impact on users when a DNS server fails.

[0060] 8. Fault Isolation

[0061] Fault isolation means controlling the impact of a fault to a limited scope.

[0062] Next, the application scenarios of the embodiments of the present application are briefly introduced.

[0063] Domain name resolution is the process of converting a domain name into an IP address, and the resolution work is completed by a DNS server. Among them, the authoritative domain name 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, in order to ensure the high availability of domain name resolution services, a large number of DNS servers need to be deployed as authoritative domain name servers, and these DNS servers back up each other, and provide domain name resolution services to the outside world through these DNS servers. In this way, since there are enough DNS servers, 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 for domain name resolution services.

[0064] Based on this, an embodiment of the present application provides a domain name resolution method based on cloud computing technology. For domain names within a target DNS zone, based on limited DNS server resources, multiple DNS servers are rationally grouped to obtain multiple DNS server groups, each of which is used to provide resolution services for some domain names within the target DNS zone. In other words, when the number of DNS servers is limited, an embodiment of the present application provides a more fine-grained domain name management solution for domain names within a single DNS zone, or domain names within a small number of DNS zones, ensuring high availability of the domain name resolution service while minimizing the explosion radius of the domain name resolution service.

[0065] The domain name resolution method based on cloud computing technology provided in the embodiments of the present application is applied to a cloud management platform. The cloud management platform can be a server cluster or distributed system composed of multiple physical servers, or 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 networks (CDNs), and big data and artificial intelligence platforms, or a cloud computing service center.

[0066] In an embodiment 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 tenants to register domain names, or submit domain names that need to be managed, or submit domain name resolution requests that need to resolve IP addresses.

[0067] In an embodiment of the present application, the cloud management platform can also provide a domain name management service interface and display it to users of the cloud management platform. The configuration interface is used for users to input domain name information of a certain name area, the total number of multiple DNS servers, the server group size, the deployment location of the DNS server and other DNS server information, so that the cloud management platform can execute the domain name resolution method based on cloud computing technology provided in an embodiment of the present application, determine multiple domain name suffixes based on the domain name information, group 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.

[0068] The user here can be an administrator of the cloud management platform or a tenant of the cloud management platform.

[0069] In some embodiments, when a user is a tenant of a 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. Specifically, the cloud management platform executes the cloud computing-based domain name resolution method provided in the embodiments of the present application to generate a target mapping relationship between the domain name suffix and the DNS server group for the tenant.

[0070] In this way, after the tenant obtains the target mapping relationship from the cloud management platform, it can perform fine-grained management of the domain name resolution services provided by its multiple DNS servers based on the target mapping relationship.

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

[0072] Optionally, when the cloud management platform generates a 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 can schedule multiple DNS servers within the cloud infrastructure to perform domain name resolution based on the target mapping relationship.

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

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

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

[0076] It can be seen that in the embodiment of the present application, the cloud management platform can provide domain name management services to the outside world, so as to provide users with DNS server grouping schemes and domain name suffix allocation schemes, that is, based on the domain name information and DNS server information managed by the user, generate a target mapping relationship between the domain name suffix and the DNS server group for the user. The cloud management platform can also provide domain name resolution services to the outside world, based on the situation of multiple DNS servers in the cloud infrastructure managed by the cloud management platform, and the domain name information in the target name area, generate a target mapping relationship between the domain name suffix and the DNS server group, and based on the target mapping relationship, schedule the DNS server in the corresponding DNS server group to resolve the domain name resolution request. The embodiment of the present application does not impose any restrictions on this.

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

[0078] Please refer to Figure 1, which is a schematic diagram of an implementation environment provided by an embodiment of the present application, and the implementation environment includes a tenant side and a service side (i.e., a cloud platform). On the service side, a cloud management platform 20 is used to manage a cloud infrastructure 1, which includes multiple regions, such as region 10, region 11, and region 12; each region includes multiple data centers, such as data center 101, data center 102, and data center 103, and each cloud data center includes multiple DNS servers that provide domain name resolution services, such as server 1011 and server 1012. On the tenant side, tenant A connects to the Internet through client 11, and tenant B connects to the Internet through client 12 and logs in to the cloud management platform 20.

[0079] The client 11 and the client 12 may be, for example, a mobile phone with Internet access function, a personal computer, a personal digital assistant, or a thin client terminal device.

[0080] Optionally, the cloud management platform 20 provides a configuration interface, and tenant A and tenant B enter the 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 based on the configuration information. For example, it can create or delete a cloud instance, and can manage the cloud instance throughout its life cycle based on the configuration information.

[0081] Optionally, each region includes multiple availability zones (AZs), which are not shown in Figure 1. An AZ is a collection of one or more data centers, each with independent water and electricity. Within an AZ, computing, network, storage, and other resources are logically divided into multiple clusters. Multiple AZs in a region can be connected via high-speed fiber optics to meet user needs for building high-availability systems across AZs.

[0082] As an example, area 10 may include AZ1 and AZ2, which are communicatively connected, wherein AZ1 includes data center 101 and data center 102, and AZ2 includes data center 103. This embodiment of the present application does not limit this.

[0083] It should be understood that regions and availability zones are used to describe the location of data centers, and tenants can create resources in specific regions and availability zones. In the embodiments of this application, regions and availability zones are used to explain the location of DNS servers, thereby determining whether the domain name resolution services provided by multiple DNS servers are deployed within a single data center, within a single AZ, across multiple AZs, or across regions.

[0084] It should be noted that Figure 1 only uses two tenants, two clients, and cloud infrastructure 1 including three regions as an example, and does not constitute a restriction on the number and type of tenant-side clients, cloud infrastructure, regions, AZs, data centers, etc. in this implementation environment.

[0085] In an embodiment 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 that need to be managed, or submit domain name resolution requests that need to resolve IP addresses.

[0086] In an embodiment 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 group size, the deployment location of the DNS server, etc., so that the cloud management platform can execute the domain name resolution method based on cloud computing technology provided in the embodiment of the present application, and determine the target mapping relationship between the domain name suffix of the target name zone and the DNS server group.

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

[0088] Optionally, when a target mapping relationship is generated, the cloud management platform may also send the target mapping relationship to the target device so that the target device can call the corresponding DNS server group based on the target mapping relationship to resolve the domain name in the target name area.

[0089] That is, the embodiment of the present application does not restrict the execution entity that schedules and manages multiple DNS servers to resolve domain names within the target name zone based on the target mapping relationship.

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

[0091] Optionally, the load balancing device can work at the transport layer (i.e., the fourth network layer). The load balancing device can also be called a four-layer load balancing device to forward domain name resolution requests sent using TCP or UDP messages, and then forward the message to the corresponding target DNS server group on the back end based on the target domain name carried in the domain name resolution request.

[0092] It should be understood that when the cloud management platform executes the domain name resolution method based on cloud computing technology provided in the embodiment of the present application, it only uses the above-mentioned management device and load balancing device as examples, and can also include more or fewer devices to combine to implement the domain name resolution method. The embodiment of the present application does not limit the specific implementation method of the corresponding device in the cloud management platform.

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

[0094] It should be noted that the application scenarios and implementation environments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0095] Next, the domain name resolution method based on cloud computing technology provided in an embodiment of the present application is introduced.

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

[0097] 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. The multiple DNS servers are used to resolve domain names in a target name area in the DNS name space.

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

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

[0100] 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).

[0101] This shows that when grouping multiple DNS servers, flexible grouping can achieve the maximum number of DNS server groups, provided there are no restrictions on the number of groups or the number of DNS servers within a DNS server group. When the number of DNS server groups is the largest, the blast radius is 1 / the number of DNS server groups, which is the smallest. This shows that for a limited number of DNS servers, reasonable grouping not only allows domain name resolution to be performed through different DNS server groups, enabling fine-grained management of domain name resolution services, but also reduces the blast radius of the domain name resolution service, improving its availability.

[0102] In some embodiments, different DNS server groups are used to resolve domain names with different domain name suffixes. If one DNS server group fails and is unable to resolve domain names with the corresponding domain name suffix, another DNS server group is needed to resolve domain names with that domain name suffix to ensure high availability of the domain name resolution service. To this end, a backup relationship is established between multiple DNS server groups, that is, there are overlapping DNS servers between different DNS server groups.

[0103] After the multiple DNS servers are grouped, 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 may be partially the same, that is, different DNS server groups may have at least one common DNS server.

[0104] In this case, after executing the above step 201 to group the DNS server a, DNS server b and DNS server c in the above example, multiple DNS server groups are obtained, including: 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).

[0105] That is, for multiple DNS server groups, when there is a common DNS server among different DNS servers, not only can the maximum number of groups be guaranteed, but also a backup relationship can exist between the server groups, thereby improving the availability of the domain name resolution service.

[0106] In some embodiments, when at least one different DNS server exists between the DNS service groups, the server group size can also be limited so that the resulting multiple DNS server groups have the same size, that is, each DNS server group includes the same number of DNS servers.

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

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

[0109] The server group size can be any positive integer greater than or equal to 1.

[0110] It should be understood that after grouping multiple DNS servers in a permutation and combination manner, the multiple DNS server groups obtained have the same size, and there is at most one common DNS server between any two DNS server groups.

[0111] As an example, if multiple DNS servers include DNS server a, DNS server b, DNS server c and DNS server d, and the server group size is 2, then after grouping the 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).

[0112] It can be seen that the embodiment of the present application can obtain more server groups by grouping a limited number of DNS servers through permutations and combinations. As the number of DNS server groups increases, the explosion radius when multiple DNS servers provide domain name resolution services to the outside world becomes smaller.

[0113] Moreover, when resolving domain names within the target name zone, the embodiment of the present application schedules the DNS server to resolve the target domain name based on the target DNS server group. Therefore, when a DNS server group fails, it only affects the resolution service of the domain name with the domain name suffix corresponding to the DNS server group, and does not affect the domain name resolution service of other DNS server groups. Therefore, in the domain name resolution method based on cloud computing technology provided by the embodiment of the present application, when multiple DNS servers provide domain name resolution services to the outside world, the explosion radius of the domain name resolution service is 1 / the number of DNS server groups, which greatly reduces the explosion radius when providing domain name resolution services for a single or a small number of domain names within a DNS zone.

[0114] As mentioned above, in a cloud infrastructure managed by a cloud management platform, multiple DNS servers can be located in one availability zone (AZ) or in multiple AZs. The following describes these two scenarios.

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

[0116] As an example, assuming that the total number of DNS servers is N and the server group size is R, the following Table 1 shows the DNS server groups obtained after grouping multiple DNS servers when multiple DNS servers are located in one AZ, as well as the explosion radius corresponding to different grouping situations.

[0117] Table 1

[0118] As shown in Table 1 above, the blast radius is calculated as 1 / C(N, R), where C represents permutations and combinations. For example, if the total number of DNS servers is 6 and the server group size is 2, then every two DNS servers are grouped together. By permuting and combining these 6 DNS servers, we can obtain C(6, 2) = 15 DNS server groups. In this grouping scenario, when these 6 DNS servers provide domain name resolution services for the target DNS zone, their corresponding blast radius is 1 / 15.

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

[0120] As an example, assuming that the total number of DNS servers is N, the server group size is R, and the number of AZs is K, the following Table 2 shows the DNS server groups obtained after grouping multiple DNS servers when multiple DNS servers are located in two AZs, as well as the explosion radius corresponding to different grouping situations.

[0121] Table 2

[0122] Refer to Table 2 above. The calculation method of explosion radius is 1 / C(N / 2, K) 2 , C represents permutations and combinations, 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 in two AZs. In this case, the permutations and combinations of the 16 DNS servers can be obtained as C(16 / 2, 2). 2 =784 DNS server groups. In this grouping scenario, when these 16 DNS servers provide domain name resolution services to the target DNS zone, their corresponding explosion radius is 1 / 784.

[0123] As an example, assuming that the total number of DNS servers is N, the server group size is R, and the number of AZs is K, the following Table 3 shows the DNS server groups obtained after grouping multiple DNS servers when multiple DNS servers are located in three AZs, as well as the explosion radius corresponding to different grouping situations.

[0124] Table 3

[0125] Refer to Table 3 above. The calculation method of explosion radius is 1 / C(N / 2, K) 3 , C represents permutations and combinations, 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 in three AZs. In this case, the permutations and combinations of the 15 DNS servers can be obtained as C(15 / 3, 2). 3 = 1000 DNS server groups. In this grouping scenario, when these 15 DNS servers provide domain name resolution services for the target DNS zone, their corresponding explosion radius is 1 / 1000.

[0126] Step 202: Acquire multiple domain name suffixes, which are suffixes of domain names in the target name area.

[0127] In one possible implementation, the implementation process of step 202 may be: based on the domain name suffix extraction rule, suffix extraction processing is performed on the domain names in the target name area to obtain multiple domain name suffixes; wherein the domain name suffix extraction rule indicates that the domain name suffix is ​​extracted from the domain name according to the specified domain name level.

[0128] It should be noted that the above-mentioned domain name suffix extraction rules can be configured by the administrator. The domain name level can be a first-level domain name, that is, the first-level domain name in each domain name is extracted as the suffix; the domain name level can also be a second-level domain name or a third-level domain name, that is, the second-level domain name or the third-level domain name is extracted as the suffix. This embodiment of the present application does not limit this. In addition, for domain names within the target name area, the embodiment of the present application does not limit the number of domain name suffixes extracted.

[0129] Step 203: Based on the multiple domain name suffixes and the multiple DNS server groups, a target mapping relationship is generated, 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.

[0130] In a possible implementation, the implementation process of step 203 may be: determining the correspondence between the domain name suffix and the DNS server group according to the quantity relationship between the domain name suffix and the DNS server group, so as to obtain the target mapping relationship.

[0131] Among them, in this target mapping relationship, the domain name suffix and the DNS server group can correspond one to one, many to one, or one to many, and the embodiment of the present application does not limit this.

[0132] In some embodiments, taking into account the possible dependency between domain name suffixes, in order to avoid mutual influence during resolution of domain names corresponding to two domain name suffixes, different DNS server groups need to be assigned to domain name suffixes with a dependency, that is, there is no identical DNS server in the DNS server group corresponding to the two domain name suffixes with a dependency, so there is no DNS server storing the domain names corresponding to the two domain name suffixes with a dependency.

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

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

[0135] It should be noted that when assigning multiple domain name suffixes to multiple DNS servers, the DNS server group corresponding to each domain name suffix can be coordinated and determined based on the relationship between the domain name suffixes and / or the overlap of DNS servers in the DNS server group. The embodiment of the present application does not impose any restrictions on this. The dependency relationship between the above-mentioned domain name suffixes is merely an example and does not constitute a limitation on the specific implementation method of the above-mentioned step 203.

[0136] Step 204: Based on the target mapping relationship, multiple domain name suffixes are allocated to corresponding DNS server groups, so that the DNS servers in the corresponding DNS server groups resolve the domain name resolution requests when receiving the domain name resolution requests.

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

[0138] In some embodiments, when the domain name resolution request carries a target domain name, and the target domain name belongs to a target name zone, the corresponding DNS server group is determined from a plurality of DNS server groups based on a mapping relationship between the target domain name and the target.

[0139] In one possible implementation, the corresponding DNS server may be a DNS server group corresponding to a target domain name suffix, wherein the target domain name suffix is ​​a domain name suffix determined from domain name suffixes corresponding to multiple DNS server groups using a longest suffix matching algorithm and matching the target domain name.

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

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

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

[0143] 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 located in the first AZ in the corresponding DNS server group.

[0144] The first AZ is the AZ where the initiator of the domain name resolution request is located.

[0145] Optionally, 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 except the first AZ in the corresponding DNS server group.

[0146] It can be seen that in the embodiment 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, multiple domain name suffixes are determined based on the domain names in the target name area, and then a target mapping relationship is generated based on the multiple domain name suffixes and multiple DNS server groups, and the multiple domain name suffixes are assigned to the corresponding DNS server groups based on the target mapping relationship, so that each DNS server group can resolve the domain name with the corresponding domain name suffix. That is, for a limited number of DNS servers, the cloud management platform reasonably groups and generates a target mapping relationship, so that when multiple DNS servers provide domain name resolution services to the outside world, they can dispatch DNS servers for domain name resolution in groups based on the target mapping relationship. This not only allows for fine-grained management of domain name resolution services, but also reduces the explosion radius of domain name resolution services and improves the availability of domain name resolution services.

[0147] Based on the domain name resolution method based on cloud computing technology shown in the above embodiment, next, taking the cloud management platform managing cloud infrastructure, where the cloud infrastructure includes multiple DNS servers as an example, the cloud management platform generates target mapping relationships for multiple DNS servers and domain names in the target name area in the DNS name space in the manner shown in the above embodiment. The cloud management platform can also schedule the corresponding DNS server group to resolve the corresponding domain name based on the target mapping relationship.

[0148] The target mapping relationship is used to indicate the domain name suffix corresponding to each DNS server group in the multiple DNS server groups.

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

[0150] Step 301: Receive a domain name resolution request, the domain name resolution request carries a target domain name, and the target domain name belongs to a target name zone.

[0151] It should be noted that, after generating the above-mentioned target mapping relationship, the cloud management platform may first store the target mapping relationship, and then execute step 301 when subsequently receiving a domain name resolution request.

[0152] That is, after receiving the domain name resolution request sent by the tenant side, the cloud management platform first resolves the target domain name from the domain name request, and when the target domain name belongs to the target DNS zone, performs the following step 302 based on the target domain name.

[0153] Step 302: parse the target domain name based on the target mapping relationship.

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

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

[0156] In a possible implementation, the implementation process of the above step (1) can be: using the longest suffix matching algorithm to determine the target domain name suffix that matches the target domain name from the domain name suffixes corresponding to multiple DNS server groups; and determining the DNS server group corresponding to the target domain name suffix as the target DNS server group.

[0157] It should be noted that the domain name suffix can be the first-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.

[0158] 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, the longest suffix matching algorithm is used to determine xxx.yyy.example.com, which has the highest domain name level, as the target domain name suffix that matches the target domain name.

[0159] It can be seen that the longest suffix matching algorithm can determine the target domain name suffix with the highest similarity to the target domain name (or in other words, the one with the most identical parts with the target domain name), thereby improving the matching accuracy of the domain name suffix, so that the target DNS server group corresponding to the target domain name suffix that matches the target domain name can effectively resolve the target domain name.

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

[0161] 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 domain name suffix.

[0162] In a possible implementation, the implementation process of the above step (2) may be: selecting a DNS server from the target DNS server group; sending the target domain name to the selected DNS server to instruct the selected DNS server to resolve the target domain name.

[0163] Among them, when selecting a DNS server from the target DNS server group, a DNS server can be selected from the DNS servers in a random, polling or other manner. The embodiment of the present application does not limit the selection method.

[0164] As an example, referring to FIG4 , based on the domain name suffix matching the target domain name, the second DNS server group is determined as the target DNS server group, and after selecting a DNS server from the second DNS server group, the target domain name is sent to the selected DNS server, instructing the DNS server to resolve the target domain name.

[0165] 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. This embodiment of the present application does not impose any restrictions on this.

[0166] In some embodiments, when multiple DNS servers are located in multiple AZs, when dividing DNS server groups, each DNS server group can include DNS servers from 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. In this case, selecting a DNS server from the target DNS server group can be implemented by: determining a first AZ in which the initiator of the domain name resolution request is located; and selecting a DNS server from the target DNS server group located in the first AZ. The first AZ is any one of the multiple AZs.

[0167] 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 the domain name resolution service. In this way, when the DNS server in the same AZ is used to provide the domain name resolution service, the communication route between the initiator of the domain name resolution request and the DNS server is shorter, the delay of the domain name resolution is shorter, and the domain name resolution efficiency is high.

[0168] Optionally, if the DNS server in the first AZ cannot resolve the target domain name, a DNS server in another AZ except the first AZ is selected from the target DNS server group to continue resolving the target domain name.

[0169] As an example, referring to Figure 5, the cloud management platform determines the target DNS server group based on the domain name suffix that matches the target domain name. If the initiator of the domain name resolution request is located in AZ1, DNS server p or DNS server q in AZ1 is selected 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, DNS server m or DNS server n in AZ2 is selected from the target DNS server group to resolve the target domain name.

[0170] It should be understood that Figure 5 only uses the example of selecting DNS server q in AZ1 to resolve the target domain name, or selecting DNS server m in AZ2 to resolve the target domain name. In actual applications, DNS server p in AZ1 can also be selected to resolve the target domain name. If the DNS server p cannot resolve the target domain name, DNS server n in AZ2 is selected to resolve the target domain name. The embodiment of the present application does not limit this.

[0171] It can be seen from this 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 located 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 efficiency of domain name resolution. When the DNS server in the target DNS server group that is located in the same AZ as the initiator of the domain name resolution request cannot resolve the target domain name, the domain name can also be resolved through the DNS servers in other AZs in the target DNS server group. In this way, when the DNS server group includes DNS servers in multiple AZs, the high availability of the domain name resolution service is further guaranteed when resolving a domain name with a certain domain name suffix.

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

[0173] Since the virtual access address of each region is the same, during the domain name resolution process, the cloud management platform can select a region from 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 server in the selected target DNS server group to resolve the target domain name.

[0174] As an example, referring to Figure 6, multiple DNS servers (i.e., DNS servers 11-1n, and DNS servers 21-2n) are used to resolve domain names within the target DNS zone. When a domain name resolution request contains a domain name within the DNS zone, DNS servers in both region 1 and region 2 can provide domain name resolution services. Therefore, both region 1 and region 2 publish the same virtual access address.

[0175] The virtual access address may be an intranet IP address, such as 10.10.10.10. In practical applications, a public IP address may also be used as the virtual access address, which is not limited in this embodiment of the present application.

[0176] It should be noted that since multiple DNS servers are used to resolve domain names within the target DNS zone, the domain name suffix corresponding to the DNS server group deployed in 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 is also different. Therefore, the mapping relationship between the domain name suffix and DNS server group in each region may be slightly different.

[0177] For example, region 1 includes 10 DNS server groups and region 2 includes 5 DNS server groups. If 10 domain name suffixes are determined based on the domain names in the target DNS zone, the target mapping relationships stored in region 1 can be the mapping relationships between the 10 domain name suffixes and the 10 DNS server groups, while the target mapping relationships stored in region 2 can be the mapping relationships between the 10 domain name suffixes and the 5 DNS server groups.

[0178] As can be seen from this, when multiple DNS servers are located in different regions, when DNS servers located in multiple regions are used to resolve domain names within the target DNS zone, the same virtual access address can be set for multiple regions, and based on the domain names within the target name zone, the same domain name suffix can be configured for the DNS server groups within multiple regions. In this way, when a domain name resolution request for any domain name within the DNS zone is forwarded to any 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 serve as backup for each other, thereby ensuring high availability of the domain name resolution service within the target DNS zone.

[0179] In summary, in an embodiment of the present application, the cloud management platform obtains a maximum number of multiple DNS server groups by reasonably grouping the multiple DNS servers included in the cloud infrastructure; and generates a target mapping relationship between the domain name suffix and the DNS server group in combination with the domain name suffix of the domain name in the target DNS zone. Based on the target mapping relationship, after receiving a domain name resolution request, 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 through the DNS servers in the target DNS server group. It can be seen that in an embodiment of the present application, when the cloud management platform performs domain name resolution based on the target mapping relationship, domain names with the same domain name suffix can be resolved through 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 DNS server group fails, it only affects the domain name suffix corresponding to the DNS server group, and will not affect the resolution service of domain names with other domain name suffixes. In this way, based on the target mapping relationship, the DNS server group is scheduled to provide domain name resolution services for domain names in the target name area. This not only allows for fine-grained management of domain name resolution services based on DNS servers, but also reduces the explosion radius of domain name resolution services and improves the availability of domain name resolution services.

[0180] Based on the domain name resolution method based on computing technology shown in the above embodiment, for ease of understanding, the following uses the cloud management platform as the execution entity, combined with Figure 7 below, to exemplarily explain the domain name resolution method based on computing technology.

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

[0182] Furthermore, after receiving the domain name resolution request, the cloud management platform determines the target DNS server group corresponding to the target domain name based on the target domain name and 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.

[0183] As can be seen from this, for multiple DNS servers capable of resolving domain names within a DNS zone, the cloud management platform first groups the DNS servers into multiple DNS server groups. It then assigns the domain name suffixes of the domain names in the DNS zone to the multiple DNS server groups, generating a target mapping relationship between the domain name suffixes and the DNS server groups. This allows multiple DNS servers to provide external domain name resolution, and domain name resolution requests can be forwarded by scheduling DNS server groups, enabling refined management of domain name resolution within the DNS zone.

[0184] Moreover, dividing the limited DNS servers into multiple DNS server groups can minimize the explosion radius of the domain name resolution service, so that when a DNS server group fails, it only affects the resolution of domain names with the domain name suffix corresponding to the DNS server group, and does not affect the domain name resolution services of other domain name suffixes; at the same time, since the multiple DNS servers included in the DNS server group can all resolve domain names with corresponding domain name suffixes, when a single DNS server in a DNS server group fails, the other DNS servers in the DNS server group can still provide domain name resolution services to the outside world, thereby improving the availability of the domain name resolution service.

[0185] In addition, when resolving domain names within the target DNS zone, the embodiments of the present application can be scheduled in units of DNS server groups. When the number of DNS server groups is maximized, the explosion radius of the domain name resolution service can be minimized, thereby improving the availability of the domain name resolution service.

[0186] Figure 8 is a structural diagram of a cloud management platform provided in an embodiment of the present application. Referring to Figure 8 , the cloud management platform includes: a grouping module 801 , a suffix acquisition module 802 , a mapping relationship generation module 803 and a suffix allocation module 804 .

[0187] A grouping module 801 is configured to group multiple DNS servers to obtain multiple DNS server groups, each DNS server group including at least one DNS server, and different DNS server groups having at least one different DNS server. The multiple DNS servers are configured to resolve domain names within a target name zone in a DNS namespace.

[0188] The suffix obtaining module 802 is used to obtain a plurality of domain name suffixes, where the plurality of domain name suffixes are suffixes of domain names in the target name area;

[0189] A mapping relationship generating module 803 is configured to 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;

[0190] The suffix allocation module 804 is used to allocate multiple domain name suffixes to the corresponding DNS server group based on the target mapping relationship, so that the DNS servers in the corresponding DNS server group resolve the domain name resolution request when receiving the domain name resolution request.

[0191] Optionally, the grouping module 801 includes:

[0192] a parameter obtaining unit, configured to obtain 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;

[0193] 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 multiple DNS server groups.

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

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

[0196] Optionally, if 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.

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

[0198] Optionally, the corresponding DNS server is a DNS server group corresponding to the target domain name suffix, and the target domain name suffix is ​​a domain name suffix determined from domain name suffixes corresponding to multiple DNS server groups using a longest suffix matching algorithm and matching the target domain name.

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

[0200] 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 located in the first AZ in the corresponding DNS server group, and the first AZ is the AZ where the initiator of the domain name resolution request is located.

[0201] Optionally, 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 except the first AZ in the corresponding DNS server group.

[0202] In an embodiment of the present application, the cloud management platform, based on multiple DNS servers included in the cloud infrastructure, reasonably groups the multiple DNS servers to obtain a maximum number of DNS server groups. Furthermore, the cloud management platform generates a target mapping relationship between the domain name suffix and the DNS server group, based on the domain name suffix within the target DNS zone. That is, for a limited number of DNS servers, the cloud management platform reasonably groups and generates a target mapping relationship, so that when multiple DNS servers provide domain name resolution services externally, the cloud management platform can schedule DNS servers for domain name resolution in groups based on the target mapping relationship. This not only enables fine-grained management of domain name resolution services, but also reduces the explosion radius of domain name resolution services, thereby improving the availability of domain name resolution services.

[0203] Furthermore, when the cloud management platform schedules the DNS server to perform domain name resolution, the cloud management platform can, based on the target mapping relationship, enable domain names with the same domain name suffix to be resolved through the DNS servers in the same DNS server group. Moreover, since there is at least one different DNS server between different DNS server groups, when a DNS server group fails, it only affects the domain name suffix corresponding to the DNS server group, and does not affect the resolution service of domain names with other domain name suffixes. In this way, based on the target mapping relationship, the DNS server group is scheduled to provide domain name resolution services for domain names within the target name area. This not only allows for fine-grained management of domain name resolution services based on DNS servers, but also reduces the explosion radius of the domain name resolution service and improves the availability of the domain name resolution service.

[0204] It should be noted that: the cloud management platform provided in the above embodiment constructs a target mapping relationship, and when resolving the domain name of the domain name in the target DNS zone based on the target mapping relationship, only the division of the above functional modules is used as an example. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the cloud management platform is 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 embodiment and the domain name resolution method embodiment based on cloud computing technology shown in Figure 2 above belong to the same concept. The specific implementation process is detailed in the above method embodiment and will not be repeated here.

[0205] In the above-described device embodiment, the grouping module, suffix acquisition module, mapping relationship generation module, and suffix assignment module can all be implemented via software or hardware. By way of example, the implementation of the grouping module will be described below using the grouping module as an example. Similarly, the implementation of the suffix acquisition module, mapping relationship generation module, and suffix assignment module can refer to the implementation of the grouping module.

[0206] As an example of a software functional unit, a grouping module may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the 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 used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple geographically close data centers. Typically, a region may include multiple AZs.

[0207] Similarly, multiple hosts / virtual machines / containers running the code can be distributed within the same virtual private cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

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

[0209] The multiple computing devices included in the grouping module can be distributed in the same region or in different regions. The multiple computing devices included in the grouping module can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the grouping module can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

[0210] It should be noted that, in other embodiments, the grouping module can be used to execute any step in the domain name resolution method based on cloud computing technology, and the suffix acquisition module, mapping relationship generation module, and suffix assignment module can also be used to execute any step in the domain name resolution method based on cloud computing technology. In other words, the steps that the grouping module, suffix acquisition module, mapping relationship generation module, and suffix assignment module are responsible for implementing can be specified as needed. By having the grouping module, suffix acquisition module, mapping relationship generation module, and suffix assignment module respectively implement different steps in the domain name resolution method based on cloud computing technology, the full functionality of the aforementioned cloud management platform can be achieved.

[0211] The present application also provides a computing device 100. As shown in FIG9 , computing device 100 includes a bus 102, a processor 104, a memory 106, and a communication interface 108. Processor 104, memory 106, and communication interface 108 communicate with each other via bus 102. Computing device 100 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 100.

[0212] Bus 102 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG9 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 102 may include a path for transmitting information between various components of computing device 100 (e.g., memory 106, processor 104, and communication interface 108).

[0213] The processor 104 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP). An integrated circuit may include an ASIC, a programmable logic device (PLD), or a combination thereof. Optionally, the PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.

[0214] The memory 106 may include volatile memory, such as random access memory (RAM). The processor 104 may also include non-volatile memory, such as read-only memory (ROM), 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 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 via the bus 102, or the memory 106 is integrated with the processor 104.

[0215] The memory 106 stores executable program code, and the processor 104 executes the executable program code to implement the functions of the aforementioned grouping module, suffix acquisition module, mapping relationship generation module, and suffix assignment module, thereby implementing the domain name resolution method based on cloud computing technology shown in FIG2 . In other words, the memory 106 stores instructions for executing the domain name resolution method based on cloud computing technology shown in FIG2 .

[0216] The communication interface 108 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 a communication network.

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

[0218] As shown in Figure 10, the computing device cluster includes at least one computing device 100. The memory 106 in one or more computing devices 100 in the computing device cluster may store the same instructions for executing the domain name resolution method based on cloud computing technology.

[0219] In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the domain name resolution method based on cloud computing technology. In other words, the 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.

[0220] The memory 106 in different computing devices 100 in the computing device cluster may store different instructions, each for executing a portion of the functions of the cloud management platform shown in FIG8 . That is, the instructions stored in the memory 106 in different computing devices 100 may implement the functions of one or more of the grouping module, the suffix acquisition module, the mapping relationship generation module, and the suffix assignment module.

[0221] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network (WAN) or a local area network (LAN), etc. FIG11 shows a possible implementation. As shown in FIG11 , two computing devices 100A and 100B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 106 in the computing device 100A stores instructions for executing the functions of a grouping module, a suffix acquisition module, and a suffix matching module. At the same time, the memory 106 in the computing device 100B stores instructions for executing the functions of a suffix assignment module.

[0222] The connection method between the computing device clusters shown in Figure 11 can be based on the consideration that after the domain name resolution method based on cloud computing technology provided by this application generates a target mapping relationship on the cloud management platform, 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 interactive processes and data configuration operations. Therefore, the functions of the suffix allocation module related to domain name resolution are separately handed over to the computing device 100B for execution.

[0223] It should be understood that the functions of the computing device 100A shown in FIG10 may also be completed by multiple computing devices 100. Similarly, the functions of the computing device 100B may also be completed by multiple computing devices 100.

[0224] The present application also provides another computing device cluster. The connection relationship between the computing devices in this computing device cluster can be similar to the connection methods of the computing device clusters shown in Figures 10 and 11. However, the memory 106 in one or more computing devices 100 in this computing device cluster can store the same instructions for executing the domain name resolution method based on cloud computing technology.

[0225] In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the domain name resolution method. In other words, the combination of one or more computing devices 100 can jointly execute instructions for executing the domain name resolution method based on cloud computing technology.

[0226] It should be noted that the memory 106 in different computing devices 100 in the computing device cluster can store different instructions for executing some functions of the domain name resolution system based on cloud computing technology. In other words, the instructions stored in the memory 106 in different computing devices 100 can implement the functions of one or more devices in the cloud management platform shown in Figure 8.

[0227] Furthermore, Figures 9-11 provided in the embodiments of the present application merely illustrate that memory 106 stores instructions for executing the cloud computing-based domain name resolution method shown in Figure 2 , and do not limit the instructions that may be stored in the memory. In other words, the memory shown in Figures 9-11 may also include a grouping module, a suffix acquisition module, a mapping relationship generation module, and a suffix assignment module, and the embodiments of the present application do not impose any limitations on this.

[0228] The present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device, or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the steps of the domain name resolution method based on cloud computing technology shown in the above embodiment.

[0229] The present application also provides a computer program product including instructions. This computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to perform the steps of the cloud computing-based domain name resolution method described in the above embodiment.

[0230] It should be understood that the "plurality" 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; "and / or" in this article 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 at the same time, and B exists alone. In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different.

[0231] 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 used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, the embodiments of this application involve obtaining relevant information on multiple domain name suffixes based on domain names within a DNS zone, all of which are obtained with full authorization.

[0232] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the 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 other AZs except the first AZ in the corresponding DNS server group.

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