Address acquisition method and system, and computing device and storage medium

Abstract

The embodiments of the present disclosure relate to the technical field of the Internet. Provided are an address acquisition method and system, and a computing device and a storage medium. The address acquisition method is applied to a data acquisition node in a first area, and comprises: sending to a request processing node an initial address acquisition request for an address providing node, wherein the address providing node is located in a second area, and the request processing node is located in a first area; receiving a target address acquisition request sent by the request processing node, wherein the target address acquisition request is obtained by the request processing node by means of replacing, with a node address of the address providing node, an address to be replaced that is carried in the initial address acquisition request; using the node address carried in the target address acquisition request to send the target address acquisition request to the address providing node; and receiving a target service address sent by the address providing node. A target service address is acquired in a cross-region manner, thereby avoiding the problem of data security being relatively low when a DNS service is accessed via a public network.

Description

Address acquisition methods and systems, computing devices, and storage media

[0001] This disclosure claims priority to Chinese Patent Application No. 202410986169.2, filed with the China Patent Office on July 22, 2024, entitled “Address Acquisition Method and System, Computing Device, Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of Internet technology, and in particular to an address acquisition method; one or more embodiments of this disclosure also relate to an address acquisition system, another address acquisition method, a computing device, a computer-readable storage medium, and a computer program product. Background Technology

[0003] With the development of Internet technology, when a user node accesses a specific service, it often involves converting the domain name corresponding to the service into an address.

[0004] Existing technologies often use public networks to access DNS (Domain Name System) services to convert domain names into addresses. However, for user nodes on private networks, accessing DNS services through the public network can lead to lower data security. Therefore, improving data security during the address acquisition process has become an urgent technical problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of this disclosure provide an address acquisition method. One or more embodiments of this disclosure also relate to an address acquisition device, an address acquisition system, another address acquisition method, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies of low data security in existing technologies that access DNS services via the public internet.

[0006] According to a first aspect of the present disclosure, an address acquisition method is provided, applied to a data acquisition node in a first region, comprising:

[0007] An initial address retrieval request for an address providing node is sent to a request processing node, wherein the address providing node is located in the second region and the request processing node is located in the first region;

[0008] Receive the target address acquisition request sent by the request processing node, wherein the target address acquisition request is obtained by the request processing node by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node;

[0009] Using the node address carried in the target address retrieval request, the target address retrieval request is sent to the address providing node;

[0010] The address provider receives a target service address sent by the address provider node, wherein the target service address is determined by the address provider node based on the domain name information carried in the request for obtaining the target address.

[0011] According to a second aspect of the present disclosure, an address acquisition device is provided, applied to a data acquisition node in a first area, comprising:

[0012] The first request sending module is configured to send an initial address acquisition request for an address providing node to a request processing node, wherein the address providing node is located in a second region and the request processing node is located in the first region;

[0013] The request receiving module is configured to receive a target address acquisition request sent by the request processing node, wherein the target address acquisition request is obtained by the request processing node by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node;

[0014] The second request sending module is configured to obtain the node address carried in the request using the target address, and send the target address acquisition request to the address providing node;

[0015] The address acquisition module is configured to receive a target service address sent by the address providing node, wherein the target service address is determined by the address providing node based on the domain name information carried in the target address acquisition request.

[0016] According to a third aspect of the present disclosure, an address acquisition system is provided, the system comprising a data acquisition node in a first region, a request processing node in the first region, and an address providing node in a second region, wherein...

[0017] The data acquisition node is configured to send an initial address acquisition request for the address providing node to the request processing node, receive a target address acquisition request sent by the request processing node, use the node address carried in the target address acquisition request to send the target address acquisition request to the address providing node, and receive a target service address sent by the address providing node.

[0018] The request processing node is configured to receive the initial address acquisition request, determine the node address of the address providing node based on the domain name information carried in the initial address acquisition request, replace the address to be replaced carried in the initial address acquisition request with the node address, obtain the target address acquisition request, and send the target address acquisition request to the data acquisition node.

[0019] The address providing node is configured to receive the target service address, determine the corresponding target service address based on the domain name information carried in the initial address acquisition request, and send the target service address to the data acquisition node.

[0020] According to a fourth aspect of the present disclosure, an address acquisition method is provided, applied to a request processing node in a first region, comprising:

[0021] Receive an initial address acquisition request sent by a data acquisition node for an address providing node, wherein the address providing node is located in a second region and the request processing node is located in the first region;

[0022] Replace the address to be replaced carried in the initial address acquisition request with the node address of the address providing node to obtain the target address acquisition request;

[0023] The target address acquisition request is sent to the data acquisition node, so that the data acquisition node sends the target address acquisition request to the address providing node and receives the target service address sent by the address providing node, wherein the target service address is determined by the address providing node based on the domain name information carried in the target address acquisition request.

[0024] According to a fifth aspect of the present disclosure, a computing device is provided, comprising:

[0025] Memory and processor;

[0026] The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, they implement the steps of the above address acquisition method.

[0027] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided that stores a computer program / instructions that, when executed by a processor, implement the steps of the address acquisition method described above.

[0028] According to a seventh aspect of the present disclosure, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the address acquisition method described above.

[0029] This disclosure provides one or more embodiments of an address acquisition method for a data acquisition node. In the process of acquiring an address, an initial address acquisition request for an address providing node in a second region is sent to a request processing node in a first region. The request processing node uses the target address acquisition request obtained by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node, thereby realizing the request update for the initial address acquisition request. By using the request processing node to realize the request update operation, the problem of high cost and configuration of request update capability for the data acquisition node during the creation process is avoided.

[0030] After receiving a target address retrieval request, the data acquisition node uses the node address carried in the request to send the request to the address provider node via a relatively secure cross-regional data transmission link. The node then receives the target service address returned by the address provider node through the same data transmission link. This enables the acquisition of the target service address across regions, ensuring the security of data transmission and avoiding the data security issues that can occur when user nodes in a private network access DNS services through the public network. Attached Figure Description

[0031] Figure 1 is a schematic diagram illustrating the application of an address acquisition method provided in an embodiment of this disclosure;

[0032] Figure 2 is a flowchart of an address acquisition method provided in an embodiment of this disclosure;

[0033] Figure 3 is a flowchart of an address acquisition method provided in an embodiment of this disclosure;

[0034] Figure 4 is a schematic diagram of the structure of an address acquisition system provided in an embodiment of this disclosure;

[0035] Figure 5 is a flowchart of another address acquisition method provided in an embodiment of this disclosure;

[0036] Figure 6 is a schematic diagram of an address acquisition device provided in an embodiment of this disclosure;

[0037] Figure 7 is a structural block diagram of a computing device provided in an embodiment of this disclosure. Detailed Implementation

