HK40083053B - Domain name resolution method, apparatus, electronic device, and storage medium - Google Patents

Description

Domain name resolution methods, devices, electronic equipment and storage media

Background Technology

With the advancement of science and technology, internet technology has developed rapidly. Among internet technologies, domain name resolution technology is a crucial foundation for accessing websites or resources. Domain name resolution technology refers to the conversion technology between domain names and Internet Protocol (IP) addresses; for example, resolving the domain name "example.com" entered by a client to the corresponding IP address "1.1.1.1", the client can then use the IP address to access the website corresponding to the domain name.

In related technologies, various entities can apply for registration of internal networks in a public network environment. Each internal network is configured with at least one Domain Name Server (DNS) to provide domain name resolution services for specific business domain names within the corresponding internal network. Specifically, before providing domain name resolution services, each DNS server needs to pre-configure the mapping relationship between each corresponding business domain name and each IP address on the DNS server. Thus, when the DNS server receives a resolution request, it will perform the conversion between the business domain name and the IP address based on the configured mapping relationship.

However, based on the aforementioned approach, each internal network needs to build its own domain name server to provide domain name resolution services for different business domain names. This increases the complexity and cost of network operation and maintenance to some extent, and is not conducive to domain name resolution management in a large-scale environment.

Summary of the Invention

This application provides a domain name resolution method, apparatus, electronic device, and storage medium to reduce network operation and maintenance costs.

On the one hand, a domain name resolution method is provided, applied to public network servers, the method comprising:

Receive a domain name resolution request sent by a first object, wherein the domain name resolution request carries target domain name information;

Based on the target domain name information, search the database to see if there is a target IP address associated with the target domain name information. The database records at least one domain name and associated IP address corresponding to each internal network established in the public network.

When it is determined that the target IP address exists in the database, the target IP address is fed back to the first object.

On the one hand, a domain name resolution device is provided for use on a public network server, the device comprising:

A receiving unit is configured to receive a domain name resolution request sent by a first object, wherein the domain name resolution request carries target domain name information;

The processing unit is used to search in the database for a target IP address associated with the target domain name information based on the target domain name information. The database records at least one domain name and associated IP address for each internal network established in the public network.

The feedback unit is used to feed back the target IP address to the first object when it is determined that the target IP address exists in the database.

Optionally, after receiving the domain name resolution request, the processing unit is further configured to:

For a preset time period, the cumulative number of other domain name resolution requests carrying the target domain name information received is counted;

If it is determined that the cumulative number of times corresponding to the preset time period reaches a set threshold, a prompt message is sent to the first object. The prompt message is used to prompt the first object to perform a duplicate check on the interface address.

On the one hand, an electronic device is provided, including a processor and a memory, wherein the memory stores program code that, when executed by the processor, causes the processor to perform the aforementioned domain name resolution method.

On one hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the aforementioned domain name resolution method.

This application provides a computer-readable storage medium including program code. When the program product is run on an electronic device, the program code is used to cause the electronic device to perform the steps of any of the above-described domain name resolution methods.

The beneficial effects of this application are as follows:

The domain name resolution method, apparatus, electronic device, and storage medium provided in this application embodiment have the following advantages: since the database corresponding to the public network server records at least one domain name information and associated IP address corresponding to each internal network established in the public network, the public network server can directly obtain the target IP address associated with the target domain name information and return the target IP address to the first object. This eliminates the need to build domain name servers in each internal network, thereby reducing the construction and maintenance of domain name servers and effectively reducing network construction costs and network operation and maintenance costs.

Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

Attached Figure Description

To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

Figure 1 is a schematic diagram of a domain name resolution method in related technologies;

Figure 2 is a schematic diagram of an optional application scenario in an embodiment of this application;

Figure 3 is a schematic flowchart of a method for determining a database in an embodiment of this application;

Figure 4 is a schematic diagram of the associated storage of object identifiers and interface addresses in an embodiment of this application;

Figure 5 is another schematic diagram of the associated storage of object identifiers and interface addresses in an embodiment of this application;

Figure 6 is a schematic diagram of a database including a first binding relationship in an embodiment of this application;

Figure 7 is a schematic diagram of the display interface for configuring domain name information in an embodiment of this application;

Figure 8 is a schematic diagram of a database including a second binding relationship in an embodiment of this application;

Figure 9 is a schematic diagram of a complete database including a first binding relationship and a second binding relationship in an embodiment of this application;

Figure 10 is a schematic diagram of a domain name resolution scenario in an embodiment of this application;

Figure 11A is a schematic flowchart of a domain name resolution method according to an embodiment of this application;

Figure 11B is a schematic diagram illustrating the cumulative number of times in an embodiment of this application;

Figure 11C is a schematic diagram of a display of prompt information in an embodiment of this application;

Figure 12 is a schematic diagram of a complete domain name resolution method in an embodiment of this application;

Figure 13 is a schematic diagram of the composition structure of a domain name resolution device in an embodiment of this application;

Figure 14 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application.

Detailed Implementation

To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

To facilitate understanding of the technical solutions provided in the embodiments of this application, some key terms used in the embodiments of this application will be explained below:

1. Internal Network: An internal network, also known as an intranet or local area network, accesses the Internet through a public gateway. The coverage area of an intranet is generally within a radius of several kilometers. Its advantages, such as easy installation, cost-effectiveness, and convenient expansion, make it widely used in various types of offices.

2. Public network: The public network is generally in contrast to the internal network. Specifically, the Internet Protocol (IP) address obtained by a computer accessing the Internet through an internal network is a reserved address on the Internet, meaning that the internal network generally accesses the Internet through a public gateway; while the IP address obtained by a computer accessing the Internet through a public network is a public address on the Internet, meaning that computers on the public network can freely access each other with other computers on the Internet.

3. Public cloud: Generally refers to a cloud provided by a third-party provider that can be used by users. Public clouds are generally accessible via the Internet, and their core attribute is shared resource service.

4. Private Network: A private network generally refers to a Virtual Private Cloud (VPC). A VPC is a private network on a public cloud, meaning it's a user-defined network. For example, users can customize private network segments, subnet segments, and routing control policies through the console or Application Programming Interface (API). The network can be further divided into multiple subnets, and applications and services can be deployed within each subnet. Furthermore, a private network can be configured with a public gateway to access the Internet.

5. Hosts: This is generally a system file whose function is to establish a database that associates commonly used website domains with their corresponding IP addresses.

6. Domain name: A domain name, also known as a network domain, is generally a name of a computer or group of computers on the Internet consisting of a string of names separated by dots. It is used to locate and identify the computer during data transmission.

