Multi-tenant shared domain name system and its use method, device and storage medium
By deploying distributed DNS servers and computing power gateways in the private network, using SRv6 technology and computing network brain to realize IPv4/IPv6 address conversion and virtual domain name generation, the domain name conflict problem in multi-tenant environment is solved, and the efficiency of DNS resolution is improved. Response speed and optimize the parsing process through storage partition SID.
Patent Information
- Application Number
- CN202211375791.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-04
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-11-04
AI Technical Summary
DNS systems in existing private network environments face domain name conflict problems, especially in multi-tenant sharing environments, the same domain name may correspond to different IPs or different IPs of the same network, resulting in invalid resolution and registration.
Using multi-tenant shared domain name system, SRv6 technology is used to deploy distributed DNS servers and computing power gateways in the private network, and IPv4/IPv6 address conversion and virtual domain name generation are realized through computing network brain and SDN controller to ensure IPv6 addresses of different tenant networks The network segments are different, thereby avoiding domain name conflicts and optimizing the DNS resolution process through storage partition SID.
It effectively avoids domain name conflicts, improves DNS resolution efficiency and response speed, reduces the resolution workload of DNS servers, and ensures the stability of network transmission through SRv6 message compression technology.
Smart Images

Figure CN115941646B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of domain name systems, and in particular to a multi-tenant shared domain name system and a method, device and storage medium for using the same. Background Art
[0002] The Domain Name System (DNS) is a hierarchical, distributed naming system for resources connected to a network such as the Internet. The Domain Name System associates numeric IP addresses with domain names of network entities. A DNS name server is a server that stores DNS records for domain names, receives DNS requests, and responds to queries against its database with answers, while DNS servers typically cache DNS requests and responses that have been received from other DNS name servers. A caching name server (DNS cache) stores query results for a period of time determined by the associated time-to-live of a domain name record.
[0003] In a private network, domain names can be registered according to the needs of tenants. In this case, domain name conflicts within the private network will occur. For example, in the intranet of a group company, two subsidiaries register the caiwu.com domain name for internal financial data processing. Then the shared DNS server has two identical domain names to be recorded in the intranet. These two domain names correspond to different IP addresses or the same IP address in different networks. Existing solutions include using restricted namespaces for different tenant virtual networks, forcing the reservation of some specific DNS suffixes, such as name_1.caiwu.com, to distinguish domain names. Another solution is to deploy a virtual machine (VM) as a DNS server for each tenant (virtual network) in its network, where it manages and hosts the required domains. Tenant virtual machines point to this DNS server for name resolution. This DNS server can serve as both an authoritative server and a forwarder / recursive resolver for external queries. However, this solution is not the best solution because it requires each tenant to have a dedicated VM for DNS and places management overhead on the client. At the same time, this solution does not provide fault tolerance. For example, if the VM crashes, the DNS resolution and registration of the tenant network will fail. Summary of the invention
[0004] The main purpose of this application is to provide a multi-tenant shared domain name system and its use method, device and storage medium, aiming to solve the domain name conflict problem faced by the DNS system in the existing private network environment.
[0005] To achieve the above-mentioned purpose, in the first aspect, a multi-tenant shared domain name system is provided, including multiple tenant networks, a private network, an SDN controller, a computing network brain, a distributedly deployed DNS server and at least one computing power gateway, wherein the computing power gateway and the DNS server are both deployed in the private network, and the private network is established based on the SRv6 technology, each of the computing power gateways corresponds to one or more tenant networks, and the tenant networks access the private network through the corresponding computing power gateways, each of the DNS servers is connected to the computing network brain signal, and the computing network brain is used to control the connected DNS server, and each of the computing power gateways is connected to the SDN controller signal, and the SDN controller is used to control the connected computing power gateway;
[0006] The DNS server includes a storage module and a cache module, wherein the cache module is used to cache domain name records resolved within a preset time, the storage module is provided with a plurality of storage partitions, each of which is provided with a unique corresponding IPv6 address network segment, the correspondence between the storage partition and the IPv6 address network segment is configured by the computing network brain and sent to the DNS server, the storage partition is used to store the domain name record corresponding to the corresponding IPv6 address network segment, the domain name record is used to record the correspondence between the domain name, IPv4 address, IPv6 address and virtual domain name of the user device in the tenant network, wherein the IPv6 address of the user device is obtained by the corresponding computing power gateway according to the tenant network where the user device is located and the IPv4 address of the user device, and the virtual domain name is generated according to the IPv6 address and domain name of the user device; the DNS server provides domain name resolution and domain name registration services based on the domain name record in the storage partition; the DNS server publishes the corresponding service status information in the private network and spreads it based on the preset routing protocol, the service status information includes the server SID, the server IP address and the storage partition SID, wherein the storage partition SID is uniformly configured by the computing network brain and sent to the DNS server;
[0007] Each of the tenant networks is configured with a unique corresponding IPv6 address segment. The correspondence between the tenant network and the IPv6 address segment is configured and stored by the computing network brain. The computing network brain transmits the correspondence between the tenant network and the IPv6 address segment to the SDN controller. The SDN controller sends the correspondence between the tenant network and the IPv6 address segment to the computing power gateway. The computing power gateway provides IPV4 / IPv6 address conversion services for user devices in the tenant network based on the correspondence between the tenant network and the IPv6 address segment and forms address conversion records. The address conversion records are partitioned and saved based on different tenant networks. The computing power gateway is configured with a DNS server virtual address. The DNS server virtual address is configured in the computing power gateway by the tenant network administrator. The DNS server virtual address forms a first mapping relationship with all server SIDs. The first mapping relationship is stored and maintained by the computing power gateway.
[0008] In a second aspect, a domain name registration method for a multi-tenant shared domain name system is provided, which is applicable to the multi-tenant shared domain name system described in the first aspect, and the method comprises:
[0009] A first user device in a first tenant network sends a DNS registration request; wherein a source address of the DNS registration request is an IPv4 address of the first user device, a destination address is a virtual address of a DNS server, and the DNS registration request includes a first domain name and an IPv4 address of the first user device;
[0010] The first computing power gateway obtains the DNS registration request and determines the first server SID according to the first mapping relationship and the routing protocol, and then obtains the first IPv6 address according to the first server SID, and performs IPV4 / IPv6 address conversion for the source address of the DNS registration request to obtain a second IPv6 address; wherein the first IPv6 address is the IP address of the DNS server corresponding to the first server SID, and the second IPv6 address is the IPv6 address of the first user device;
[0011] The first computing power gateway packages and generates DNS registration request data and sends it, where the source address of the DNS registration request data is the IP address of the first computing power gateway, the destination address is the first IPv6 address, and the DNS registration request data includes the first domain name, the IPv4 address of the first user device, and the second IPv6 address;
[0012] The DNS server corresponding to the first server SID receives and parses the DNS registration request data, determines the corresponding first tenant identifier according to the second IPv6 address, determines the storage partition according to the first tenant identifier, generates a first virtual domain name based on the first domain name and the first tenant identifier, and then generates a corresponding domain name record based on the first domain name, the IPv4 address of the first user device, the second IPv6 address and the first virtual domain name, stores it in the determined storage partition, and returns the DNS registration result to the first computing power gateway;
[0013] The first computing power gateway receives the DNS registration result returned by the DNS server corresponding to the first server SID, and returns the DNS registration result to the IPv4 address of the first user equipment;
[0014] The DNS server corresponding to the first server SID synchronizes its domain name record with other DNS servers.
[0015] In a third aspect, a domain name resolution method for a multi-tenant shared domain name system is provided, the method comprising:
[0016] The second user equipment in the second tenant network sends a DNS resolution request; wherein the source address of the DNS resolution request is the IPv4 address of the second user equipment, the destination address is the DNS server virtual address, and the DNS resolution request includes a second domain name, which is the domain name to be resolved;
[0017] The second computing power gateway obtains the DNS resolution request and determines the second server SID according to the first mapping relationship and the routing protocol, and then obtains the third IPv6 address according to the second server SID, and performs IPV4 / IPv6 address conversion for the source address of the DNS resolution request to obtain a fourth IPv6 address, and queries the storage partition SID in the service status information according to the fourth IPv6 address to obtain the first storage partition SID; wherein the third IPv6 address is the IP address of the DNS server corresponding to the second server SID, the fourth IPv6 address is the IPv6 address of the second user device, and the first storage partition SID is the SID of the storage partition corresponding to the IPv6 address network segment where the fourth IPv6 address is located;
[0018] The second computing power gateway packages and generates DNS resolution request data and sends it, wherein the source address of the DNS resolution request data is the IP address of the second computing power gateway, the destination address is the third IPv6 address, and the DNS resolution request data includes the second domain name, the fourth IPv6 address, and the first storage partition SID;
[0019] The DNS server corresponding to the second server SID receives the DNS resolution request data, and determines the corresponding storage partition according to the first storage partition SID, and determines the corresponding second tenant identifier according to the fourth IPv6 address, obtains the second virtual domain name according to the second domain name and the second tenant identifier, and determines whether the domain name record corresponding to the second virtual domain name exists in the corresponding cache. If so, obtains the third user device IPv4 address according to the domain name record corresponding to the second virtual domain name in the cache, generates a DNS resolution result based on the third user device IPv4 address, and returns it to the second computing power gateway; otherwise, traverses the storage partition corresponding to the first storage partition SID based on the second virtual domain name to query the corresponding domain name record to obtain the third user device IPv4 address, generates a DNS resolution result based on the third user device IPv4 address, and returns it to the second computing power gateway;
[0020] The second computing power gateway receives the DNS resolution result and forwards it to the second user device.
[0021] The embodiment of the present application also provides a computer device, including one or more processors;
[0022] a memory for storing one or more programs,
[0023] When the one or more programs are executed by the one or more processors, the one or more processors execute the methods described in the second and third aspects above.
[0024] An embodiment of the present application further provides a storage medium storing a computer program, which, when executed by a processor, implements the methods described in the second and third aspects above.
[0025] The beneficial effect of the present invention is that the domain name record of the IP-domain name in the prior art is replaced by a domain name record constructed by a domain name, an IPv4 address of a user device corresponding to the domain name in a tenant network, an IPv6 address converted from an IPv4 address, and a virtual domain name generated based on the converted IPv6 address and the domain name, so that even if the domain name and the same internal network IPv4 address are from different tenant networks, different domain name records can be formed, thereby ensuring that a multi-tenant shared DNS system for a private network can avoid domain name conflicts, because the domain name record in the private network needs to be generated based on an IPv6 address converted from an IPv4 address and a virtual domain name generated based on the converted IPv6 address and the domain name, and the IPv6 address network segments corresponding to different tenant networks are different, thereby ensuring that the converted IPv6 addresses of user devices from different tenant networks cannot conflict, and therefore the generated domain name records will not conflict; further ,This application creatively adopts storage partition SID, so that when the DNS server publishes service status information to the private network, it also spreads the partition storage status of the domain name record in the server to the private network, so that when resolving the domain name, the computing power gateway can obtain the storage partition status of the domain name to be resolved, and there is no need to perform partition query on the server side, that is, the DNS server, which greatly alleviates the resolution workload of the DNS server, improves the domain name resolution response speed of the private network, and improves the resolution efficiency; the use of storage partition SID actually performs the partition retrieval work of the domain name to be resolved at the network layer, and in the SRv6 network, SID is usually in the form of a 128-bit IPv6 address. The implementation of storage partition SID requires a large number of SIDs to be published, which may be segmented due to the SRv6 message length limit. Therefore, this application also provides an SRv6 message compression idea to support the publication of storage partition SID, thereby ensuring that the efficiency of private network domain name resolution is improved while not affecting network transmission. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 is a schematic diagram of a multi-tenant shared domain name system provided by an embodiment of the present invention;
[0027] Figure 2 A flowchart of a domain name registration method provided by an embodiment of the present invention;
[0028] Figure 3 A data flow diagram of a domain name registration method provided by an embodiment of the present invention;
[0029] Figure 4 A schematic diagram of a domain name resolution method flow chart provided by an embodiment of the present invention;
[0030] Figure 5 A schematic diagram of the overall architecture of a multi-tenant shared domain name system provided by an embodiment of the present invention;
[0031] Figure 6 A schematic diagram of the structure of a device provided in one embodiment of the present invention.
[0032] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0033] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.
[0034] The following embodiments relate to a multi-tenant shared domain name system for a private network and its corresponding domain name registration and domain name resolution method. A cloud service provider is a company that provides cloud computing components such as Infrastructure as a Service (IaaS), Software as a Service (SaaS) or Platform as a Service (PaaS) to other businesses or individuals. With the development of cloud computing technology, the services of cloud service providers have become more refined, and there are more and more products for private networks. For example, enterprise intranets can also be implemented through cloud computing services, further reducing the cost of enterprises. With the development of private network services, unless it is a relatively large enterprise, it is less and less common to build an independent private network for a single customer. More and more private networks shared by a limited number of tenants are used to provide enterprises with high-quality private network services. At this time, the problem of domain name conflicts may occur in the private network. This is mainly because cloud service providers usually need to support the addressing and naming attributes of tenants' private networks to remain unchanged. For private network domain names, many tenants will use some frequently used domain names, such as caiwu.com, luntan.com, etc. at the beginning of the original setting. When multiple tenants access the private network, they will bring their original domain names, which makes it very easy for domain name conflicts to occur in the private network. The embodiments involve a multi-tenant shared domain name system for a private network and its corresponding domain name registration and domain name resolution method, which can solve the problem of providing name resolution services for virtual networks in which customers can introduce their own domain names.
[0035] like Figure 1 As shown, Figure 1 It is a structural diagram of a multi-tenant shared domain name system involved in an embodiment of the present invention. As an embodiment of the present application, a multi-tenant shared domain name system is provided, including multiple tenant networks, a private network, an SDN controller, a computing network brain, a distributedly deployed DNS server and at least one computing power gateway, the computing power gateway and the DNS server are both deployed in the private network, the private network is established based on SRv6 technology, each of the computing power gateways corresponds to one or more tenant networks, the tenant networks access the private network through the corresponding computing power gateways, each of the DNS servers is connected to the computing network brain signal, the computing network brain is used to control the connected DNS server, each of the computing power gateways is connected to the SDN controller signal, the SDN controller is used to control the connected computing power gateway;
[0036] The DNS server includes a storage module and a cache module, wherein the cache module is used to cache domain name records resolved within a preset time, the storage module is provided with a plurality of storage partitions, each of which is provided with a unique corresponding IPv6 address network segment, the correspondence between the storage partition and the IPv6 address network segment is configured by the computing network brain and sent to the DNS server, the storage partition is used to store the domain name record corresponding to the corresponding IPv6 address network segment, the domain name record is used to record the correspondence between the domain name, IPv4 address, IPv6 address and virtual domain name of the user device in the tenant network, wherein the IPv6 address of the user device is obtained by the corresponding computing power gateway according to the tenant network where the user device is located and the IPv4 address of the user device, and the virtual domain name is generated according to the IPv6 address and domain name of the user device; the DNS server provides domain name resolution and domain name registration services based on the domain name record in the storage partition; the DNS server publishes the corresponding service status information in the private network and spreads it based on the preset routing protocol, the service status information includes the server SID, the server IP address and the storage partition SID, wherein the storage partition SID is uniformly configured by the computing network brain and sent to the DNS server;
[0037] Each of the tenant networks is configured with a unique corresponding IPv6 address segment. The correspondence between the tenant network and the IPv6 address segment is configured and stored by the computing network brain. The computing network brain transmits the correspondence between the tenant network and the IPv6 address segment to the SDN controller. The SDN controller sends the correspondence between the tenant network and the IPv6 address segment to the computing power gateway. The computing power gateway provides IPV4 / IPv6 address conversion services for user devices in the tenant network based on the correspondence between the tenant network and the IPv6 address segment and forms address conversion records. The address conversion records are partitioned and saved based on different tenant networks. The computing power gateway is configured with a DNS server virtual address. The DNS server virtual address is configured in the computing power gateway by the tenant network administrator. The DNS server virtual address forms a first mapping relationship with all server SIDs. The first mapping relationship is stored and maintained by the computing power gateway.
[0038] In the above scheme, the domain name record adopted by the multi-tenant shared domain name system does not simply adopt the IP-domain name record method, but converts the real IPv4 address of the user device in the tenant network into an IPv6 address, and then generates a virtual domain name based on the domain name, IPv6 address and domain name, generates a domain name record with the IPv4 address, IPv6 address, domain name and virtual domain name, and then sets the corresponding address conversion protocol so that different tenant networks correspond to different IPv6 address segments to isolate different tenants and ensure that user devices from different tenant networks have different IPv6 addresses after address conversion. The virtual domain name is generated based on the real domain name and the tenant network identifier. Although there may be conflicts in the real domain name, due to different tenant networks, the tenant network identifiers are also different, so the generated virtual domain name must be different. During resolution, the corresponding tenant network can be determined according to the network segment where the user's IPv6 address in the request is located, and then a virtual domain name is generated based on the tenant network identifier and the real domain name. DNS resolution is performed with the virtual domain name to obtain a uniquely determined domain name record, and then the real IPv4 address corresponding to the domain name is obtained to send the resolution result back to the computing power gateway, and the computing power gateway forwards the resolution result to the corresponding user device.
[0039] On the other hand, the private network is built based on SRv6 technology. The DNS server can publish service status information in the private network and spread it through the routing protocol. The service status information includes server SID, server IP and storage partition SID. The corresponding server IP can be obtained through the server SID. By spreading the storage partition SID, the storage area of the domain name to be resolved in the DNS server can be determined at the network layer, avoiding traversal queries in the DNS server, thereby improving the resolution efficiency of the DNS server. The implementation of the storage partition SID requires a large number of SIDs to be published, which may be segmented due to the length limit of the SRv6 message. Therefore, this application also provides a SRv6 message compression idea. The principle is that the storage partition SID is configured by the computing network brain, and usually has a common prefix for the convenience of configuration. The common prefix part of the SID in a SID List in the SRv6 message header is repeated and redundant. Therefore, the Common Prefix part and other redundant parts in the SRv6 SID are removed from the SID list, and the Node ID and Function ID are retained as compressed SIDs. Specifically, it is agreed that the SID list in the SRv6 message header includes several SID Containers, the length of the SID Container is set to 128 bits, the SID Container is used to store a SID of standard length or 1-4 compressed SIDs, the length of the compressed SID is set to 32 bits, the compressed SID is the Node ID and Function ID part of its standard SID, and the SID Container with less than four compressed SIDs is padded with 0. The SID list includes at least one standard SID, at least one of which is marked with the Common Prefix part, the compressed SID in the SID Container is provided with a compression flag, and the compressed SID at the end of the SID list is not provided with a compression flag; configure the SID index, and place the SID index in the lowest bit of the Arguments after the compressed SID in the destination address, and the SID index is 2 bits; the SID index is used to specify the compressed SID in the SID The location in the Container. Since the SIDContainer is used to store a standard length SID or 1-4 compressed SIDs, a maximum of four compressed SIDs can be stored in a SID Container. Therefore, the value range of the SID index is 0-3, so a maximum of 2 bits are required. Through the above compression idea, the server can compress the server SID and storage partition SID when publishing, reducing the size of the SRv6 message header occupied by the SID, especially the storage partition SID, and avoiding fragmentation.
[0040] like Figure 2 and Figure 3 As shown, as another embodiment of the present application, a domain name registration method for a multi-tenant shared domain name system is provided, which is applicable to the above multi-tenant shared domain name system, and the method includes:
[0041] A first user device in a first tenant network sends a DNS registration request; wherein a source address of the DNS registration request is an IPv4 address of the first user device, a destination address is a virtual address of a DNS server, and the DNS registration request includes a first domain name and an IPv4 address of the first user device;
[0042] The first computing power gateway obtains the DNS registration request and determines the first server SID according to the first mapping relationship and the routing protocol, and then obtains the first IPv6 address according to the first server SID, and performs IPV4 / IPv6 address conversion for the source address of the DNS registration request to obtain a second IPv6 address; wherein the first IPv6 address is the IP address of the DNS server corresponding to the first server SID, and the second IPv6 address is the IPv6 address of the first user device;
[0043] The first computing power gateway packages and generates DNS registration request data and sends it; the source address of the DNS registration request data is the IP address of the first computing power gateway, the destination address is the first IPv6 address, and the DNS registration request data includes the first domain name, the IPv4 address of the first user device, and the second IPv6 address;
[0044] The DNS server corresponding to the first server SID receives and parses the DNS registration request data, determines the corresponding first tenant identifier according to the second IPv6 address, determines the storage partition according to the first tenant identifier, generates a first virtual domain name based on the first domain name and the first tenant identifier, and then generates a corresponding domain name record based on the first domain name, the IPv4 address of the first user device, the second IPv6 address and the first virtual domain name, stores it in the determined storage partition, and returns the DNS registration result to the first computing power gateway;
[0045] The first computing power gateway receives the DNS registration result returned by the DNS server corresponding to the first server SID, and returns the DNS registration result to the IPv4 address of the first user equipment;
[0046] The DNS server corresponding to the first server SID synchronizes its domain name record with other DNS servers.
[0047] like Figure 4 As shown, as another embodiment of the present application, a domain name resolution method for a multi-tenant shared domain name system is provided, the method comprising:
[0048] The second user equipment in the second tenant network sends a DNS resolution request; wherein the source address of the DNS resolution request is the IPv4 address of the second user equipment, the destination address is the DNS server virtual address, and the DNS resolution request includes the second domain name;
[0049] The second computing power gateway obtains the DNS resolution request and determines the second server SID according to the first mapping relationship and the routing protocol, and then obtains the third IPv6 address according to the second server SID, and performs IPV4 / IPv6 address conversion for the source address of the DNS resolution request to obtain a fourth IPv6 address, and queries the storage partition SID in the service status information according to the fourth IPv6 address to obtain the first storage partition SID; wherein the third IPv6 address is the IP address of the DNS server corresponding to the second server SID, the fourth IPv6 address is the IPv6 address of the second user device, and the first storage partition SID is the SID of the storage partition corresponding to the IPv6 address network segment where the fourth IPv6 address is located;
[0050] The second computing power gateway packages and generates DNS resolution request data and sends it, wherein the source address of the DNS resolution request data is the IP address of the second computing power gateway, the destination address is the third IPv6 address, and the DNS resolution request data includes the second domain name, the fourth IPv6 address, and the first storage partition SID;
[0051] The DNS server corresponding to the second server SID receives the DNS resolution request data, and determines the corresponding storage partition according to the first storage partition SID, and determines the corresponding second tenant identifier according to the fourth IPv6 address, obtains the second virtual domain name according to the second domain name and the second tenant identifier, and determines whether the domain name record corresponding to the second virtual domain name exists in the corresponding cache. If so, obtains the third user device IPv4 address according to the domain name record corresponding to the second virtual domain name in the cache, generates a DNS resolution result based on the third user device IPv4 address, and returns it to the second computing power gateway; otherwise, traverses the storage partition corresponding to the first storage partition SID based on the second virtual domain name to query the corresponding domain name record to obtain the third user device IPv4 address, generates a DNS resolution result based on the third user device IPv4 address, and returns it to the second computing power gateway;
[0052] The second computing power gateway receives the DNS resolution result and forwards it to the second user device.
[0053] The following cases are explained in detail. Figure 5For example, there are users A and B in tenant network A, and user C in tenant network B. The IPv4 addresses of users A and C in their respective networks are both 192.168.9.3, and the domain names are both ABC.com. The IPv4 address of user B is 192.168.9.4. Assume that the network segment corresponding to tenant network A is FF00::0001 to FF00::000F, and its resident ID is set to FA. The network segment corresponding to tenant network B is FF00::0011 to FF 00::001F, tenant network A is connected to computing gateway A, tenant network B is connected to computing gateway B, the DNS server virtual address set by the administrator of tenant network A in computing gateway A is 192.168.9.9, and the DNS server virtual address set by the administrator of tenant network B in computing gateway B is 192.168.9.9. DNS servers a, b, and c are deployed in the cloud private network, and they publish corresponding service status information respectively. The service status information package The service status information of DNS server a includes SID_a, IP_a and storage partition SID group, namely SID_x, SID_y and SID_z; the service status information of DNS server b includes SID_b, IP_b and storage partition SID group, namely SID_x, SID_y and SID_z; the service status information of DNS server c includes SID_c, IP_c and storage partition SID group, namely SID_x, SID_y and SID_z; the specific service status information publishing process of the server includes the server registering the service status information into the local state routing table of the connected computing network router; the computing network router loads the local state routing table into the message based on the routing protocol and spreads it to other computing network routers; the computing network router generates a service status information routing table based on the local state routing table and the service status information spread by other computing network routers; the computing power gateway obtains the required service status information content based on the service status information routing table;
[0054] When user A registers a domain name, user A first initiates a domain name registration request. The source address of the request is 192.168.9.3, and the destination address is 192.168.9.9. Computing gateway A obtains the domain name registration request. Computing gateway A determines the corresponding IPv6 address segment based on the tenant network A from which user A comes, and performs address conversion to obtain the corresponding IPv6 address FF00::0001, and records 192.168.9.3-FF00::0001 in the conversion record of computing gateway A. Computing gateway A finds the corresponding SID based on the first mapping relationship, where the first mapping relationship is 192.168.9.9-SID_a, SID_b, SID_c. Then computing gateway A determines a specific server SID based on the routing protocol. Assuming that the server SID determined according to the routing protocol is SID_a, the server IP is determined according to SID_a, that is, IP_a. Computing gateway A generates domain name registration request data, and the registration request The data includes user A's domain name ABC.com, user A's IPv4 address 192.168.9.3 and user A's converted IPv6 address FF00::0001; computing power gateway A sends registration request data to DNS server a, and DNS server a determines the storage partition based on user A's converted IPv6 address FF00::0001, assuming it is storage partition x and the tenant network identifier of tenant network A, assuming it is recorded as 010F, and then generates a virtual domain name - 010F_ABC.com based on the tenant network identifier of tenant network A and user A's domain name, and then forms a corresponding domain name record based on user A's domain name, IPv4 address, IPv6 address and virtual domain name, namely ABC.com-192.168.9.3-FF00::0001-010F_ABC.com, and then records the domain name into the storage partition x of DNS server a, and then synchronizes the domain name record to DNS server b and DNS server c.Similarly, user C can also register a domain name, and the resulting domain name record is ABC.com—192.168.9.3—FF00::0011—111F_ABC.com (assuming that the converted IPv6 address of user C is FF00::0011). Due to the form of domain name record adopted by this application, user C and user A will not conflict. When user B accesses the domain name ABC.com, user B first generates a domain name resolution request, the source address of the request is 192.168.9.4, and the destination address is 192.168.9.9. Computing gateway A obtains the domain name resolution request. Computing gateway A determines the corresponding IPv6 address segment based on the tenant network A from which user A comes and performs address conversion to obtain the corresponding IPv6 address FF00::0002, and records 192.168.9.4-FF00::0002 in the conversion record of computing gateway A. Computing gateway A finds the corresponding DNS server SID based on the first mapping relationship, assuming it is SID_a, and then queries the service status routing table based on the converted IPv6 address FF00::0002 and SID_a to find the DNS server. The IP address IP_a of the computing gateway a and the corresponding storage partition SID—SID_x, then the computing gateway A generates a domain name resolution request data. The source address of the domain name resolution request data is the IP address of the computing gateway A, and the destination address is IP_a. The resolution request data includes the domain name to be resolved ABC.com, the SID of the storage partition, namely SID_x, and the IPv6 address of user B after conversion—FF00::0002. After receiving the domain name resolution request data, DNS server a determines the tenant network identifier 010F according to the IPv6 address of user B, and then determines the tenant network identifier 010F according to the network segment identifier The virtual domain name 010F_ABC.com is generated by the domain name ABC.com, and then the cache module is queried according to 010F_ABC.com to find the domain name record, and the IP address 192.168.9.3 is queried and returned to the computing power gateway A, which then returns the address to user B; if the corresponding domain name record is not found in the cache module, the storage partition is found according to SID_x, and then the corresponding IP address 192.168.9.3 is found according to ABC.com and returned to the computing power gateway A, which then returns the address to user B.
[0055] In the above domain name registration process, even if user A and user C have the same IPv4 address and domain name in their respective tenant networks, they still have different domain names in the private network's DNS servers a, b, and c. This is mainly due to the fact that the domain name records used by the private network's DNS server are in the form of domain name, IPv4 address, IPv6 address, and virtual domain name (for example, the domain name record corresponding to user A is ABC.com—192.168.9.3—FF00::0001—010F_ABC.com), so that domain name records from different tenant networks must have different virtual domain names, and the same tenant network retains the domain name conflict rules, so that when users in the tenant network need domain name resolution services, the DNS server The virtual domain name can be calculated according to the information in the request data, and then the corresponding domain name record can be directly found in the cache module for resolution based on the virtual domain name. Or, when the relevant record cannot be found in the cache module, the specific partition where the relevant domain name record is stored can be accurately located through the storage partition SID, and the storage partition can be traversed to obtain the domain name record. The introduction of the storage partition SID can determine the storage partition where the domain name record of the domain name to be resolved is located when the resolution request data is generated. This process is completed at the network level without confirmation in the DNS server, which greatly reduces the resolution workload of the DNS server, improves the response speed of the DNS resolution service, improves the efficiency of the DNS server, and optimizes the private network experience of tenant network users.
[0056] Figure 6 A schematic diagram of the structure of a device provided by an embodiment of the present invention. Figure 6 As shown, as another aspect, the present application also provides a computer device 100, including one or more central processing units (CPU) 101, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 102 or the program loaded from the storage part 108 to the random access memory (RAM) 103. In the RAM 103, various programs and data required for the operation of the device 100 are also stored. The CPU 101, the ROM 102, and the RAM 103 are connected to each other through a bus 104. An input / output (I / O) interface 105 is also connected to the bus 104.
[0057] The following components are connected to the I / O interface 105: an input section 106 including a keyboard, a mouse, etc.; an output section 107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 108 including a hard disk, etc.; and a communication section 109 including a network interface card such as a LAN card, a modem, etc. The communication section 109 performs communication processing via a network such as the Internet. A driver 110 is also connected to the I / O interface 105 as needed. A removable medium 111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the driver 110 as needed, so that a computer program read therefrom is installed into the storage section 108 as needed.
[0058] In particular, according to the embodiments disclosed in the present application, the method described in the above embodiment 1 can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program tangibly contained on a machine-readable medium, and the computer program includes a program code for executing the method described in any of the above embodiments. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 109, and / or installed from the removable medium 111.
[0059] As another aspect, the present application further provides a computer-readable storage medium, which may be a computer-readable storage medium included in the apparatus of the above embodiment; or a computer-readable storage medium that exists independently and is not assembled into the device. The computer-readable storage medium stores one or more programs, which are used by one or more processors to execute the method described in the present application.
[0060] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a dedicated hardware-based system that performs a specified function or operation, or can be realized by a combination of dedicated hardware and computer instructions.
[0061] The units or modules involved in the embodiments described in the present application may be implemented by software or by hardware. The units or modules described may also be arranged in a processor. For example, each of the units may be a software program arranged in a computer or a mobile smart device, or may be a separately configured hardware device. The names of these units or modules do not, in some cases, constitute limitations on the units or modules themselves.
[0062] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the concept of the present application. For example, the above features are replaced with the technical features with similar functions disclosed in the present application (but not limited to) to form a technical solution.
Claims
1. A multi-tenant shared domain name system, characterized in that: It includes multiple tenant networks, private networks, SDN controllers, a computing network brain, distributedly deployed DNS servers and at least one computing power gateway. The computing power gateway and DNS server are deployed in the private network. The private network is established based on SRv6 technology. Each computing power gateway corresponds to one or more tenant networks. The tenant networks access the private network through corresponding computing power gateways. Each DNS server is connected to the computing network brain signal. The computing network brain is used to control the connected DNS server. Each computing power gateway is connected to the SDN controller signal. The SDN controller is used to control the connected computing power gateway. The DNS server includes a storage module and a cache module, wherein the cache module is used to cache domain name records resolved within a preset time, the storage module is provided with a plurality of storage partitions, each of which is provided with a unique corresponding IPv6 address network segment, the correspondence between the storage partition and the IPv6 address network segment is configured by the computing network brain and sent to the DNS server, the storage partition is used to store the domain name record corresponding to the corresponding IPv6 address network segment, the domain name record is used to record the correspondence between the domain name, IPv4 address, IPv6 address and virtual domain name of the user device in the tenant network, wherein the IPv6 address of the user device is obtained by the corresponding computing power gateway according to the tenant network where the user device is located and the IPv4 address of the user device, and the virtual domain name is generated according to the IPv6 address and domain name of the user device; the DNS server provides domain name resolution and domain name registration services based on the domain name record in the storage partition; the DNS server publishes the corresponding service status information in the private network and spreads it based on the preset routing protocol, the service status information includes the server SID, the server IP address and the storage partition SID, wherein the storage partition SID is uniformly configured by the computing network brain and sent to the DNS server; Each of the tenant networks is configured with a unique corresponding IPv6 address segment. The correspondence between the tenant network and the IPv6 address segment is configured and stored by the computing network brain. The computing network brain transmits the correspondence between the tenant network and the IPv6 address segment to the SDN controller. The SDN controller sends the correspondence between the tenant network and the IPv6 address segment to the computing power gateway. The computing power gateway provides IPV4 / IPv6 address conversion services for user devices in the tenant network based on the correspondence between the tenant network and the IPv6 address segment and forms address conversion records. The address conversion records are partitioned and saved based on different tenant networks. The computing power gateway is configured with a DNS server virtual address. The DNS server virtual address is configured in the computing power gateway by the tenant network administrator. The DNS server virtual address forms a first mapping relationship with all server SIDs. The first mapping relationship is stored and maintained by the computing power gateway.
2. A multi-tenant shared domain name system according to claim 1, characterized in that: The SRv6 SID in the private network is in the form of a compressed SID, and the SID compression method includes: In the SID list of the SRv6 message, remove the Common Prefix part and other redundant parts in the SRv6 SID, and keep the Node ID and Function ID as the compressed SID.
3. A domain name registration method for a multi-tenant shared domain name system, applicable to the multi-tenant shared domain name system of claim 1, characterized in that: The method comprises: A first user device in a first tenant network sends a DNS registration request; wherein a source address of the DNS registration request is an IPv4 address of the first user device, a destination address is a virtual address of a DNS server, and the DNS registration request includes a first domain name and an IPv4 address of the first user device; The first computing power gateway obtains the DNS registration request and determines the first server SID according to the first mapping relationship and the routing protocol, and then obtains the first IPv6 address according to the first server SID, and performs IPV4 / IPv6 address conversion for the source address of the DNS registration request to obtain a second IPv6 address; wherein the first IPv6 address is the IP address of the DNS server corresponding to the first server SID, and the second IPv6 address is the IPv6 address of the first user device; The first computing power gateway packages and generates DNS registration request data and sends it, where the source address of the DNS registration request data is the IP address of the first computing power gateway, the destination address is the first IPv6 address, and the DNS registration request data includes the first domain name, the IPv4 address of the first user device, and the second IPv6 address; The DNS server corresponding to the first server SID receives and parses the DNS registration request data, determines the corresponding first tenant identifier according to the second IPv6 address, determines the storage partition according to the first tenant identifier, generates a first virtual domain name based on the first domain name and the first tenant identifier, and then generates a corresponding domain name record based on the first domain name, the IPv4 address of the first user device, the second IPv6 address and the first virtual domain name, stores it in the determined storage partition, and returns the DNS registration result to the first computing power gateway; The first computing power gateway receives the DNS registration result returned by the DNS server corresponding to the first server SID, and returns the DNS registration result to the IPv4 address of the first user equipment; The DNS server corresponding to the first server SID synchronizes its domain name record with other DNS servers.
4. A domain name resolution method for a multi-tenant shared domain name system, applicable to the multi-tenant shared domain name system of claim 1, characterized in that: The method comprises: The second user equipment in the second tenant network sends a DNS resolution request; wherein the source address of the DNS resolution request is the IPv4 address of the second user equipment, the destination address is the DNS server virtual address, and the DNS resolution request includes a second domain name, which is the domain name to be resolved; The second computing power gateway obtains the DNS resolution request and determines the second server SID according to the first mapping relationship and the routing protocol, and then obtains the third IPv6 address according to the second server SID, and performs IPV4 / IPv6 address conversion for the source address of the DNS resolution request to obtain a fourth IPv6 address, and queries the storage partition SID in the service status information according to the fourth IPv6 address to obtain the first storage partition SID; wherein the third IPv6 address is the IP address of the DNS server corresponding to the second server SID, the fourth IPv6 address is the IPv6 address of the second user device, and the first storage partition SID is the SID of the storage partition corresponding to the IPv6 address network segment where the fourth IPv6 address is located; The second computing power gateway packages and generates DNS resolution request data and sends it, wherein the source address of the DNS resolution request data is the IP address of the second computing power gateway, the destination address is the third IPv6 address, and the DNS resolution request data includes the second domain name, the fourth IPv6 address, and the first storage partition SID; The DNS server corresponding to the second server SID receives the DNS resolution request data, and determines the corresponding storage partition according to the first storage partition SID, and determines the corresponding second tenant identifier according to the fourth IPv6 address, obtains the second virtual domain name according to the second domain name and the second tenant identifier, and determines whether the domain name record corresponding to the second virtual domain name exists in the corresponding cache. If so, obtains the third user device IPv4 address according to the domain name record corresponding to the second virtual domain name in the cache, generates a DNS resolution result based on the third user device IPv4 address, and returns it to the second computing power gateway; otherwise, traverses the storage partition corresponding to the first storage partition SID based on the second virtual domain name to query the corresponding domain name record to obtain the third user device IPv4 address, generates a DNS resolution result based on the third user device IPv4 address, and returns it to the second computing power gateway; The second computing power gateway receives the DNS resolution result and forwards it to the second user device.
5. A computer device, characterized in that: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the method according to claim 3 or 4.
6. A storage medium storing a computer program, characterized in that: When the program is executed by a processor, the method according to claim 3 or 4 is implemented.