[0038] Numerous specific details are set forth in the following description to provide a full understanding of this disclosure. However, this disclosure can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this disclosure. Therefore, this disclosure is not limited to the specific implementations disclosed below.

[0039] The terminology used in one or more embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this disclosure. The singular forms “a,” “the,” and “the” as used in one or more embodiments of this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this disclosure refers to and includes any or all possible combinations of one or more associated listed items.

[0040] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this disclosure, and similarly, second may also be referred to as first. Depending on the context, the word “if” as used herein may be interpreted as “when”, “in response to a determination”, or “when…”.

[0041] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this disclosure are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0042] First, the terms and concepts involved in one or more embodiments of this disclosure will be explained.

[0043] DNS: Domain Name System, an internet service that acts as a distributed database that maps domain names to IP addresses, making it easier for people to access the internet.

[0044] PrivateLink: Private network connection, which can establish a secure and stable private connection between a Virtual Private Cloud (VPC) and services on the cloud, simplifying the network architecture, enabling private network access to services, and avoiding the potential security risks of accessing services through the public network.

[0045] PrivateZone is a private DNS service based on a Virtual Private Cloud (VPC) environment. This service allows you to map private domain names to IP addresses within one or more custom VPCs.

[0046] Resolver: The parser.

[0047] VPC: Virtual Private Cloud, is a dynamically configured pool of public cloud computing resources that requires the use of encryption protocols, tunneling protocols, and other security procedures to transfer data between private enterprises and cloud service providers.

[0048] CEN: This is a networking product designed for enterprise private networks.

[0049] VPC Peering refers to a VPC peering connection, a connection between two VPCs. VPC Peering allows two VPCs to communicate with each other using two private addresses.

[0050] ISV: Independent Software Vendor.

[0051] Weather: Weather service program.

[0052] ENI: Elastic Network Interface. ENI is a logical network component in VPC, representing a virtual network interface card. ENI is an elastic network interface that is bound to a cloud server within a private network. It can be freely migrated between multiple cloud servers. Multiple network interfaces can be bound to a cloud server to achieve a high-availability network, or multiple internal network IPs can be bound to an elastic network interface to achieve a single host with multiple IPs.

[0053] VSW: Virtual Switch.

[0054] Zone: This is a DNS concept. A Zone is usually represented by the suffix of an organization domain name or a service domain name.

[0055] Domain name: A domain name is a string formed by adding the Host (host machine) prefix to the Zone, such as www.aliyun.com.

[0056] DNS Server: A DNS server provides DNS resolution queries for domain names using protocols such as UDP (User Datagram Protocol), TCP (Transmission Control Protocol), and HTTP (Hypertext Transfer Protocol), returning the IP address or other record format corresponding to the domain name.

[0057] DNS Resolver: A DNS resolver is typically configured to forward domain name queries to specific DNS servers based on a specific domain suffix.

[0058] Internal network domain name resolution: Resolves the requested domain name through the internal network.

[0059] Internal network link: Compared to the public network link, the network communication link is achieved through network connectivity technology based on standard interconnection products CEN and VPC Peering between VPCs in the cloud.

[0060] With the development of internet technology, when user nodes access specific services, it often involves converting the domain name corresponding to the service into an address. This conversion is often done by accessing DNS services over the public internet. However, for user nodes on private networks, accessing DNS services through the public internet presents data security risks. For example, current DNS solutions in cloud networks are limited to a single user. To publish and implement DNS resolution for all users of cloud products, it's necessary to iterate through and update the private DNS configurations of all users, which is undoubtedly inefficient when dealing with a large number of users.

[0061] Based on this, this disclosure provides two solutions. The first solution is based on PrivateZone (user private DNS), which creates a Zone for each user. When the domain name resolution changes, it is necessary to iterate through all users to update the configuration. However, this solution has significant drawbacks. First, it is not a distributed management solution, and the resolution changes are complex, requiring iteration through each user's PrivateZone to make configuration changes.

[0062] The second option is to use public DNS domain name services: for example, using the company's internal IDNS, ADNS, or cloud DNS for domain name resolution; however, this option has significant drawbacks. First, using public domain names allows external users to resolve the domain name, which is not what the project expects. Second, using public domain names requires applying for a fixed domain, which then needs to be used by a service provider, which is not legally compliant and carries certain public opinion risks.

[0063] Based on this, this disclosure provides an address acquisition method. One or more embodiments of this disclosure also relate to an address acquisition device, an address acquisition system, a computing device, a computer-readable storage medium, and a computer program product. These will be described in detail in the following embodiments.

[0064] Referring to Figure 1, which illustrates an application diagram of an address acquisition method provided according to an embodiment of the present disclosure, as shown in Figure 1, the cloud server in the first region needs to send an access request carrying the domain name information and a preset IP address to the request processing node for resolution when accessing the target service based on the domain name information of the target service.

[0065] The request processing node determines the IP address of the DNS server based on the domain name information, and replaces the preset IP address carried in the access request with the IP address of the DNS server to obtain the DNS query request; finally, the DNS query request is returned to the cloud server.

[0066] The cloud server receives the DNS query request and, based on the IP address carried in the DNS query request, sends the DNS query request across regions to the DNS server in the second region.

[0067] Based on the domain name information carried in the DNS query request, the DNS server determines the IP address corresponding to the domain name information from the locally stored IP addresses, and sends the IP address of the target service to the cloud server along the same path, so that the cloud server can access the corresponding target service based on the IP address.

[0068] Referring to Figure 2, which shows a flowchart of an address acquisition method according to an embodiment of the present disclosure, the address acquisition method is applied to a data acquisition node in a first region and specifically includes the following steps.

[0069] Step 202: Send the initial address acquisition request for the address providing node to the request processing node, wherein the address providing node is located in the second region and the request processing node is located in the first region.

[0070] In this context, a region can be understood as a locality or a private network area, and different private network areas constitute a complete private network; the first region and the second region can be understood as two different regions, and cross-regional data transmission between the first region and the second region needs to be carried out through a data transmission network.

[0071] A data acquisition node can be understood as a node used to obtain the target service address; for example, the data acquisition node is a cloud server (ECS). An address providing node can be understood as a node used to provide the target service address; for example, the address providing node can be a DNS server, which is a top-level authoritative server. A request processing node can be understood as a node that processes the initial address acquisition request to obtain the target address acquisition request; for example, the request processing node can be a PrivateZone resolver. It should be noted that the nodes in one or more embodiments of this disclosure can be hardware devices such as servers or server clusters, or software devices such as virtual machines, cloud servers, software systems, and applications.

[0072] An initial address retrieval request can be understood as a request to obtain the target service address from the address providing node. This initial address retrieval request carries the address to be replaced and domain name information. For example, this initial address retrieval request can be understood as an access request initiated by an application in ECS, which carries weather.isv.a****est.com and the default DNS address.