7. IP address: Generally refers to Internet Protocol address or Internet Protocol address. Specifically, an IP address is a unified address format provided by the IP protocol. It assigns a logical address to every network and every host on the Internet to mask the differences in physical addresses.

Currently, referring to Figure 1, which is a schematic diagram of domain name resolution in a public network environment in related technologies, each internal network needs to build at least one corresponding domain name server. Then, based on configuring the domain name server with its respective business domain name and corresponding IP address, when a domain name resolution request is received, the domain name server can resolve the domain name information to obtain the corresponding IP address.

For example, internal network 1 has its own domain name server 1. Then, the domain name of business A, for example, "xxx.zzzzz.com", is configured with the corresponding IP address on domain name server 1. Object 1 of internal network 1 sends a domain name resolution request for business A's domain name to domain name server 1. Then, domain name server 1 can determine whether there is an IP address corresponding to business A's domain name based on the domain name information carried in the domain name resolution request. When domain name server 1 determines that there is an IP address corresponding to business A's domain name, it sends the IP address back to object 1 of internal network 1.

When Domain Name Server 1 determines that there is no IP address corresponding to the domain name of business A, it can first send a request to the root name server to inquire about the address of the name server for ".com". The root server then returns that there are "a to m" top-level name servers containing ".com". Domain Name Server 1 then sends a request to any of the top-level name servers containing the domain name information returned by the root server, for example, top-level name server 'a', to inquire about the address of the name server for "zzzzz.com". This top-level name server then returns to Domain Name Server 1 that there are "s1 to s4" authoritative name servers for "zzzzz.com". Domain Name Server 1 then sends a request to one of these authoritative name servers, for example, domain name server 's1', to inquire about the resolved value of "xxx.zzzzz.com". The authoritative name server returns the domain name "fffff". Further, based on the aforementioned query order from Domain Name Server 1 to the root name server and then to the authoritative name server, the query continues until an IP address is found. Then, object 1 can obtain the IP address sent by Domain Name Server 1.

Therefore, this application provides a novel system architecture for domain name resolution. This architecture eliminates the need for separate domain name resolution servers for each internal network. Instead, it uses a database on a public network server to determine the IP address corresponding to each domain name. Specifically, the database on the public network server records at least one domain name and its associated IP address for each internal network established on the public network. Therefore, the public network server can perform domain name resolution based on the database and the domain name to obtain the corresponding IP address. This effectively reduces network construction and maintenance costs while significantly improving the efficiency of domain name resolution. Furthermore, it enables comprehensive management of domain name resolution for multiple internal networks in a large-scale environment.

After introducing the design concept of the embodiments of this application, the following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of this application can be applied. It should be noted that the application scenarios described below are only for illustrating the embodiments of this application and are not intended to limit the scope. In specific implementation, the technical solutions provided by the embodiments of this application can be flexibly applied according to actual needs.

The solution provided in this application embodiment can be applied to most domain name resolution scenarios. Referring to Figure 2, which is a schematic diagram of a scenario provided in this application embodiment, the scenario may include multiple terminal devices 201 and a public network server 202, wherein terminal devices 201-1, terminal devices 201-2, ..., terminals 101-n can be used by different users.

Furthermore, in this embodiment, the user can log in to their publicly registered account on terminal device 201 and, after logging in, send a domain name resolution request to the public server 202 via the terminal device. Specifically, the network corresponding to the user's terminal device 201 can be understood as an internal network. This internal network can be implemented in various ways, such as: the office network connected to the user's terminal device 201, the home network connected to the user's terminal device 201, or the private cloud network connected to the user's terminal device 201, which is the network that the user has applied for on the public network using their corresponding account. The aforementioned account can be a personal account or a company account, and this embodiment does not impose any restrictions on this.

In the following text, "account" may be described as an "object," such as a first object, a second object, etc. However, it should be noted that "first object" and "second object," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data used can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein.

Terminal device 201 can be, for example, a mobile phone, tablet computer (PAD), personal computer (PC), smart TV, smart in-vehicle device, and wearable device. Each terminal device 101 may include one or more processors 2011, memory 2012, and I/O interface 2013 for interacting with the server.

In this embodiment of the application, the public network server 202 may be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN), and big data and artificial intelligence platforms, but is not limited to this.

For example, each user can log in to their registered account on the public network on terminal device 201 and send a domain name resolution request to public network server 202. Similarly, public network server 202 will process the domain name resolution requests sent by each object. For example, if object A sends a domain name resolution request to public network server 202 through terminal device 201-1, then public network server 202 will process the domain name resolution request and return the IP address corresponding to the domain name information carried in the domain name resolution request to object A.

In this embodiment, terminal device 201 and public network server 202, as well as various terminal devices 101, can communicate directly or indirectly through one or more networks 203. The network 203 can be a wired network or a wireless network. For example, the wireless network can be a mobile cellular network or a Wireless-Fidelity (WIFI) network, or other possible networks. This application embodiment does not limit this.

Of course, the method provided in this application embodiment is not limited to the application scenario shown in Figure 2, and can also be used in other possible application scenarios. This application embodiment does not impose any limitations. The functions that each device in the application scenario shown in Figure 2 can achieve will be described in subsequent method embodiments, and will not be elaborated on here.

In this embodiment of the application, a database is set up in the public network server. Each object can apply to the public network server to establish an association relationship, and the association relationship established by the public network server for each object is recorded in the database.

Specifically, in this embodiment, each object that sends a domain name resolution request to the public network server can be referred to as a first object, and each object that applies to the public network server to establish an association during the preprocessing stage can be referred to as a second object. After applying to establish an association, each second object can also send a domain name resolution request to the public network server as a first object. In addition, other objects that have not established an association in the public network, other than the second objects, can also send a domain name resolution request to the public network server as a first object.

Referring to Figure 3, in this embodiment of the application, the database establishment process is described using a second object as an example. The specific process is as follows:

Step 301: Receive the association establishment request sent by the second object, wherein the second object has already requested to establish the corresponding internal network in the public network.

Specifically, once it is determined that the second object has requested the establishment of the corresponding internal network in the public network, the second object can send an association establishment request to the public network server. The association establishment request must at least carry the identifier of the second object.

Step 302: Based on the association relationship, establish a request, assign a corresponding interface address to the second object, create a corresponding domain name resolution instance for the second object, and generate a corresponding instance identifier; wherein, the domain name resolution instance is used to resolve the domain name information corresponding to the internal network requested by the second object.