[0073] The address to be replaced can be understood as the address that needs to be replaced. This address to be replaced can be the IP address that is configured by default during the creation or initialization process of each data acquisition node. For example, the address to be replaced can be the default DNS address.

[0074] Domain information can be understood as the domain name corresponding to the target service node. For example, this domain information could be weather.isv.a****est.com.

[0075] In one or more embodiments provided in this disclosure, in order to ensure data security, the data transmission between the address providing node and the request processing node in a region needs to be implemented through a first regional transmission network, and the specific implementation method is as follows.

[0076] The step of sending the initial address acquisition request for the address providing node to the request processing node includes:

[0077] According to the first area transmission network between the data acquisition node and the request processing node, the initial address acquisition request for the address providing node is sent to the request processing node;

[0078] The first regional transmission network is used for data transmission between the data acquisition node and the request processing node, and the first regional transmission network includes a data acquisition private network in which the data acquisition node is located; based on the first regional transmission network, secure and efficient data transmission between the data acquisition node and the request processing node can be achieved.

[0079] A data acquisition private network can be understood as the VPC where the data acquisition node is located, and this VPC can be a user's VPC.

[0080] Taking the application of the address acquisition method provided in this disclosure in a cloud-based multi-tenant domain name resolution scenario across all regions as an example, this address acquisition method is explained. Here, the private network for data acquisition can be a user VPC, the data acquisition node is an ECS, the ECS contains an application (APP), the request processing node is a PrivateZone resolver, and the address providing node is a DNS server.

[0081] Therefore, when ECS needs to obtain an address, it needs to send the address acquisition request to the PrivateZone resolver (hereinafter referred to as the resolver) through the user VPC according to the pre-configured address (such as 100.10*.2.136, 100.10*.2.138, etc.) for processing, thereby ensuring data security.

[0082] In one or more embodiments provided in this disclosure, the initial address acquisition request is sent when the user needs to make a service request for the target service node, and the specific implementation method is as follows.

[0083] Before sending the initial address retrieval request for the address providing node to the request processing node, the process further includes:

[0084] Upon receiving a service access request from a client, the domain name information carried in the service access request is determined, and an initial address acquisition request is generated based on the domain name information and the preset address to be replaced. The service access request is generated by the client based on the service access operation performed by the user on the service page.

[0085] The client can be understood as a hardware device such as a user terminal, server, or smart device, or as a software device such as an application or software system. The service page can be a page that provides a specific service to the user; this service page can be an application page, a webpage, etc. The specific service can be set according to the actual application scenario, such as a weather information service.

[0086] Continuing with the previous example, when a user needs to access a specific service, they can provide the ECS with the domain name information corresponding to that specific service through the service page in the application, thereby instructing the ECS to obtain the corresponding service based on that domain name information. Based on the user's request, the ECS uses the domain name information and locally pre-configured addresses (such as PrivateZone addresses like 100.10*.2.136 and 100.10*.2.138) to generate an initial address retrieval request, thereby satisfying the user's access needs for the specific service.

[0087] In one or more embodiments provided in this disclosure, sending the initial address acquisition request for the address providing node to the request processing node includes:

[0088] Based on the address to be replaced carried in the initial address acquisition request, the initial address acquisition request is sent to the request forwarding unit;

[0089] Using the request forwarding unit, the request processing node is determined based on the domain name information carried in the initial address acquisition request, and the initial address acquisition request is forwarded to the request processing node.

[0090] The request forwarding unit can be understood as a unit that forwards data acquisition requests sent by the data acquisition node to the initial address to the request processing node. Considering the high cost of configuring request update capabilities for the data acquisition node during its creation, the data transmission method provided in this disclosure provides a request processing node. To avoid reconfiguring the data acquisition node during the updating or replacement of the request processing node, the data transmission method provided in this disclosure provides a request forwarding unit that can forward the initial address acquisition request sent by the data acquisition node through the address to be replaced (default address) to the request processing node, thereby enabling flexible updating or replacement of the request processing node without affecting the data acquisition node. For example, this request forwarding unit can be a PrivateZone.

[0091] Specifically, the data acquisition node can obtain the address to be replaced carried in the request based on the initial address, and send the initial address acquisition request to the request forwarding unit through the transmission network;

[0092] Upon receiving an initial address retrieval request, the request forwarding unit obtains the domain name information carried in the request, determines the request processing node based on the domain name information, and forwards the initial address retrieval request to the request processing node through the transmission network. Based on this, the request forwarding unit forwards the initial address retrieval request sent by the data acquisition node through the address to be replaced (default address) to the request processing node, thereby facilitating flexible updating or replacement of the request processing node without affecting the data acquisition node.

[0093] It should be noted that the data transmission operations between the data acquisition node, the request forwarding unit, and the request processing node can be implemented through the first area transmission network.

[0094] Using the previous example, when an application on a user's VPC ECS initiates a request to access weather.isv.a****est.com, the access request is sent to PrivateZone (i.e., the private DNS service) through the pre-configured default DNS address (PrivateZone address: 100.10*.2.138 / 139).

[0095] PrivateZone analyzes the domain name in the access request, which has the domain name ending with alicomputenest.com. Therefore, it forwards the request to the PrivateZone resolver for access.

[0096] Step 204: Receive the target address acquisition request sent by the request processing node, wherein the target address acquisition request is obtained by the request processing node by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node.

[0097] The node address can be understood as the address that provides the node's address; for example, the node address can be the IP address of the node.

[0098] A target address retrieval request can be understood as a request to obtain the target service address, which can be understood as a domain name resolution request to a DNS server.

[0099] Using the previous example, when ECS needs to obtain the IP address corresponding to a domain name, it needs to send the request to PrivateZone (i.e., private DNS service) through the user VPC based on the pre-configured address (such as PrivateZone addresses like 100.10*.2.136 and 100.10*.2.138).

[0100] The private DNS service analyzes the domain name in the request, which has the suffix alicomputenest.com. Therefore, it forwards the request to the resolver for access.

[0101] After receiving the request, the resolver determines the IP address of the DNS server and the data transmission link configured for that DNS server from the locally stored IP address information.

[0102] The resolver replaces the address (PrivateZone address) in the request with the IP address of the DNS server to obtain the domain name resolution request for the DNS server. Furthermore, it performs outbound terminal resolution based on the data transmission link to determine the outbound terminal node (a type of virtual network device) and forwards the domain name resolution request for the DNS server to the configured target terminal node through the outbound terminal node.

[0103] Here, the target terminal node is the user VPC that has accessed the virtual internet, and the DNS server is configured with the address (11.2*.0.1).

[0104] After traffic enters the user's VPC, it is found that the target address request is 11.2*.0.1. According to the user's VPC's basic routing configuration, the traffic will be sent to the ECS within the VPC, and then forwarded through the ECS within the VPC.

[0105] In one or more embodiments provided in this disclosure, receiving the target address acquisition request sent by the request processing node includes:

[0106] The request processing node receives a request to obtain the target address sent by the first regional transmission network.

[0107] Specifically, the request processing node can send a target address acquisition request to the data processing node through the first regional transmission network; thus, the data processing node can receive the target address acquisition request sent by the request processing node through the first regional transmission network, thereby ensuring secure and efficient data transmission between the request processing node and the data acquisition node.

[0108] Using the previous example, after the request sent by the resolver enters the user's VPC, it finds that the target address request is 11.2*.0.1. According to the user's VPC's basic routing configuration, the traffic will be sent to the ECS within the VPC.

[0109] Step 206: Using the node address carried in the target address acquisition request, send the target address acquisition request to the address providing node.

[0110] In one or more embodiments provided in this disclosure, sending the target address acquisition request to the address providing node using the node address carried in the target address acquisition request includes: sending the target address acquisition request to the address providing node by cross-regional routing forwarding using the node address carried in the target address acquisition request.

[0111] In one or more embodiments provided in this disclosure, the step of sending the target address acquisition request to the address providing node using the node address carried in the target address acquisition request includes:

[0112] Determine the data transmission network between the first region and the second region;

[0113] The node address carried in the target address acquisition request is sent to the address providing node through the data transmission network.

[0114] The data transmission network is used to perform data transmission operations between the first region and the second region. The data transmission network includes a first region transmission private network, a second region transmission private network, and a cross-region transmission network. The data transmission operations are performed through the first region transmission private network, the second region transmission private network, and the cross-region transmission network.

[0115] The first area transmission private network can be understood as a VPC located in the first area, and the cross-region transmission network can be understood as a cross-region network connected through VPC Peering; the second area transmission private network can be understood as a VPC located in the second area.

[0116] Specifically, in the process of sending the target address acquisition request, the data acquisition node first needs to determine the data transmission network between the first region and the second region, wherein the data transmission network includes the private transmission network of the first region, the private transmission network of the second region, and the cross-regional transmission network;

[0117] Secondly, the data acquisition node uses the node address carried in the target address acquisition request to send the target address acquisition request to the first regional transmission private network through its own configured network interface (ENI). Upon receiving the target address acquisition request, the first regional transmission private network obtains the node address carried in the target address acquisition request, performs routing analysis on the node address, and determines that the target address acquisition request is a request that needs to be transmitted across regions. Therefore, it determines the second regional transmission private network corresponding to the node address. The routing analysis is implemented based on the switches or virtual switches in the first regional transmission private network.

[0118] Finally, the first regional transmission private network determines the cross-regional transmission network between itself and the second regional transmission private network, and transmits the target address acquisition request to the second regional transmission private network through the cross-regional transmission network; wherein, the cross-regional transmission network is a pre-established network that enables cross-regional transmission between the first regional transmission private network and the second regional transmission private network; for example, the cross-regional transmission network is a cross-regional network established through VPC Peering.

[0119] After receiving a target address retrieval request, the second area transmission private network determines the node address carried in the request and performs routing analysis on that node address to determine the private network corresponding to the node address. This private network can be the private network where the address providing node is located (referred to as the address providing node private network). For example, this private network is a DNS service VPC, and the DNS service is located in this VPC. The routing analysis is implemented based on the switches or virtual switches in the second area transmission private network.

[0120] After determining the address-providing node private network, the second-zone transmission private network forwards the target address acquisition request to the address-providing node private network, which in turn forwards the target address acquisition request to the address-providing node based on the node address.

[0121] Based on this, the above steps enable data acquisition nodes and address providing nodes to transmit data through a relatively secure cross-regional data transmission link, thus ensuring data security.

[0122] Continuing with the previous example, the user's VPC sends a DNS query request to the DNS server in the second zone via cross-zone transmission. The specific steps are as follows: After the DNS query request arrives at the ECS, it is routed through the system router and forwarded to the virtual internet network in the first zone (i.e., the first zone's private transmission network) via the virtual internet's network interface card.

[0123] The interconnected VPC in the first region, based on the destination address 11.2*.0.1, is found by the VSW to require cross-VPC access after routing analysis. Therefore, the DNS query request is sent to the interconnected VPC in the second region through the cross-regional network (i.e., cross-regional transport network) established by VPC Peering, thus realizing a DNS architecture available across all regions.

[0124] The interconnected VPC of the second zone, after being forwarded by the VSW, sends the DNS query request to the DNS service VPC where the DNS server is located, and the DNS service VPC then sends the DNS query request to the DNS server.

[0125] Step 208: Receive the target service address sent by the address providing node, wherein the target service address is determined by the address providing node based on the domain name information carried in the request for obtaining the target address.

[0126] In one or more embodiments provided in this disclosure, receiving the target service address sent by the address providing node includes:

[0127] Receive the target service address sent by the address providing node through the data transmission network.

[0128] Specifically, after receiving the target address retrieval request, the address providing node can first obtain the domain name information carried in the target address retrieval request, and then perform a parsing query on the domain name information to determine the target service address corresponding to the domain name information.

[0129] The process of resolving and querying the domain name information includes: determining the locally stored domain name mapping table, and then determining the target service address corresponding to the domain name information from the domain name mapping table; or

[0130] The process of resolving and querying the domain name information includes: performing information transformation processing on the domain name information, such as hash transformation, to obtain the target service address corresponding to the domain name information.

[0131] Secondly, the target service address is transmitted to the data acquisition node through the data transmission network. For the step of transmitting the target service address to the data acquisition node through the data transmission network, please refer to the above-described execution flow of sending the target address acquisition request to the address providing node through the data transmission network, which will not be described in detail here.

[0132] Using the previous example, after receiving a DNS query request, the DNS server performs a query and resolution configuration based on the domain name information carried in the DNS query request, and obtains the resolution address corresponding to the domain name information as 11.1*.0.1; after obtaining the IP address corresponding to the weather service, it returns to the user's VPC ECS application along the same path.

[0133] In the above embodiments, the data acquisition node uses the node address carried in the target address acquisition request to send the target address acquisition request to the address providing node through a relatively secure cross-regional data transmission link, and receives the target service address returned by the address providing node based on the same data transmission link, thereby realizing the acquisition of the target service address in a cross-regional manner and ensuring the security of data transmission.

[0134] In one or more embodiments provided in this disclosure, after receiving the target service address sent by the address providing node, the method further includes:

[0135] Based on the target service address, a data processing request is sent to the target service node, wherein the target service address is the address of the target service node;