In this embodiment of the application, the public network server can allocate a corresponding interface address to the second object. Then, the second object can send a domain name resolution request to the public network server based on the interface address allocated to it by the public network server, so that the public network server can process the domain name resolution request sent by the second object; or, other first objects can obtain the corresponding interface address from the second object and send a domain name resolution request to the public network server, so that the public network server can process the domain name resolution request sent by the first objects.

The interface address can be an Elastic IP Address (EIP), or other types, which are not limited in this embodiment.

Specifically, when the public network server receives a request from the second object to establish a relationship, the public network server can determine whether the relationship establishment request is valid. If the relationship establishment request is valid, the public network server can allocate the corresponding interface address to the second object based on the relationship establishment request and the resource pool corresponding to the public network server. When the second object applies to revoke the relationship, the public network server can reclaim the interface address.

Furthermore, when the public network server distributes and reclaims the interface address of the second object, it can bind the identifier of the second object to the interface address and store it in the corresponding database of the public network server. It should be noted that the representation of the object identifier can include, but is not limited to, characters, Chinese characters, graphics, or other languages and scripts, and is not limited in this embodiment.

In related technologies, the hosts file only includes domain names and their corresponding IP addresses, as shown in Table 1. Table 1 is a schematic table of the storage of hosts files in related technologies:

Table 1

domain name IP address www.example1.com 192.168.0.100 bbb.qq.com 192.168.100.100, 201.201.203.204, 10.10.10.13 xxx.example2.com 222.22.101.103, 148.148.148.101, 103.104.10.77

In this application, the identifier of the second object and the address allocated to the second object can be stored in the form of a table. For example, see Table 2, which is a storage illustration table in this application:

Table 2

The identifier of the second object Interface address ID_a 134.158.11.13 ID_c 22.22.22.22 ID_f 10.134.156.11

As shown in Table 2, in this application, the identifier of a second object can be associated with an interface address for storage.

For example, if the identifier of the second object A is determined to be ID_a, and the interface address to which the second object A is successfully assigned is represented as IP_a, then an array of approximately (ID_a, IP_a) can be obtained, and the array can be stored in the database.

For example, as shown in Figure 4, the database includes second object 1 and its corresponding interface address 1, second object 2 and its corresponding interface address 2, ..., second object n1 and its corresponding interface address n1, where n1 is a positive integer greater than 1.

In this embodiment of the application, a public network server can assign an interface address to a second object, and the second object can also assign the interface address to other objects associated with it, so that other objects can perform domain name resolution based on the interface address.

For example, the identifier of the second object, the identifier of the sub-objects of the second object, and the address allocated to the second object are stored accordingly. For example, see Table 3, which is another storage illustration table in this application:

Table 3

The identifier of the second object The identifier of the sub-object of the second object Interface address ID_a ID_a-1 134.158.11.13 ID_c ID_c-1, ID_c-2 22.22.22.22 ID_f ID_f-1, ID_f-2..., ID_f-n 10.134.156.11

For example, referring to Figure 5, the database includes second object 1 and its corresponding interface address 1, second object 2 and its corresponding interface address 1, ..., second object n1 and its corresponding interface address n1. Second object 1 can send its corresponding interface address 1 to its child object 1-01, child object 1-02, ..., child object 1-0m1; second object n1 can send its corresponding interface address n1 to its child object n1-01, child object n1-02, where m1 and n1 are both positive integers greater than 1.

In this embodiment of the application, the public network server can also be used to create a corresponding domain name resolution instance for the second object and generate a corresponding instance identifier; wherein, the domain name resolution instance is used to resolve the domain name information corresponding to the internal network requested by the second object.

Specifically, the instance identifier can be an identifier containing characters related to the object identifier. For example, if the object identifier is represented as ID_w, then the instance identifier can be represented as Cloud_HostsID_W. Of course, the instance identifier can also be determined based on other identifier determination methods, and the identifier can be English letters, numbers, and other characters. This application embodiment does not impose any limitations.

Step 303: Associate and bind the interface address corresponding to the second object with the instance identifier to determine the first binding relationship, and store the first binding relationship in the database.

Specifically, the public server can associate and bind the interface address corresponding to the second object with the instance identifier to determine the first binding relationship, and store the first binding relationship in the database.

As can be seen, once the interface address corresponding to the second object is obtained, the instance identifier can be determined based on the interface address, and the domain name resolution instance can be called. This identifier-based association triggering can more easily and quickly determine the corresponding instance.

Specifically, the public server can store the first binding relationship corresponding to all objects that have applied to establish an association in the database. To facilitate database management, the instance identifier and interface address in any first binding relationship can be stored in the database as an array.

For example, the first binding relationship can be represented as (IP_c, Cloud_HostsID_C), and the second binding relationship can be represented as (IP_t, Cloud_HostsID_T). In the database, it is stored as: (IP_c, Cloud_HostsID_C); (IP_t, Cloud_HostsID_T).

For example, as shown in Figure 6, the database includes a first binding relationship 1 corresponding to the second object 1, a first binding relationship 2 corresponding to the second object 2, ..., a first binding relationship n2 corresponding to the second object n2. Here, first binding relationship 1 is the relationship determined by binding interface address 1 and instance identifier 1; first binding relationship 2 is the relationship determined by binding interface address 2 and instance identifier 2; and first binding relationship n2 is the relationship determined by binding interface address n2 and instance identifier n2, where n2 is a positive integer greater than 1.

Step 304: Receive the domain name configuration information sent by the second object. The domain name configuration information includes at least one domain name information corresponding to the internal network and the IP address associated with each domain name information.

Specifically, after the first binding relationship is determined, the public server can also receive the domain name configuration information sent by the second object, then associate and bind the instance identifier corresponding to the second object with the domain name configuration information to determine the second binding relationship, and store the second binding relationship in the database.

Specifically, the second object can select domain name configuration information on the terminal device, so that the public server can receive the domain name configuration information sent by the second object. It should be noted that the selection method can be a single click, double click, or other methods, and this embodiment does not limit the method.

In this embodiment, the second object can configure its corresponding DNS IP address as the interface address it is assigned, and then select the domain name configuration information on the terminal device. Specifically, it can first select the DNS records to be resolved, such as www.IN.A.192.168.0.1, www.IN.A.168.168.0.1, and ccc.IN.A.10.101.10.10, and then determine the corresponding domain name information, such as qq.com.