[0136] Receive the data processing result determined by the target service node based on the data processing request.

[0137] The target service node can be understood as a node that provides the target service. The target service can perform data processing operations based on the data processing request and obtain the data processing result.

[0138] Using the previous example, the ECS application sends a weather information query request to the weather service in the ISV VPC via the IP address. This request is then sent to the interconnected VPC through the ECS's network interface (ENI).

[0139] Based on the destination address 11.1*.0.1, the VSW's routing analysis found that cross-VPC access was not required. Therefore, the weather information query request was sent to the weather server in the ISV VPC via routing forwarding.

[0140] Based on the weather information query request, the weather server returns the weather information to the user's VPC ECS application along the same path, thus enabling access to the target service node based on the user's request and meeting the user's actual needs.

[0141] This disclosure provides one or more embodiments of an address acquisition method for a data acquisition node. In the process of acquiring an address, an initial address acquisition request for an address providing node in a second region is sent to a request processing node in a first region. The request processing node uses the target address acquisition request obtained by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node, thereby realizing the request update for the initial address acquisition request. By using the request processing node to realize the request update operation, the problem of high cost and configuration of request update capability for the data acquisition node during the creation process is avoided.

[0142] After receiving a target address retrieval request, the data acquisition node uses the node address carried in the request to send the request to the address provider node via a relatively secure cross-regional data transmission link. The node then receives the target service address returned by the address provider node through the same data transmission link. This enables the acquisition of the target service address across regions, ensuring the security of data transmission and avoiding the data security issues that can occur when user nodes in a private network access DNS services through the public network.

[0143] The following description, in conjunction with Figure 3, uses the application of the address acquisition method provided in this disclosure in a multi-tenant domain name resolution scenario across all regions as an example to further illustrate the address acquisition method. Figure 3 shows a flowchart of the processing procedure of an address acquisition method provided in an embodiment of this disclosure. Based on Figure 3, it can be understood that the ECS in Figure 3 can be understood as a data acquisition node, the DNS Server as an address providing node, the PrivateZone as a request forwarding unit, the PrivateZone resolver as a request processing node, the user VPC as a data acquisition private network, the DNS service VPC as an address providing node private network, the interconnected VPCs in the first region as a first data transmission private network, the interconnected VPCs in the second region as a second data transmission private network, and the cross-regional network connected by VPC Peering as a cross-regional transmission network.

[0144] Furthermore, based on Figure 3, it can be seen that the address acquisition method implements ESC in the first region and obtains the address corresponding to the domain name from the DNS server in the second region through a cross-region approach; the key components of its address acquisition process include 5 VPCs (Virtual Private Networks), as shown below.

[0145] In the first region, the user VPC is used to access the virtual network and access services.

[0146] The interconnected VPC in Zone 1 is an interconnected VPC in the Virtual Internet Plane, with a network segment of 11.10.0.0 / 16;

[0147] In the first zone, the ISV VPC is a service provider that has deployed a weather service. The service provider's VPC is connected to the virtual network plane, and the network card address is 11.1*.0.1.

[0148] Interconnected VPCs in the second region: Interconnected VPCs in virtual domestic and international planes, with network segments of 11.2*.0.0 / 16. Interconnected VPC network segments cannot be duplicated;

[0149] The DNS service VPC in the second zone has a highly available distributed DNS service (DNS Server) deployed.

[0150] Specifically, it includes the following steps.

[0151] Steps 1 to 3 are the steps for updating the service registration domain name, as detailed below.

[0152] Step 1: The service provider registers its service with the virtual internet, and the virtual internet assigns a service address (11.1*.0.1 in Figure 3), and then transmits the service information and address information to the domain name management system.

[0153] Step 2: The domain name management system assigns a service domain name (weather.isv.a****est.com) and connects it to the service address (11.1*.0.1), and sends it to the DNS service to update the authoritative DNS configuration.

[0154] Step 3: DNS service (DNS authoritative service), after receiving the DNS domain name resolution update request, updates the local resolution configuration record. The detailed record is: 11.1*.0.1->weather.isv.a****est.com.

[0155] Steps 4 to 10 are the steps for requesting domain name access resolution, as detailed below.

[0156] Step 4: The application on the user's VPC ECS initiates a request to access weather.isv.a****est.com. At this time, the access request is sent to PrivateZone (i.e., the private DNS service) through the pre-configured default DNS address (PrivateZone address: 100.10*.2.138 / 139).

[0157] Step 5: PrivateZone analyzes the domain name with the suffix a****est.com carried in the access request, and therefore forwards the request to the PrivateZone resolver for access.

[0158] Step 6: The PrivateZone resolver forwards the received access node information to the target terminal node.

[0159] The specific execution steps are as follows:

[0160] First, after receiving the access request, the PrivateZone resolver determines the IP address of the DNS server and the data transmission link configured for that DNS server from the locally stored IP address information.

[0161] Secondly, the address (PrivateZone address) in the access request is replaced with the IP address of the DNS server to obtain a DNS query request (also known as DNS query traffic).

[0162] Finally, based on the data transmission link, outbound terminal resolution is performed to determine the outbound terminal node (a virtual network device), and the DNS request is forwarded to the configured target terminal node through the outbound terminal node.

[0163] Here, the target terminal node is the user VPC that has accessed the virtual internet, and the DNS server is configured with the address (11.2*.0.1).

[0164] Step 7: The user VPC sends the DNS query request to the DNS server in the second zone via cross-zone transport.

[0165] The specific execution steps are as follows:

[0166] First, after traffic enters the user's VPC, the user's VPC discovers that the target address carried in the DNS query request is 11.2*.0.1. Therefore, according to the user's VPC's basic routing configuration, the DNS query request will be sent to the ECS within the VPC, and then forwarded through the ECS within the VPC.

[0167] Secondly, after the DNS query request reaches the ECS, it is routed through the system and forwarded to the Virtual Internet Network (i.e., Interconnected VPC) in the first zone via the network card of the Virtual Internet.

[0168] Step 8: The interconnected VPC in the first region, based on the destination address 11.2*.0.1, is found to require cross-VPC access after routing analysis by the VSW. Therefore, the DNS query request is sent to the interconnected VPC in the second region through the cross-regional network established by VPC Peering, thereby realizing a DNS architecture available across all regions.

[0169] The term "full region" refers to the network architecture provided by this address acquisition method, which enables DNS services to be available across the entire region. Nodes in other regions can access the region where the DNS is located through the cross-regional network established by VPC Peering, thereby achieving a DNS architecture that is available across the entire region.

[0170] Step 9: The interconnected VPC of the second region, through VSW forwarding, sends the DNS query request to the DNS service VPC where the DNS server is located, and the DNS service VPC then sends the DNS query request to the DNS server.

[0171] Step 10: After receiving the DNS query request, the DNS server performs a query and resolution configuration based on the domain name information carried in the DNS query request, and obtains the resolution address corresponding to the domain name information as 11.1*.0.1; after obtaining the IP address corresponding to the weather service, it returns to the user's VPC ECS application along the same path.

[0172] It should be noted that after obtaining this IP address, the VPC ECS application will access the weather service through this IP address, as follows:

[0173] First, the application in the ECS sends a weather information query request to the weather service in the ISV VPC via the IP address. This request is then sent to the interconnected VPC in the first region via the network interface (ENI) of the ECS.

[0174] Secondly, based on the target address 11.1*.0.1, the VSW's routing analysis found that cross-VPC access was not required. Therefore, the weather information query request was sent to the weather server in the ISV VPC via routing forwarding.

[0175] Finally, the weather server, based on the weather information query request, returns the weather information to the user's VPC ECS application along the same path.

[0176] Based on the above steps, it can be seen that the address acquisition method in one or more embodiments of this disclosure provides a method and system for supporting multi-tenant domain name resolution across all regions in the cloud. This method and system for supporting multi-tenant domain name resolution across all regions in the cloud can be applied in virtual Internet scenarios. Its purpose is to enable service providers to publish user services and then publish them to the virtual Internet by assigning a fixed and unique access IP to the user service. For users accessing the virtual Internet, the design requires access via domain name. Correspondingly, during the process of users accessing the user service, the resolution method for the domain name is private network resolution, avoiding the risks to processes, security, and public opinion caused by using public domain names.

[0177] Based on this, the address acquisition method in one or more embodiments of this disclosure designs a DNS system that can access the virtual Internet, thereby enabling full Region (area) and multi-tenant use, distributed, and supporting multi-level caching; it realizes the effect of virtual Internet service domain names being configured instantly within the virtual Internet intranet and taking effect instantly for all users, eliminating the need to traverse all users' private DNS configurations for changes.

[0178] It should be noted that the address acquisition method in one or more embodiments of this disclosure firstly implements the construction of an interconnected intranet plane based on the entire Region; secondly, it implements the deployment of DNS services across multiple regions and connects them to the intranet plane, achieving full Region visibility; and finally, it utilizes PrivateZone to enable the availability of self-built DNS servers without requiring any special configuration of user resources (such as configuring Host or DNS). Therefore, it achieves the goal of providing domain name resolution across the entire intranet, transparently to customer VPC resources, and across the entire Region.

[0179] In one or more embodiments of this disclosure, the technical effects achieved by the address acquisition method include at least: global effectiveness, simplified configuration, security risk avoidance, availability across the entire Region intranet, and distributed architecture.

[0180] Among them, "valid across the entire region" refers to a solution that provides DNS resolution across the entire region via internal network links.

[0181] Simplified configuration: This refers to implementing service discovery and configuration management functions based on the entire region's intranet DNS, allowing customers to configure these functions only once.

[0182] Security risk avoidance: This refers to using the entire region's intranet as the DNS request link, avoiding the security issues caused by relying on the public network for resolution. In the future, it is expected that products such as PrivateLink can directly use this address acquisition method to avoid risks, which has great value.

[0183] Full Region Availability: This refers to a DNS architecture that is available across the entire Region.

[0184] Distributed architecture: refers to providing full region resolution services through a centrally distributed DNS service deployed in multiple regions. It implements a three-layer distributed architecture of top-level authoritative server, resolver forwarding, and host caching. Compared with the current privateZone DNS products on various cloud networks, which require configuring a privateZone record for each user when the service domain name changes, this reduces complexity.

[0185] Corresponding to the above method embodiments, this disclosure also provides an address acquisition system embodiment. Figure 4 shows a schematic diagram of the structure of an address acquisition system provided by an embodiment of this disclosure. As shown in Figure 4, the system includes a data acquisition node 402 in a first region, a request processing node 404 in the first region, and an address providing node 406 in a second region, wherein...

[0186] The data acquisition node 402 is configured to send an initial address acquisition request for the address providing node 406 to the request processing node 404, receive a target address acquisition request sent by the request processing node 404, use the node address carried in the target address acquisition request to send the target address acquisition request to the address providing node 406, and receive a target service address sent by the address providing node 406.

[0187] The request processing node 404 is configured to receive the initial address acquisition request, determine the node address of the address providing node 406 based on the domain name information carried in the initial address acquisition request, replace the address to be replaced carried in the initial address acquisition request with the node address, obtain the target address acquisition request, and send the target address acquisition request to the data acquisition node.

[0188] The address providing node 406 is configured to receive the target service address, determine the corresponding target service address based on the domain name information carried in the initial address acquisition request, and send the target service address to the data acquisition node 402.

[0189] Optionally, the address providing node 406 is further configured to receive the domain name information and the target service address sent by the target service node, and establish a correspondence between the domain name information and the target service address.

[0190] Optionally, the data acquisition node 402 is further configured to determine the data transmission network between the first region and the second region, wherein the data transmission network includes a first region transmission private network, a second region transmission private network and a cross-region transmission network, and the target address acquisition request is sent to the address providing node 406 through the first region transmission private network, the second region transmission private network and the cross-region transmission network.

[0191] The address providing node 406 is also configured to determine the data transmission network between the first region and the second region, and send the target service address to the data acquisition node 402 through the first region transmission private network, the second region transmission private network and the cross-region transmission network.

[0192] The address acquisition system provided in one or more embodiments of this disclosure, during the address acquisition process, the data acquisition node sends the initial address acquisition request of the address providing node in the second region to the request processing node in the first region. The request processing node uses the target address acquisition request obtained by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node, thereby realizing the request update for the initial address acquisition request. By using the request processing node to realize the request update operation, the problem of high cost and configuration of request update capability for the data acquisition node during the creation process is avoided.

[0193] Furthermore, after receiving a target address retrieval request, the data acquisition node uses the node address carried in the request to send the request to the address provider node via a relatively secure data transmission link. It then receives the target service address returned by the address provider node through the same data transmission link. This enables the acquisition of the target service address across regions, ensuring the security of data transmission and avoiding the data security issues that can occur when user nodes in a private network access DNS services through the public network.

[0194] The above is an illustrative scheme of an address acquisition system according to this embodiment. It should be noted that the technical solution of this address acquisition system and the technical solution of the address acquisition method described above belong to the same concept. For details not described in detail in the technical solution of the address acquisition system, please refer to the description of the technical solution of the address acquisition method described above.

[0195] Referring to Figure 5, Figure 5 shows a flowchart of another address acquisition method provided according to an embodiment of the present disclosure. The address acquisition method is applied to a request processing node in a first region and specifically includes the following steps.