It should be noted that in this application embodiment, the second object can be configured with multiple IP addresses for one domain name, or multiple domain names for one IP address; this application does not impose any restrictions on this. For example, referring to Figure 7, Figure 7 is a schematic diagram of an interface for selecting domain name configuration information, exemplarily shown in an embodiment of this application. When a user sets domain name configuration information on a terminal device, the user can choose to manually enter the domain name information on the terminal device, or select the default configured domain name information from preset domain name candidates. The terminal device will determine the various domain name information included in the domain name configuration information based on the user's operation.

As shown in Figure 7, when setting domain name configuration information on a terminal device, the user can choose to manually enter "xxx.zzzzzz.com" on the terminal device, or select the default configuration "xxx.zzzwsz.com" from the preset domain name candidates, namely "xxx.zzzwsz.com, ..., xxx.zzsopz.com".

In addition, regarding the IP address corresponding to the domain name information contained in the domain name configuration information, users can choose to manually enter the IP address on the terminal device, or they can choose the default IP address from the preset IP address candidates. The terminal device will then select the IP address from the domain name configuration information based on the user's operation.

As shown in Figure 7, when setting domain name configuration information on a terminal device, the user can choose to manually enter "11.11.34.222" on the terminal device, or select the default configuration "11.11.20.221" from the preset IP address candidates, namely "11.11.20.221, ..., 11.11.13.146".

For example, domain name configuration information may also include, but is not limited to, the following: weight, record type, and availability status information.

The record types can include, but are not limited to, address (A) records, name server (NS) records, mail exchange (MX) records, and canonical name (CNAME) records. Specifically, an A record specifies the IP address corresponding to a hostname (or domain name); a name server record specifies which DNS server resolves the domain name; a mail exchange record points to a mail server and is used by email systems to locate the mail server based on the recipient's address suffix when sending emails; and an alias record allows multiple domain names to be mapped to the same computer.

Specifically, the weight is used to represent the strategy for returning records within the same subdomain, and it is mainly used to achieve dynamic load balancing across IP addresses. The weight value is generally a positive integer greater than 1, for example, a weight value between 1 and 100.

For example, if a domain name corresponds to two IP addresses, designated as IP address 1 and IP address 2, and the weight of IP address 1 is 10, then when a domain name resolution request for that domain name is received, if the first IP address was returned previously, the second IP address will be returned for the next 10 requests. Furthermore, after 10 requests have been returned using the second IP address, the first IP address will be returned for any subsequent domain name resolution request. In other words, when a domain name resolution request is received, both IP addresses are returned cyclically based on their weights to ensure load balancing across all IP addresses.

Furthermore, the information regarding the weight, record type, and availability status in the domain name configuration can all be selected and confirmed by the user from the corresponding options, which will not be elaborated further here.

It should be noted that Figure 7 is an exemplary interface display diagram. In specific implementations, the display method of the functional modules of each configuration information in the domain name configuration information can be determined according to the actual implementation situation. For example, it can be displayed horizontally, or the module graphics of each functional module are different, etc. This application embodiment does not limit it.

It should be noted that, in this embodiment of the application, each domain name in the domain name configuration information bound to an interface address is different; that is, each domain name in the domain name configuration information is unique, but each domain name can correspond to multiple IP addresses. In other words, the domain name configuration information can include at least one domain name, and each domain name can correspond to multiple IP addresses.

Furthermore, in this embodiment, the domain name configuration information can also be updated based on user operations. Specifically, the user can update it at any time based on actual needs through the terminal device, or an update prompt can be sent to the terminal device based on a preset time interval, so that the user can update the domain name configuration information through the terminal device. The preset time interval can be flexibly configured based on the actual application environment, such as one week, one month, etc., and is not limited in this embodiment.

Step 305: Associate and bind the instance identifier corresponding to the second object with the domain name configuration information to determine the second binding relationship, and store the second binding relationship in the database.

Specifically, after the public server provides the interface address to the second object, it can also associate and bind the domain name configuration information and instance identifier determined by the second object itself, thereby determining the second binding relationship.

By using the above configuration method, the second object can customize the required domain name configuration information, thus meeting the actual usage needs of the second object.

In this embodiment of the application, after determining the domain name configuration information and instance identifier corresponding to the second object, the second binding relationship can be determined accordingly.

For example, the second binding relationship can be represented as: (Str_A, Cloud_HostsID_A, example.com INA1.1.1.1, 0, -1); where "Str_A" represents the identifier of the second object A; "Cloud_HostsID_A" represents the instance identifier of the second object A; in "example.com 10IN A1.1.1.1", "example.com" represents the example domain name, "10" represents that if 101 resolutions to "example.com" are received, then 10 will return the IP address "1.1.1.1", "IN" represents that the fixed format of the record is the record type, that is, the type of feedback to the object that sent the domain name resolution request is the feedback IP address, and the example IP address corresponding to the example domain name "1.1.1.1", "0" represents the status information of whether the domain name configuration information is available, and "-1" represents whether the example domain name is in a locked state, that is, the domain name configuration information cannot be changed by other personnel except the person who configured it.

For example, referring to Figure 8, the database includes second binding relationship 1 corresponding to second object 1, second binding relationship 2 corresponding to second object 2, ..., and second binding relationship n3 corresponding to second object n3. Here, second binding relationship 1 is the relationship determined by binding domain name configuration information 1 and instance identifier 1; second binding relationship 2 is the relationship determined by binding domain name configuration information 2 and instance identifier 2; and second binding relationship n3 is the relationship determined by binding domain name configuration information n3 and instance identifier n3, where n3 is a positive integer greater than 1.

The above embodiment only uses one second object as an example. In practical applications, each second object can establish corresponding first and second binding relationships and store them in the database. The summary of the data corresponding to the aforementioned first and second binding relationships forms the mapping relationship between each domain name information and each IP address set in the database.

In this embodiment of the application, the first binding relationship and the second binding relationship can be stored in a table, for example, see Table 4, which is a complete storage illustration table in this application:

Table 4

As can be seen, in this embodiment of the application, an array consisting of the identifier of the second object, the interface address, the cloud hosts instance identifier, and the domain name configuration information can be formed into a table and stored in the database.

For example, referring to Figure 9, which is a schematic diagram of a complete database in an embodiment of this application, the complete database includes a first binding relationship 1 and a second binding relationship 1 corresponding to a second object 1, a first binding relationship 2 and a second binding relationship 2 corresponding to a second object 2, ..., and a first binding relationship n4 and a second binding relationship n4 corresponding to a second object n, where n4 is a positive integer greater than 1.

Referring to Figure 10, which is a system architecture diagram of domain name resolution shown in an embodiment of this application, when any object triggers a domain name resolution service request based on a terminal device using the corresponding internal network, the public network server can process the domain name resolution server requests sent by each object based on the terminal device and return the corresponding IP address to each object.