[0196] Step 502: Receive an initial address acquisition request sent by the data acquisition node for the address providing node, wherein the address providing node is located in the second region and the request processing node is located in the first region.

[0197] Step 504: Replace the address to be replaced carried in the initial address acquisition request with the node address of the address providing node to obtain the target address acquisition request.

[0198] Step 506: Send the target address acquisition request to the data acquisition node, so that the data acquisition node sends the target address acquisition request to the address providing node and receives the target service address sent by the address providing node, wherein the target service address is determined by the address providing node based on the domain name information carried in the target address acquisition request.

[0199] This disclosure provides one or more embodiments of an address acquisition method applied to a request processing node. During the process of a data acquisition node acquiring a target service address, it can receive an initial address acquisition request from an address providing node for a second region. By replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node, a target address acquisition request is obtained, thereby achieving a request update for the initial address acquisition request. By implementing the request update operation through the request processing node, the high cost of configuring request update capabilities for the data acquisition node during its creation is avoided.

[0200] After receiving the target address retrieval request, the subsequent data acquisition node uses the node address carried in the target address retrieval request to send the target address retrieval request to the address providing node through a relatively secure cross-regional data transmission link. It then receives the target service address returned by the address providing node based on the same data transmission link. This enables the acquisition of the target service address in a cross-regional manner, ensuring the security of data transmission and avoiding the data security issues that may arise when user nodes in a private network access DNS services through the public network.

[0201] The above is an illustrative scheme of another address acquisition method in this embodiment. It should be noted that the technical solution of this other address acquisition method belongs to the same concept as the technical solution of the address acquisition method described above. For details not described in detail in the technical solution of the other address acquisition method, please refer to the description of the technical solution of the address acquisition method described above.

[0202] Corresponding to the above method embodiments, this disclosure also provides an address acquisition device embodiment. Figure 6 shows a schematic diagram of the structure of an address acquisition device provided in one embodiment of this disclosure. As shown in Figure 6, the device is applied to a data acquisition node in a first area and includes:

[0203] The first request sending module 602 is configured to send an initial address acquisition request for an address providing node to a request processing node, wherein the address providing node is located in a second region and the request processing node is located in the first region;

[0204] The request receiving module 604 is configured to receive a target address acquisition request sent by the request processing node, wherein the target address acquisition request is obtained by the request processing node by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node;

[0205] The second request sending module 606 is configured to use the target address to obtain the node address carried in the request, and send the target address acquisition request to the address providing node;

[0206] The address acquisition module 608 is configured to receive a target service address sent by the address providing node, wherein the target service address is determined by the address providing node based on the domain name information carried in the target address acquisition request.

[0207] Optionally, the address acquisition device further includes a request generation module, configured to:

[0208] Upon receiving a service access request from a client, the domain name information carried in the service access request is determined, and an initial address acquisition request is generated based on the domain name information and the preset address to be replaced. The service access request is generated by the client based on the service access operation performed by the user on the service page.

[0209] Optionally, the address acquisition device further includes a data processing module, configured to:

[0210] Based on the target service address, a data processing request is sent to the target service node, wherein the target service address is the address of the target service node;

[0211] Receive the data processing result determined by the target service node based on the data processing request.

[0212] Optionally, the first request sending module 602 is further configured to:

[0213] Based on the first area transmission network between the data acquisition node and the request processing node, an initial address acquisition request for the address providing node is sent to the request processing node;

[0214] The request receiving module 604 is further configured to:

[0215] The request processing node receives the request based on the target address sent by the first regional transmission network.

[0216] Optionally, the first regional transmission network is used for data transmission between the data acquisition node and the request processing node, and the first regional transmission network includes a data acquisition private network, in which the data acquisition node is located.

[0217] Optionally, the second request sending module 606 is further configured to:

[0218] Determine the data transmission network between the first region and the second region;

[0219] Using the node address carried in the target address acquisition request, the target address acquisition request is sent to the address providing node through the data transmission network;

[0220] The address acquisition module 608 is further configured to:

[0221] Receive the target service address sent by the address providing node through the data transmission network.

[0222] Optionally, the first request sending module 602 is further configured to

[0223] Based on the address to be replaced carried in the initial address acquisition request, the initial address acquisition request is sent to the request forwarding unit;

[0224] Using the request forwarding unit, the request processing node is determined based on the domain name information carried in the initial address acquisition request, and the initial address acquisition request is forwarded to the request processing node.

[0225] Optionally, the data transmission network is used to perform data transmission operations between the first region and the second region. The data transmission network includes a first region transmission private network, a second region transmission private network, and a cross-region transmission network. The data transmission operations are performed through the first region transmission private network, the second region transmission private network, and the cross-region transmission network.

[0226] The address acquisition device provided in one or more embodiments of this disclosure, during the address acquisition process, sends an initial address acquisition request for an address providing node in a second region to a request processing node in a first region. The request processing node uses the target address acquisition request obtained by replacing the address to be replaced carried in the initial address acquisition request with the node address of the address providing node, thereby realizing the request update for the initial address acquisition request. By using the request processing node to realize the request update operation, the problem of high cost and configuration of request update capability for the data acquisition node during the creation process is avoided.

[0227] After receiving a target address retrieval request, the data acquisition node uses the node address carried in the request to send the request to the address provider node via a relatively secure cross-regional data transmission link. The node then receives the target service address returned by the address provider node through the same data transmission link. This enables the acquisition of the target service address across regions, ensuring the security of data transmission and avoiding the data security issues that can occur when user nodes in a private network access DNS services through the public network.

[0228] The above is a schematic scheme of an address acquisition device according to this embodiment. It should be noted that the technical solution of this address acquisition device and the technical solution of the address acquisition method described above belong to the same concept. For details not described in detail in the technical solution of the address acquisition device, please refer to the description of the technical solution of the address acquisition method described above.

[0229] Figure 7 shows a structural block diagram of a computing device 700 according to an embodiment of the present disclosure. The components of the computing device 700 include, but are not limited to, a memory 710 and a processor 720. The processor 720 is connected to the memory 710 via a bus 730, and a database 750 is used to store data.