As can be seen, the embodiments of this application provide a new system architecture for resolving domain names. In this system architecture, instead of setting up separate domain name resolution servers for each internal network, the IP address corresponding to the domain name is determined based on the database of the public network server.

Specifically, the database corresponding to the public network server records at least one domain name and its associated IP address for each internal network established on the public network. Therefore, the public network server can perform domain name resolution based on the database and the domain names to obtain the IP address corresponding to the domain name. This effectively reduces network construction and maintenance costs, and also significantly improves the efficiency of domain name resolution. Furthermore, it enables comprehensive management of domain name resolution for multiple internal networks in a large-scale environment.

In this embodiment of the application, referring to Figure 11A, Figure 11A is a schematic flowchart of a domain name resolution method provided in this embodiment of the application. Specifically, the method can be executed by the aforementioned public network server, including the following steps:

Step 1101: Receive the domain name resolution request sent by the first object, which carries the target domain name information.

In this embodiment, the public network server can receive a domain name resolution request sent by a first object, wherein the domain name resolution request carries target domain name information. Specifically, the first object can be any object that has established a corresponding internal network on the public network. Furthermore, the domain name resolution request may also carry a corresponding interface address, wherein the interface address can be assigned by the public network server to the first object, or it can be an interface address assigned by the public network server to other second objects, and the first object can obtain the corresponding interface address.

Step 1102: Based on the target domain name information, search the database to see if there is a target IP address associated with the target domain name information. The database records at least one domain name and associated IP address corresponding to each internal network established in the public network.

Optionally, in this embodiment of the application, when the public network server determines that the database also records: each domain name configuration information includes at least one domain name information corresponding to the corresponding internal network, the IP address associated with each domain name information, and the information on availability status, after receiving the domain name resolution request sent by the first object, before executing step 1102, the public network server may further query the database to see if there is any domain name configuration information in an available state, and start executing step 1102 only after determining that there is any domain name configuration information in an available state.

For example, the database records: Domain configuration information 1 (including availability status information), Domain configuration information 2 (including availability status information), ..., Domain configuration information n5 (including availability status information). After receiving the domain name resolution request sent by the first object, the public network server can query the database for the specific status of the availability status information in Domain configuration information 1, Domain configuration information 2, ..., Domain configuration information n5. If it is determined that the value corresponding to the availability status information in Domain configuration information 2 is 0, it indicates that Domain configuration information 2 is in an available state. Then, the public network server can search the database to see if there is a target IP address associated with the target domain name information.

In other words, only when it is determined that the domain name configuration information exists in a usable state can the public server begin to search the database for a target IP address associated with the target domain name information. This method can determine that the domain name configuration information is usable, thereby enabling effective domain name resolution processing.

In this embodiment of the application, when performing step 1102, the public network server can search in the database for a target IP address associated with the target domain name information based on the target domain name information; wherein, the database can be a database created based on the method in Figure 3 above.

For example, the specific process by which a public server searches the database for a target IP address associated with the target domain name information can be as follows: based on the target interface address and the first binding relationship carried in the domain name resolution request, determine the target instance identifier associated with the target interface address; then, based on the target instance identifier, call the corresponding target domain name resolution instance to search the database for a target IP address associated with the target domain name information.

For example, referring to Figure 8, assuming that the target interface address carried in the domain name resolution request is interface address 1, and the first binding relationship is that interface address 1 is bound to instance identifier 1, then the public network server can determine that the target instance identifier associated with the target interface address is instance identifier 1. Then, based on the target instance identifier, i.e. instance identifier 1, it can call the target domain name resolution instance corresponding to instance identifier 1 and search for the target IP address associated with the target domain name information in the database.

Specifically, when the public server calls the target domain name resolution instance corresponding to instance identifier 1 and searches for the target IP address associated with the target domain name information in the database, the public server can determine the domain name configuration information corresponding to the target instance identifier associated with the target interface address based on the second binding relationship. Thus, the public server can determine the target IP address associated with the target domain name information based on the domain name configuration information and the target domain name information.

For example, the target instance identifier "Cloud_HostsID_2w" associated with the target interface address can be used to determine the target IP address as "11.123.13.46" based on the second binding relationship.

As can be seen, in this embodiment of the application, the target instance identifier associated with the target interface address can be determined based on the first binding relationship pre-stored in the database. Thus, the corresponding target domain name resolution instance can be called based on the target instance identifier, and the target IP address associated with the target domain name information can be searched in the database based on the second binding relationship.

On the other hand, in this embodiment of the application, when it is determined that there is no domain name configuration information in an available state, the public network server can forward the domain name resolution request to the domain name server associated with the target domain name information based on a preset forwarding strategy, so that the domain name server can recursively resolve the domain name resolution request based on the preset forwarding strategy, obtain another target IP address, and feed back the other target IP address to the first object; wherein, the domain name server is set in the public network.

Specifically, when the public server determines that there is no domain name configuration information in an available state, it can first forward the aforementioned domain name resolution request to the root name server, then receive the information of the top-level name server returned by the root server, and then send the aforementioned domain name resolution request to the top-level name server again, and receive the information of the authoritative name server returned by the top-level name server. Then, based on the information of the authoritative name server returned by the top-level name server, the public server sends the aforementioned domain name resolution request to the authoritative name server again. The authoritative name server receives the aforementioned domain name resolution request, performs the corresponding domain name resolution processing, and returns the resolved value.

If the public server determines that the obtained resolution value does not conform to the preset IP format, it can obtain a new resolution value again in the same way until another target IP address that conforms to the above preset IP format is found. Then the public server can return the obtained other target IP address to the first object.

For example, if the target domain name information is "sss.vvvv.com", the public server can send the target domain name information to the root name server, top-level name server, and authoritative name server associated with the domain name information until the public server determines that the resolution value returned by the authoritative name server conforms to the preset IP format. Thus, the public server can obtain "11.156.36.12" and return "11.156.36.12" to the first object.

As can be seen, in this embodiment of the application, when it is determined that there is no domain name configuration information in an available state on the public network server, the domain name resolution request can still be processed.

In other words, this application provides a method that can both enable custom domain name resolution for specific services on the public network and support recursive resolution services on the public network.

Step 1103: When it is determined that a target IP address exists, the target IP address is fed back to the first object.

In this embodiment of the application, when it is determined that the target IP address exists in the database corresponding to the public network server, the target IP address can be fed back to the first object.

In this embodiment, the public network server can receive a domain name resolution request sent by a first object. The domain name resolution request carries target domain name information. Since the database corresponding to the public network server records at least one domain name and associated IP address for each internal network established on the public network, the public network server can directly obtain the target IP address associated with the target domain name based on the target domain name information and the pre-defined domain name-IP address mapping relationship for each internal network in the database. It then returns the target IP address to the first object, eliminating the need to build domain name servers within each internal network. This reduces the construction and maintenance of domain name servers, effectively lowering network construction and operation costs. Furthermore, it significantly improves the resolution efficiency of the target domain name information. Moreover, since at least one domain name and associated IP address for each internal network are stored in the database, domain name resolution management in a large-scale environment can be achieved, improving the management effectiveness of domain name resolution.

Based on the above embodiments, in one possible implementation, the second object assigned to the interface address may assign its interface address to other objects, or the interface address of the second object may be stolen. If the above situation is discovered, it will cause the public network server to receive multiple domain name resolution requests in a short period of time, and the multiple domain name resolution requests are for the same domain name information. It can be seen that the public network server also needs to perform regular checks on the aforementioned situation.

Specifically, taking the first object mentioned above as an example, the public network server can count the cumulative number of other domain name resolution requests carrying the target domain name information received within a preset time period. If it is determined that the cumulative number of requests within the preset time period reaches a set threshold, a prompt message is sent to the first object. The prompt message is used to prompt the first object to perform a duplicate check on the interface address.

For example, referring to Figure 11B, during the period from 8:00 to 9:00, statistics are collected on domain name resolution requests carrying target domain name information. This results in a cumulative total of 50,000 domain name resolution requests carrying target domain name information during the period from 8:00 to 9:00. If the set threshold for the cumulative total during the period from 8:00 to 9:00 is determined to be 30,000, then it can be determined that the cumulative total during the period from 8:00 to 9:00 has reached the set threshold.

For example, referring to Figure 11C, when it is determined that the cumulative number of domain name resolution requests carrying target domain name information has reached a set threshold, a prompt message is sent to the first object, prompting the first object to perform a duplicate check on its corresponding interface address. The prompt message might be something like: "Prompt: The corresponding bound interface address has triggered duplicate domain name resolution requests. Please check carefully."

To better explain the embodiments of this application, the following uses the domain name resolution of a first object as an example to introduce a domain name resolution method provided by the embodiments of this application. This method is executed by a public network server and includes the following steps, as shown in Figure 12:

Step 1201: Receive the domain name resolution request sent by the first object, which carries the target domain name information.

For example, suppose a public server receives a domain name resolution request from a first object, containing the target domain name information "mmm.wosz.com" and an identifier corresponding to the first object. Based on this identifier, the public server can determine the target interface address corresponding to the first object, such as "1.2.3.4". Of course, the domain name resolution request can also include the target interface address, such as "1.2.3.4".

Step 1202: Query the database to see if there are any domain name configuration information that are available. The database records at least one domain name and associated IP address for each internal network that has been established on the public network. If yes, proceed to step 1203; otherwise, proceed to step 1206.

Specifically, the public server can check the configuration information of each domain name in the database to determine whether the configuration information of each domain name is in an available state, that is, to determine whether the configuration information of each domain name can be used, so as to avoid the target IP address obtained based on the domain name configuration information being unusable.

Step 1203: Based on the target interface address and the first binding relationship carried in the domain name resolution request, determine the target instance identifier associated with the target interface address.

For example, when the public server determines that there is a domain name configuration information that is available, it continues to use the above target interface address as "1.2.3.4", and then, based on the first binding relationship, determines the target instance identifier associated with the target interface address as "Cloud_HostsID_1".

Step 1204: Based on the target instance identifier, call the corresponding target domain name resolution instance to search the database for a target IP address associated with the target domain name information.

For example, once the public server determines that the target instance is identified as "Cloud_HostsID_1", it can access the target domain name resolution instance corresponding to "Cloud_HostsID_1", that is, the hosts file in the database corresponding to HostsID_1. Based on the hosts file, a second binding relationship can be determined, and then the target IP address can be found based on the second binding relationship. Specifically, the hosts file stores domain name configuration information, which includes at least the domain name information and the IP address corresponding to that domain name information.

For example, if a public server determines that the first domain name configuration information among the multiple domain name configuration information stored in the hosts file includes the domain name "mmm.wosz.com", then the IP address corresponding to "mmm.wosz.com" in the first domain name configuration information, namely "11.134.10.12", can be determined as the target IP address.

Step 1205: When it is determined that the target IP address exists in the database, the target IP address is fed back to the first object.

For example, when a public server finds the target IP address associated with "mmm.wosz.com" as "11.134.10.12" based on the second binding relationship, it can then send "11.134.10.12" back to the first object.

As can be seen, in this embodiment of the application, when the domain name information to be resolved is the domain name information included in the domain name configuration information in the database, it can be directly executed based on the aforementioned steps 1201-1205. Obviously, when the domain name information to be resolved is the domain name information pre-configured by the first object, that is, the domain name information that the internal network corresponding to the first object can resolve, it can be directly and quickly determined based on the information pre-stored in the database.

In addition, when the domain name information to be resolved is not the domain name information included in the domain name configuration information in the database, that is, when the domain name information requested by the first object is not the domain name information that can be resolved by the internal network, the following step 1206 can be executed.

Step 1206: Based on the preset forwarding strategy, forward the domain name resolution request to the domain name server associated with the target domain name information, so that the domain name server recursively resolves the domain name resolution request based on the preset forwarding strategy, obtains another target IP address, and feeds back the other target IP address to the first object.

Specific examples have been described in detail in the steps for determining another target IP address, and will not be repeated here.

As can be seen, the embodiments of this application provide a solution that can both enable customized domain name resolution for specific services on the public network and support recursive resolution on the public network, avoiding the need to build a domain name server on the internal network, and allowing users to set domain name configuration information based on their actual usage needs, thereby improving the user experience.

Based on the same inventive concept, this application also provides a domain name resolution device. As shown in Figure 13, which is a structural schematic diagram of the domain name resolution device 1300, it may include:

The receiving unit 1301 is used to receive a domain name resolution request sent by the first object, the domain name resolution request carrying target domain name information;

The processing unit 1302 is used to search in the database for a target IP address associated with the target domain name information based on the target domain name information. The database records at least one domain name and associated IP address for each internal network established in the public network.

Feedback unit 1303 is used to feed back the target IP address to the first object when it is determined that the target IP address exists in the database.