[0230] The computing device 700 also includes an access device 740, which enables the computing device 700 to communicate via one or more networks 760. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 740 may include one or more of any type of wired or wireless network interface (e.g., a network interface controller (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0231] In one embodiment of this disclosure, the aforementioned components of the computing device 700, as well as other components not shown in FIG. 7, may be interconnected, for example, via a bus. It should be understood that the computing device block diagram shown in FIG. 7 is merely for illustrative purposes and is not intended to limit the scope of this disclosure. Those skilled in the art can add or replace other components as needed.

[0232] The computing device 700 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 700 can also be a mobile or stationary server.

[0233] The processor 720 is configured to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the above address acquisition method.

[0234] The various embodiments in this disclosure are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computing device embodiments are basically similar to the address acquisition method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the address acquisition method embodiments.

[0235] An embodiment of this disclosure also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the address acquisition method described above.

[0236] The various embodiments in this disclosure are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computer-readable storage medium embodiments are basically similar to the address acquisition method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the address acquisition method embodiments.

[0237] An embodiment of this disclosure also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described address acquisition method.

[0238] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the address acquisition method described above belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the address acquisition method described above.

[0239] The foregoing has described specific embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0240] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0241] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of this disclosure are not limited to the described order of actions, because according to the embodiments of this disclosure, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments of this disclosure.

[0242] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0243] The preferred embodiments disclosed above are merely illustrative of this disclosure. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments of this disclosure.

[0244] These embodiments are selected and specifically described in this disclosure to better explain the principles and practical applications of the embodiments of this disclosure, thereby enabling those skilled in the art to better understand and utilize this disclosure. This disclosure is limited only by the claims and their full scope and equivalents.

Claims

1. An address obtaining method applied to a data obtaining node in a first region, comprising: sending an initial address obtaining request for an address providing node to a request processing node, wherein the address providing node is located in a second region and the request processing node is located in the first region; receiving a target address obtaining request sent by the request processing node, wherein the target address obtaining request is obtained by the request processing node by replacing a to-be-replaced address carried in the initial address obtaining request with a node address of the address providing node; sending the target address obtaining request to the address providing node by using the node address carried in the target address obtaining request; and receiving a target service address sent by the address providing node, wherein the target service address is determined by the address providing node according to domain name information carried in the target address obtaining request. 2.The address obtaining method of claim 1, before the sending of the initial address obtaining request for the address providing node to the request processing node, further comprising: in a case where a service access request sent by a client is received, determining domain name information carried in the service access request, and generating the initial address obtaining request based on the domain name information and a preset to-be-replaced address, wherein the service access request is generated by the client based on a service access operation performed by a user on a service page. 3.The address obtaining method of claim 1 or 2, after the receiving of the target service address sent by the address providing node, further comprising: sending a data processing request to a target service node based on the target service address, wherein the target service address is an address of the target service node; and receiving a data processing result determined by the target service node according to the data processing request. 4.The address obtaining method of any one of claims 1-3, the sending of the initial address obtaining request for the address providing node to the request processing node comprising: sending the initial address obtaining request for the address providing node to the request processing node according to a first region transmission network between the data obtaining node and the request processing node; and the receiving of the target address obtaining request sent by the request processing node comprising: receiving the target address obtaining request sent by the request processing node according to the first region transmission network. 5.The address obtaining method of claim 4, the first region transmission network is used for data transmission between the data obtaining node and the request processing node, and the first region transmission network comprises a data obtaining private network, and the data obtaining node is located in the data obtaining private network. 6.The address obtaining method of any one of claims 1-3, the sending of the initial address obtaining request for the address providing node to the request processing node comprising: sending the initial address obtaining request to a request forwarding unit according to the to-be-replaced address carried in the initial address obtaining request. The request forwarding unit is configured to determine the request processing node according to the domain name information carried by the initial address acquisition request, and forward the initial address acquisition request to the request processing node.

7. The address acquisition method of any one of claims 1-6, wherein the sending the target address acquisition request to the address providing node by using the node address carried by the target address acquisition request comprises: determining a data transmission network between the first region and the second region; sending the target address acquisition request to the address providing node by using the node address carried by the target address acquisition request through the data transmission network; the receiving the target service address sent by the address providing node comprises: receiving the target service address sent by the address providing node through the data transmission network.

8. The address acquisition method of claim 7, wherein the data transmission network is configured to perform a data transmission operation between the first region and the second region, and the data transmission network comprises a first-region transmission private network, a second-region transmission private network, and a cross-region transmission network, and the data transmission operation is performed through the first-region transmission private network, the second-region transmission private network, and the cross-region transmission network.

9. An address acquisition method applied to a request processing node in a first region, comprising: receiving an initial address acquisition request sent by a data acquisition node and directed to an address providing node, wherein the address providing node is located in a second region, and the request processing node is located in the first region; replacing a to-be-replaced address carried by the initial address acquisition request with a node address of the address providing node to obtain a target address acquisition request; sending the target address acquisition request to the data acquisition node, so that the data acquisition node sends the target address acquisition request to the address providing node, and receives a target service address sent by the address providing node, wherein the target service address is determined by the address providing node according to domain name information carried by the target address acquisition request.

10. An address acquisition system, comprising a data acquisition node in a first region, a request processing node in the first region, and an address providing node in a second region, wherein: the data acquisition node is configured to send an initial address acquisition request directed to the address providing node to the request processing node, receive a target address acquisition request sent by the request processing node, send the target address acquisition request to the address providing node by using a node address carried by the target address acquisition request, and receive a target service address sent by the address providing node; the request processing node is configured to receive the initial address acquisition request, determine a node address of the address providing node according to domain name information carried by the initial address acquisition request, replace a to-be-replaced address carried by the initial address acquisition request with the node address to obtain the target address acquisition request, and send the target address acquisition request to the data acquisition node. The address providing node is configured to receive the target service address, determine the corresponding target service address according to the domain name information carried in the initial address acquisition request, and send the target service address to the data acquisition node. 11.The address acquisition system of claim 10, wherein the address providing node is further configured to receive the domain name information and the target service address sent by the target service node, and establish a corresponding relationship between the domain name information and the target service address.

12. The address acquisition system of claim 10 or 11, the data acquisition node, further configured to determine a data transfer network between the first region and the second region, wherein, The data transmission network comprises a first regional transmission private network, a second regional transmission private network, and a cross-regional transmission network, and the target address acquisition request is sent to the address providing node through the first regional transmission private network, the second regional transmission private network, and the cross-regional transmission network. The address providing node is further configured to determine the data transmission network between the first region and the second region, and send the target service address to the data acquisition node through the first regional transmission private network, the second regional transmission private network, and the cross-regional transmission network. 13.A computing device, comprising: a memory and a processor; the memory is configured to store computer programs / instructions, and the processor is configured to execute the computer programs / instructions, which realize the address acquisition method of any one of claims 1 to 8 or the steps of the address acquisition method of claim 9 when executed by the processor. 14.A computer readable storage medium storing computer programs / instructions, which realize the address acquisition method of any one of claims 1 to 8 or the steps of the address acquisition method of claim 9 when executed by the processor. 15.A computer program product comprising computer programs / instructions, which realize the address acquisition method of any one of claims 1 to 8 or the steps of the address acquisition method of claim 9 when executed by the processor.

Images