Optionally, before the receiving unit receives the domain name resolution request sent by the first object, the processing unit 1302 is further configured to:

Receive a relationship establishment request sent by a second object, wherein the second object has already requested to establish a corresponding internal network in the public network, and the second object and the first object are the same object or different objects;

Based on the relationship, a request is established, a corresponding interface address is assigned to the second object, and a corresponding domain name resolution instance is created for the second object, and a corresponding instance identifier is generated; wherein, the domain name resolution instance is used to resolve the domain name information corresponding to the internal network requested by the second object;

Associate and bind the interface address corresponding to the second object with the instance identifier to determine the first binding relationship, and store the first binding relationship in the database.

Optionally, after determining the first binding relationship, the processing unit 1302 is further configured to:

Receive domain name configuration information sent by the second object. The domain name configuration information includes at least one domain name information corresponding to the internal network and the IP address associated with each domain name information.

Associate and bind the instance identifier corresponding to the second object with the domain name configuration information to determine the second binding relationship, and store the second binding relationship in the database.

Optionally, when searching the database for a target IP address associated with the target domain name information based on the target domain name information, the processing unit 1302 is specifically used for:

Based on the target interface address and the first binding relationship carried in the domain name resolution request, determine the target instance identifier associated with the target interface address;

Based on the target instance identifier, the corresponding target domain name resolution instance is invoked to search the database for a target IP address associated with the target domain name information.

Optionally, the database may also record: each domain name configuration information includes at least one domain name information corresponding to the internal network, the IP address associated with each domain name information, and available status information;

Before searching the database for a target IP address associated with the target domain name information, the processing unit also performs the following:

Check the database to see if there is any domain name configuration information that is available.

Once it is determined that there is domain name configuration information that is in an available state, the database is searched to see if there is a target IP address associated with the target domain name information.

Optionally, after querying the database to see if there is any domain name configuration information in an available state, the processing unit 1302 is further used to:

When it is determined that there is no domain name configuration information in an available state, the domain name resolution request is forwarded to the domain name server associated with the target domain name information based on the preset forwarding policy, so that the domain name server recursively resolves the domain name resolution request based on the preset forwarding policy, obtains another target IP address, and feeds back the other target IP address to the first object;

The domain name server is set up on the public network.

Optionally, if based on the identifier of the terminal corresponding to the object carried in the domain name resolution request, it is determined that there are other objects using the same interface address as the first object, then after receiving the domain name resolution request, the processing unit 1302 is further configured to:

For a preset time period, count the cumulative number of other domain name resolution requests carrying the target domain name information received;

If the cumulative number of times corresponding to the preset time period is determined to reach the set threshold, a prompt message is sent to the first object. The prompt message is used to prompt the first object to perform a duplicate check on the interface address.

In the above implementation, the internal network avoids building its own domain name server and introduces a public network server, which enables both custom domain name resolution for specific services on the public network and supports recursive resolution on the public network, thereby reducing the operation and maintenance costs of the internal network.

For ease of description, the above sections are divided into modules (or units) according to their functions and described separately. Of course, in implementing this application, the functions of each module (or unit) can be implemented in one or more software or hardware components.

Having introduced the domain name resolution method and apparatus according to exemplary embodiments of this application, we will now introduce an electronic device according to another exemplary embodiment of this application.

Those skilled in the art will understand that various aspects of this application can be implemented as a system, method, or program product. Therefore, various aspects of this application can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, collectively referred to herein as a "circuit," "module," or "system."

Based on the same inventive concept as the above-described method embodiments, this application also provides an electronic device. In one embodiment, the electronic device can be a public network server, as shown in Figure 3. In this embodiment, the structure of the electronic device can be as shown in Figure 14. This application also provides an electronic device, as shown in Figure 14. The electronic device in this application includes at least one processor 1401, and a memory 1402 and a communication interface 1403 connected to at least one processor 1401. This application does not limit the specific connection medium between the processor 1401 and the memory 1402. Figure 14 shows an example of the connection between the processor 1401 and the memory 1402 via a bus 1400. The bus 1400 is represented by a thick line in Figure 14. The connection methods between other components are only for illustrative purposes and are not intended to be limiting. The bus 1400 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in Figure 14, but this does not mean that there is only one bus or one type of bus.

In this embodiment of the application, the memory 1402 stores instructions that can be executed by at least one processor 1401. By executing the instructions stored in the memory 1402, at least one processor 1401 can perform the steps included in the aforementioned domain name resolution method.

The processor 1401 is the control center of the electronic device. It can connect to various parts of the fault detection device through various interfaces and lines. By running or executing instructions stored in the memory 1402 and calling data stored in the memory 1402, it performs various functions of the electronic device and processes data. Optionally, the processor 1401 may include one or more processing units. The processor 1401 may integrate an application processor and a modem processor. The processor 1401 mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1401. In some embodiments, the processor 1401 and the memory 1402 may be implemented on the same chip; in some embodiments, they may also be implemented on separate chips.

Processor 1401 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

Memory 1402, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 1402 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic memory, magnetic disk, optical disk, etc. Memory 1402 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, memory 1402 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and/or data.

Communication interface 1403 is a transmission interface that can be used for communication. Data can be received or sent through communication interface 1403.

In addition, the electronic device also includes a basic input/output system (I/O system) 1404 that helps transmit information between various devices within the electronic device, and a large-capacity storage device 1408 for storing the operating system 1405, application programs 1406 and other program modules 1407.

The basic input/output system 1404 includes a display 1409 for displaying information and an input device 1410 for user input, such as a mouse or keyboard. Both the display 1409 and the input device 1410 are connected to the processor 1401 via the basic input/output system 1404 connected to the system bus 1400. The basic input/output system 1404 may also include an input/output controller for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input/output controller also provides output to a display screen, printer, or other types of output devices.

Specifically, mass storage device 1408 is connected to processor 1401 via a mass storage controller (not shown) connected to system bus 1400. Mass storage device 1408 and its associated computer-readable media provide non-volatile storage for the server package. That is, mass storage device 1408 may include computer-readable media (not shown) such as hard disk drives or CD-ROM drives.

According to various embodiments of this application, the electronic device can also be connected to a remote computer on a network such as the Internet. That is, the electronic device can be connected to the network 1411 through the communication interface 1403 connected to the system bus 1400, or the communication interface 1403 can be used to connect to other types of networks or remote computer systems (not shown).

In some possible implementations, various aspects of the domain name resolution method provided in this application can also be implemented in the form of a program product, which includes program code. When the program product is run on an electronic device, the program code is used to cause the electronic device to perform the steps in the domain name resolution method according to various exemplary embodiments of this application described above. For example, the electronic device can perform the steps shown in FIG11A.

The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

The program product of the embodiments of this application may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a computing device. However, the program product of this application is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with a command execution system, apparatus, or device.

A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. This propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with a command execution system, apparatus, or device.

The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, and conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims (13)

1. A domain name resolution method, characterized in that it is applied to a public network server, the method comprising: Receive a domain name resolution request sent by a first object, wherein the domain name resolution request carries target domain name information; Based on the target domain name information and the first binding relationship stored in the database, the database is searched to see if there is a target IP address associated with the target domain name information. The database records at least one domain name information and associated IP address corresponding to each internal network established in the public network. When it is determined that the target IP address exists in the database, the target IP address is fed back to the first object; The first binding relationship in the database is stored using the following method before receiving the domain name resolution request sent by the first object: Receive a relationship establishment request sent by a second object, wherein the second object has already requested to establish a corresponding internal network in the public network, and the second object and the first object are the same object or different objects; Based on the established association request, a corresponding interface address is assigned to the second object, and a corresponding domain name resolution instance is created for the second object, and a corresponding instance identifier is generated; wherein, the domain name resolution instance is used to resolve the domain name information corresponding to the internal network requested by the second object; Associate and bind the interface address corresponding to the second object with the instance identifier to determine the first binding relationship, and store the first binding relationship in the database. 2. The method as described in claim 1, characterized in that, after determining the first binding relationship, it further includes: Receive domain name configuration information sent by the second object, wherein the domain name configuration information includes at least one domain name information corresponding to the corresponding internal network and the IP address associated with each domain name information; Associate and bind the instance identifier corresponding to the second object with the domain name configuration information to determine the second binding relationship, and store the second binding relationship in the database. 3. The method as described in claim 1, characterized in that, based on the target domain name information and the first binding relationship stored in the database, searching the database for the existence of a target IP address associated with the target domain name information includes: Based on the target interface address carried in the domain name resolution request and the first binding relationship, determine the target instance identifier associated with the target interface address; Based on the target instance identifier, the corresponding target domain name resolution instance is invoked to search the database for a target IP address associated with the target domain name information. 4. The method according to any one of claims 1-3, wherein the database further records: each domain name configuration information includes at least one domain name information corresponding to the corresponding internal network, the IP address associated with each domain name information, and information on its availability status; After receiving the domain name resolution request sent by the first object, and before searching the database for a target IP address associated with the target domain name information, the method further includes: Query the database to see if there is any domain name configuration information that is available. When it is determined that there is domain name configuration information in an available state, the database is searched to see if there is a target IP address associated with the target domain name information. 5. The method as described in claim 4, wherein the method further comprises: When it is determined that there is no domain name configuration information in an available state, the domain name resolution request is forwarded to the domain name server associated with the target domain name information based on the preset forwarding policy, so that the domain name server recursively resolves the domain name resolution request based on the preset forwarding policy to obtain another target IP address, and feeds back the other target IP address to the first object; The domain name server is located on the public network. 6. The method as described in claim 1, characterized in that, after receiving the domain name resolution request, the method further includes: For a preset time period, the cumulative number of other domain name resolution requests carrying the target domain name information received is counted; If it is determined that the cumulative number of times corresponding to the preset time period reaches a set threshold, a prompt message is sent to the first object. The prompt message is used to prompt the first object to perform a duplicate check on the interface address. 7. A domain name resolution device, characterized in that it is applied to a public network server, the device comprising: A receiving unit is configured to receive a domain name resolution request sent by a first object, wherein the domain name resolution request carries target domain name information; The processing unit is used to search the database for a target IP address associated with the target domain name information based on the target domain name information and the first binding relationship stored in the database. The database records at least one domain name and associated IP address corresponding to each internal network established in the public network. A feedback unit is used to feed back the target IP address to the first object when it is determined that the target IP address exists in the database; Before the receiving unit receives the domain name resolution request sent by the first object, the processing unit is further configured to store the first binding relationship in the database by the following method: receiving a relationship establishment request sent by a second object, wherein the second object has already requested the establishment of a corresponding internal network in the public network, and the second object and the first object are the same object or different objects; based on the relationship establishment request, allocating a corresponding interface address for the second object, creating a corresponding domain name resolution instance for the second object, and generating a corresponding instance identifier; wherein the domain name resolution instance is used to resolve the domain name information corresponding to the internal network requested by the second object; associating and binding the interface address corresponding to the second object with the instance identifier to determine the first binding relationship, and storing the first binding relationship in the database. 8. The apparatus of claim 7, wherein after determining the first binding relationship, the processing unit is further configured to: Receive domain name configuration information sent by the second object, wherein the domain name configuration information includes at least one domain name information corresponding to the corresponding internal network and the IP address associated with each domain name information; Associate and bind the instance identifier corresponding to the second object with the domain name configuration information to determine the second binding relationship, and store the second binding relationship in the database. 9. The apparatus as described in claim 7, wherein when searching the database for a target IP address associated with the target domain name information based on the target domain name information and the first binding relationship stored in the database, the processing unit is specifically used for: Based on the target interface address carried in the domain name resolution request and the first binding relationship, determine the target instance identifier associated with the target interface address; Based on the target instance identifier, the corresponding target domain name resolution instance is invoked to search the database for a target IP address associated with the target domain name information. 10. The apparatus according to any one of claims 7-9, wherein the database further records: each domain name configuration information includes at least one domain name information corresponding to the corresponding internal network, the IP address associated with each domain name information, and information on its availability status; Before searching the database for a target IP address associated with the target domain name information, the processing unit is further configured to: Query the database to see if there is any domain name configuration information that is available. When it is determined that there is domain name configuration information in an available state, the database is searched to see if there is a target IP address associated with the target domain name information. 11. The apparatus of claim 10, wherein after querying the database to determine whether there is domain name configuration information in an available state, the processing unit is further configured to: When it is determined that there is no domain name configuration information in an available state, the domain name resolution request is forwarded to the domain name server associated with the target domain name information based on the preset forwarding policy, so that the domain name server recursively resolves the domain name resolution request based on the preset forwarding policy to obtain another target IP address, and feeds back the other target IP address to the first object; The domain name server is located on the public network. 12. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the program to implement the steps of the method according to any one of claims 1 to 6. 13. A computer-readable storage medium, characterized in that it includes program code, which, when the program product is run on an electronic device, causes the electronic device to perform the steps of any one of the methods of claims 1 to 6.