WO2025055509A1 - Domain name resolution data configuration method, domain name resolution method, and related apparatus - Google Patents

Abstract

Embodiments of the present invention provide a domain name resolution data configuration method, a domain name resolution method, and a related apparatus. In the domain name resolution data configuration method, a plurality of domain name spaces isolated from each other are obtained by division in a domain name resolution system, when a configuration request for configuring a certain domain name by a user is received, a target domain name space corresponding to a user identifier of the user is determined from among the plurality of domain name spaces, and when there is no conflict domain name resolution data in the target domain name space, domain name resolution data to be configured is stored in the target domain name space. In this way, the domain name resolution system can support the requirements of different users to configure a same domain name in different domain name spaces, the probability of presence of conflict domain name resolution data when a user configures domain name resolution data in a certain domain name space is also reduced, the convenience of the user in configuring the domain name resolution data is improved, and user experience can be improved.

Description

A method for configuring domain name resolution data, a domain name resolution method and related devices

This application claims the priority of the Chinese patent application filed with the China Patent Office on September 15, 2023, with application number 202311197280.5 and application name “A method for configuring domain name resolution data, a domain name resolution method and related devices”, the entire contents of which are incorporated by reference in this application.

Technical Field

The implementation methods in this specification relate to the field of computer application technology, specifically, to domain name resolution technology under the field of computer application technology, and more specifically, to a domain name resolution data configuration method, a domain name resolution method and related devices.

Background Art

IP address (Internet Protocol Address) is a unified address format. In the Internet, IP address is the logical address of Internet participants. Each Internet participant can access other Internet participants by accessing their IP addresses. However, IP addresses are usually composed of a string of numbers separated by dots, which is not convenient to remember and cannot display the names and properties of Internet participants. For this reason, people designed domain names (Domain Name) and used the Domain Name System (Domain Name System) to map domain names and IP addresses to each other, so that users can access the Internet more conveniently through domain names.

The domain name resolution system is a platform that provides domain name resolution management services. It can help users manage and configure domain name resolution data. Users can configure domain name resolution data in the domain name resolution system to establish a mapping relationship between domain names and IP addresses, improve the convenience of domain name resolution data configuration, and have important significance for improving user experience.

Summary of the invention

Multiple implementations in this specification provide a method for configuring domain name resolution data, a domain name resolution method, and related devices to achieve the purpose of improving the convenience of configuring domain name resolution data.

In a first aspect, an embodiment of the present specification provides a method for configuring domain name resolution data, which is applied to a domain name resolution system, wherein the domain name resolution system includes a plurality of domain name spaces isolated from each other, The domain name space is used to store domain name resolution data and provide domain name resolution services. The method for configuring the domain name resolution data includes:

In response to a configuration request carrying a user identifier and domain name resolution data to be configured, determining a target domain name space corresponding to the user identifier from a plurality of domain name spaces; the domain name resolution data to be configured includes a mapping relationship between a domain name and an IP address;

If there is no conflicting domain name resolution data in the target domain name space, storing the domain name resolution data to be configured in the target domain name space;

The conflicting domain name resolution data includes domain name resolution data having a domain name that is the same as the domain name in the domain name resolution data to be configured.

In a second aspect, an implementation of this specification provides a domain name resolution method, including:

Obtaining a resolution request carrying a domain name to be resolved and a domain name space identifier to be resolved; the domain name space identifier to be resolved is used to represent the domain name space to be resolved;

According to the resolution request, a domain name space to be resolved is determined in a plurality of domain name spaces isolated from each other in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services;

The resolution request is forwarded to the domain name space to be resolved, where the resolution request is used to instruct the domain name space to be resolved to return an IP address corresponding to the domain name to be resolved.

In a third aspect, an embodiment of the present specification provides a device for configuring domain name resolution data, which is applied to a domain name resolution system, wherein the domain name resolution system includes a plurality of domain name spaces isolated from each other, wherein the domain name spaces are used to store domain name resolution data and provide domain name resolution services, and the device for configuring domain name resolution data includes:

A space determination module, configured to determine a target domain name space corresponding to the user identifier among a plurality of domain name spaces in response to a configuration request carrying a user identifier and domain name resolution data to be configured; the domain name resolution data to be configured includes a mapping relationship between a domain name and an IP address;

A data storage module, configured to store the domain name resolution data to be configured in the target domain name space if there is no conflicting domain name resolution data in the target domain name space;

The conflicting domain name resolution data includes domain name resolution data having a domain name that is the same as the domain name in the domain name resolution data to be configured.

In a fourth aspect, an implementation of this specification provides a domain name resolution device, including:

A request acquisition module, used to acquire a resolution request carrying a domain name to be resolved and a domain name space identifier to be resolved; the domain name space identifier to be resolved is used to represent the domain name space to be resolved;

A resolution space module, used to determine a domain name space to be resolved from a plurality of domain name spaces isolated from each other in a domain name resolution system according to the resolution request; the domain name space is used to store domain name resolution data and provide domain name resolution services;

The request forwarding module is used to forward the resolution request to the domain name space to be resolved, and the resolution request is used to instruct the domain name space to be resolved to return the IP address corresponding to the domain name to be resolved.

In a fifth aspect, an embodiment of this specification provides an electronic device, including a processor and a memory;

Wherein, the memory is connected to the processor, and the memory is used to store a computer program;

The processor is used to implement the domain name resolution data configuration method or the domain name resolution method as described in any one of the above items by running the computer program stored in the memory.

In a sixth aspect, an embodiment of the present specification provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the domain name resolution data configuration method or domain name resolution method as described above is implemented.

In a seventh aspect, an embodiment of the present specification provides a computer program product or a computer program, wherein the computer program product includes a computer program, and the computer program is stored in a computer-readable storage medium; the processor of the computer device reads the computer program from the computer-readable storage medium, and the processor implements the above-mentioned domain name resolution data configuration method or domain name resolution method steps when executing the computer program.

The multiple implementations provided in this specification provide a method for configuring domain name resolution data, a domain name resolution method and related devices, wherein the method for configuring domain name resolution data divides a plurality of domain name spaces isolated from each other in the domain name resolution system, and upon receiving a configuration request from a user to configure a domain name, determines a target domain name space corresponding to the user identifier of the user in the plurality of domain name spaces, and when there is no conflicting domain name resolution data in the target domain name space, stores the domain name resolution data to be configured in the target domain name space. In this way, the domain name resolution system can support the needs of different users to configure the same domain name in different domain name spaces, and also reduces the probability of conflicting domain name resolution data appearing when the user configures the domain name resolution data in a certain domain name space, thereby improving the user's convenience in configuring the domain name resolution data and helping to improve the user's experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a schematic diagram of the structure of a domain name;

FIG2 is a schematic diagram of the DNS resolution process;

FIG3 is a feasible application scenario of a method for configuring domain name resolution data provided by an embodiment of this specification;

FIG4 is a schematic diagram of a structure of a domain name resolution system including multiple domain name spaces provided by one embodiment of the present specification;

FIG5 is a flow chart of a method for configuring domain name resolution data provided by one embodiment of the present specification;

FIG6 is a schematic diagram of a situation in which different users configure domain name resolution data for the same domain name in a domain name resolution system, provided by an embodiment of the present specification;

FIG. 7 is a flow chart of a method for configuring domain name resolution data provided in another embodiment of the present specification;

FIG8 is a schematic diagram of a process for obtaining a domain name space provided by one embodiment of the present specification;

FIG9 is a flowchart of a domain name resolution method provided by one embodiment of the present specification;

FIG10 is a schematic diagram of the structure of a device for configuring domain name resolution data provided by one embodiment of the present specification;

FIG11 is a schematic diagram of the structure of a domain name resolution device provided by one embodiment of the present specification;

FIG. 12 is a schematic diagram of the structure of an electronic device provided in accordance with an embodiment of the present specification.

DETAILED DESCRIPTION

Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this specification shall have the common meanings understood by persons with ordinary skills in the field to which this specification belongs. The words "first", "second" and similar words used in the embodiments of this specification do not indicate any order, quantity or importance, but are only used to avoid confusion of constituent elements.

Unless the context requires otherwise, throughout the specification, "plurality" means "at least two", and "including" is interpreted as an open, inclusive meaning, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "examples", "specific examples" or "some examples" are intended to indicate that a particular feature, structure, material or characteristic associated with the embodiment or example is included in at least one embodiment or example of the specification. The schematic representation of the above terms does not necessarily refer to the same embodiment or example.

The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification. All other embodiments obtained by ordinary technicians in this field based on the embodiments in this specification without creative work are within the scope of protection of this specification.

Overview

Referring to Figure 1, a domain name is essentially a path in a large inverse tree, which can also be called a domain namespace. A "domain" is a manageable division in a domain namespace. Syntactically, each domain name consists of a sequence of labels, and each label is separated by a dot (decimal point). A domain name can be divided into subdomains, and subdomains can be further divided into subdomains of subdomains, thus forming a first-level domain name, a primary domain name, a subdomain name, and so on.

For example, in Figure 1, ".com" is the first-level domain name, "xx.com" is the main domain name (also called a hosted first-level domain name), "yyy.xx.com" is a subdomain name (also called a hosted second-level domain name), and "www.yyy.xx.com" is a subdomain of the subdomain name (also called a hosted third-level domain name).

Corresponding to the domain name, the DNS system can also be a hierarchical structure, and the multiple DNS servers included in the DNS system can also be a corresponding hierarchical structure. With the domain name structure, a DNS server is also needed to resolve the domain name, and it needs to be resolved by DNS servers all over the world. The DNS server is actually a host with a domain name system installed. The domain name resolution process involves 4 DNS servers, which can be: Root DNS server (Root Nameserver), first-level domain name server (Tld Nameserver), authoritative domain name server (Authoritative Nameserver) and local domain name server (DNS Resolver or Local DNS).

Among them, the local domain name server can be used to respond to the resolution request from the client (Client), and finally track until the DNS server that obtains the resolution result. When the local domain name server cannot find the resolution result locally, it will query the root DNS server and obtain the IP address of the first-level domain name server. The authoritative domain name server is unique in a specific area and is responsible for maintaining the mapping relationship between domain names and IP addresses in the area. The first-level domain name server is responsible for managing the second-level domain names registered under the first-level domain name server.

Specifically, referring to Figure 2, the purpose of each DNS server is explained below using a DNS resolution process. The result of a DNS query is usually cached in the local domain name server. If there is a cache in the local domain name server, the local domain name server will directly return the resolution result to the cache. The following example outlines the 8 steps required for a DNS query when the local domain name server has no cache:

1. The user enters "example.com" in the web browser, and the local domain name server starts Perform a recursive query.

2. The local domain name server uses an iterative query method to query the root domain name server.

3. The root domain name server tells the local domain name server the IP address of the first-level domain name server (Top Level Domain, TLD.com) that should be queried next.

4. The local domain name server queries the first-level domain name server .com.

5. The primary domain name server .com tells the local domain name server to query the IP address of the authoritative domain name server for example.com in the next step.

6. The local domain name server sends a query to the authoritative domain name server for example.com.

7. The example.com authoritative domain name server tells the local domain name server the IP address of the host being queried.

8. The local domain name server finally responds to the web browser with the queried IP address.

Once the eight steps of the DNS query return the IP address for example.com, the browser can then make a request for the web page:

9. The browser sends an HTTP request to the IP address.

10. The web server at that IP returns the web page to be rendered in the browser.

The domain name resolution system may include a DNS server to provide users with DNS resolution services and configuration services for domain name resolution data (i.e., the mapping relationship between domain names and IP addresses). The DNS server included in the domain name resolution system may specifically be an authoritative domain name server. An authoritative domain name server usually only has complete information about a certain part of the domain name space, which we call a zone. The content of the zone may be loaded from a file or another authoritative domain name server. After loading, the authoritative domain name server may claim to have authority over the zone. An authoritative domain name server may have authority over multiple zones at the same time. In this specification, a domain name resolution system may refer to a system that provides domain name resolution services to users, that is, a domain name resolution system may respond to resolution requests and return a mapping relationship between domain names and IP addresses.

After a user purchases a domain name (for example, exampleA.com) on the domain name platform, the user can configure the authoritative domain name server domain name on the domain name platform. The authoritative domain name server domain name is used to represent the name of the authoritative domain name server that has the qualification to resolve the domain name. The domain name platform will send the authoritative domain name server domain name to the registry for registration. After that, the user can log in to the domain name resolution system to configure the correspondence between the domain name exampleA.com and the IP address. When other users access the domain name exampleA.com, the domain name resolution system will return the mapping relationship between exampleA.com and the IP address to the local domain name server, and the local domain name server will return the mapping relationship to the user's browser, ultimately enabling the user to access the domain name. IP address of access.

At present, the domain name resolution system does not support multiple users to configure domain name resolution data for the same domain name, which may reduce the user's configuration convenience. For example, in some cases, the following situation may occur: User A purchases and registers the domain name exampleB.com, and configures the mapping relationship between exampleB.com and IP address B in the domain name resolution system; afterwards, user B purchases the domain name exampleB.com from user A and registers it with the registry. However, when user B wants to configure the mapping relationship between exampleB.com and IP address C in the same domain name resolution system, since the domain name resolution system already has the mapping relationship between exampleB.com and IP address B, in order to avoid resolution anomalies and other problems, the domain name resolution system will reject user B's configuration request for the domain name resolution data of exampleB.com, or require user B to provide proof information of owning the domain name exampleB.com, which has a negative impact on user B's configuration convenience and is not conducive to providing user B with a good user experience.

In order to solve this problem, the inventor found through research that multiple domain name spaces isolated from each other can be divided in the domain name resolution system. When receiving a configuration request from a user to configure a domain name, the target domain name space corresponding to the user ID of the user is determined in multiple domain name spaces, and when there is no conflicting domain name resolution data in the target domain name space, the domain name resolution data to be configured is stored in the target domain name space. In this way, the domain name resolution system can support the needs of different users to configure the same domain name in different domain name spaces, and also reduce the probability of conflicting domain name resolution data when the user configures the domain name resolution data in a certain domain name space, improve the user's configuration convenience of the domain name resolution data, and help improve the user experience.

Based on the above concept, an embodiment of the present specification provides a method for configuring domain name resolution data, and the method for configuring domain name resolution data will be exemplarily described below in conjunction with the accompanying drawings.

Example scenarios

Refer to Figure 3, which is a feasible application scenario of the domain name resolution data configuration method. In Figure 3, a user (such as the domain name owner 11 in Figure 3) registers the domain name resolution data to the domain name resolution system 10. The domain name resolution system 10 responds to the resolution requests of other users (such as the visitor 12 in Figure 3) based on the resolution data, and returns the IP address mapped to the domain name in the resolution request to meet the access needs of other users.

The resolution request responded by the domain name resolution system can be sent directly by the user to the domain name resolution system or by the local domain name server, and this specification does not limit this.

In FIG3 , the domain name owner 11 and the visitor 12 can access the domain name resolution system through the client. In the system 10, the domain name resolution system may include multiple servers, and the multiple servers may include an authoritative domain name server. The client may be an electronic device with network access capability. Specifically, for example, the client may be a desktop computer, a tablet computer, a laptop computer, a smart phone, a digital assistant, a smart wearable device, etc. Among them, the smart wearable device includes but is not limited to a smart bracelet, a smart watch, a smart glasses, etc.

The server can be an electronic device with certain computing and processing capabilities. It can have a network communication module, a processor, a memory, etc. Of course, the server can also refer to software running in the electronic device. The server can also be a distributed server, which can be a system with multiple processors, memories, network communication modules, etc. working together. Alternatively, the server can also be a server cluster formed by several servers. Alternatively, with the development of science and technology, the server can also be a new technical means that can realize the corresponding functions of the implementation method of the specification. For example, it can be a new form of "server" based on quantum computing.

Exemplary Methods

Taking the domain name resolution system 10 applied to the application scenario shown in FIG. 3 as an example, as shown in FIG. 4 , the domain name resolution system includes a plurality of domain name spaces isolated from each other, the domain name spaces are used to store domain name resolution data and provide domain name resolution services. The embodiment of this specification provides a method for configuring domain name resolution data, as shown in FIG. 5 , the method for configuring domain name resolution data includes:

S501: In response to a configuration request carrying a user identifier and domain name resolution data to be configured, determine a target domain name space corresponding to the user identifier in a plurality of domain name spaces; the domain name resolution data includes a mapping relationship between a domain name and an IP address.

The user identifier may be a unique identifier of the user in the domain name resolution system, and the user identifier may be used to characterize the identity of the user in the domain name resolution system. In some feasible implementations, the user identifier may be, for example, a user name, a user ID, and the like.

The domain name resolution data to be configured includes the mapping relationship between the domain name that the user wants to configure and the IP address. In most cases, the user represented by the user identifier owns the domain name in the domain name resolution data to be configured. For example, user A purchased the domain name: exampleC.com, and wants to propose a mapping relationship between exampleC.com and the IP address 10.186.xxx.102. In this way, other users can access the IP address 10.186.xxx.102 by typing exampleC.com in the browser. In the process of establishing the mapping relationship, user A can send a configuration request carrying the mapping relationship between exampleC.com and the IP address 10.186.xxx.102 to the domain name resolution system, requesting the domain name resolution system to store the domain name to be configured. The domain name resolution data is set so that when the domain name resolution system receives a resolution request for exampleC.com, it can return the corresponding IP address to the requester.

A domain name space may be a plurality of independent spaces in a domain name resolution system, and users are isolated from each other. A domain name space may be used to store domain name resolution data and may provide domain name resolution services. In some embodiments, a domain name space may include one or more servers, which may specifically be authoritative domain name servers, and each authoritative domain name server stores information of at least part of a domain name space. Each domain name space may be used to store domain name resolution data configured by multiple users. Different domain name spaces may support configuration of domain name resolution data for the same domain name by different users. This enables the domain name resolution system to support the needs of different users to configure the same domain name in different domain name spaces, and also reduces the probability of conflicting domain name resolution data when a user configures domain name resolution data in a certain domain name space, thereby improving the convenience of configuring domain name resolution data for users and improving the user experience.

S502: If there is no conflicting domain name resolution data in the target domain name space, storing the domain name resolution data to be configured in the target domain name space;

The conflicting domain name resolution data includes domain name resolution data having a domain name that is the same as the domain name in the domain name resolution data to be configured.

When storing the configured domain name resolution data, it is only necessary to consider whether there is conflicting domain name resolution data in the target domain name space, which reduces the probability of conflicting domain name resolution data appearing when the user configures the domain name resolution data, improves the user's configuration convenience for the domain name resolution data, and is conducive to improving the user experience.

For example, referring to FIG6 , it is assumed that user A purchases domain name A, and configures the mapping relationship between domain name A and IP address A in the domain name space 255 of the domain name resolution system, and then registers the authoritative server of domain name A with the domain name registry as domain name space 255. In this case, when other users request resolution for domain name A, the primary domain name server will return domain name space 255 as the authoritative domain name server to the local domain name server of the user, and the local domain name server of the user will request domain name space 255 to return IP address A that has a mapping relationship with domain name A.

Afterwards, assuming that user B purchases domain name A from user A, user B will provide the registry with proof of ownership of domain name A, register the authoritative domain name server of domain name A as domain name space 0, and store the mapping relationship between domain name A and IP address B in domain name space 0 of the domain name resolution system. Since domain name space 0 and domain name space 255 are isolated from each other, the mapping relationship between domain name A and IP address B stored in domain name space 0 will not conflict with the mapping relationship between domain name A and IP address A stored in domain name space 255. And it will not affect other users' normal access to domain name A. Specifically, in this case, when other users request resolution for domain name A, since user B has registered the authoritative domain name server of domain name A as domain name space 0, the primary domain name server will return domain name space 0 as the authoritative domain name server to the user's local domain name server, and the user's local domain name server will request domain name space 0 to return IP address B that has a mapping relationship with domain name A.

In this way, different domain name spaces of the domain name resolution system can support the configuration requirements of domain name resolution data for the same domain name. When user B configures the domain name resolution data of domain name A in the domain name resolution system, he will not be required to provide proof information again due to the existing mapping relationship between domain name A and IP address A in the domain name resolution system. This reduces the probability of conflicting domain name resolution data when users configure domain name resolution data, improves the convenience of users' configuration of domain name resolution data, and is conducive to improving users' usage experience.

In order to solve the problem of configuring domain name resolution data when there is conflicting domain name resolution data, in some implementations, the method for configuring domain name resolution data further includes:

If the conflicting domain name resolution data exists in the target domain name space, an authentication prompt is issued; the authentication prompt is used to instruct the user to provide proof information of owning the domain name in the domain name resolution data to be configured.

In this embodiment, when there is conflicting domain name resolution data in the target domain name space, an authentication prompt can be issued to prompt the user to provide proof information of owning the domain name in the domain name resolution data to be configured, so that the domain name resolution system can decide how to handle the domain name resolution data to be configured based on the proof information.

After the user provides the proof information of owning the domain name, in some embodiments, the issuing of the authentication prompt further includes:

If the certification information is received, the domain name resolution data to be configured is used to overwrite the conflicting domain name resolution data in the target domain name space.

In this embodiment, it is assumed that the domain name resolution system has stored the mapping relationship between domain name D and IP address D in domain name space 1. Later, user E purchased domain name D, and user E's target domain name space is also domain name space 1, and wants to store the mapping relationship between domain name D and IP address E in domain name space 1. At this time, the mapping relationship between domain name D and IP address D in domain name space 1 is the conflicting domain name resolution data to be configured submitted by user E to the domain name resolution system. The domain name resolution system can send an authentication prompt to user E, instructing user E to provide proof information of owning domain name D. If user E provides the proof information, the domain name resolution system can consider user E to be the current legal owner of domain name D. Alternatively, the mapping relationship between domain name D and IP address E can be used to overwrite the original mapping relationship between domain name D and IP address D. In this way, when conflicting domain name resolution data exists in a domain name space, the user who currently owns the domain name can normally configure the domain name resolution data of the domain name.

In some implementations, the method for configuring domain name resolution data further includes:

If a configuration conflict event occurs a preset number of times in a configuration request carrying the same user identifier, a domain name space is reallocated to the user identifier as a target domain name space for the user identifier; the preset number of times is greater than or equal to 1;

The configuration conflict event includes: conflicting domain name resolution data exists in the target domain name space.

In this embodiment, in a domain name space, if a configuration request submitted by the same user has a preset number of configuration conflict events, the target domain name space can be changed for the user to avoid frequent configuration conflicts in the configuration requests submitted by the user, which is conducive to improving the user experience.

For example, assuming that the target domain name space of user F and user G are both domain name space 3, and user F has purchased a large number of different domain names from user G, in this case, when user F wants to configure the domain name resolution data of these domain names in domain name space 3, configuration conflict events will frequently occur. In order to solve this problem, after a preset number of configuration conflict events occur in the configuration request submitted by user F, the target domain name space corresponding to the user identifier corresponding to user F can be replaced with domain name space 5. In this way, the probability of configuration conflict events occurring when user F configures domain name resolution data in the target domain name space can be reduced, which is conducive to improving user experience.

In some implementations, when the target domain name space is changed for a certain user, the domain name resolution data configured by the user in the original target domain name space can be transferred to the new target domain name space, eliminating the need for the user to repeatedly configure the domain name resolution data, thereby improving user experience.

Some users have a large number of domain names, and a separate domain name space can be set for them to ensure that these users can configure domain name resolution data smoothly. For example, in some implementations, the multiple domain name spaces include shared spaces and exclusive spaces; the shared space corresponds to multiple user identifiers, and the exclusive space corresponds to one user identifier;

After determining the target domain name space corresponding to the user identifier among the multiple domain name spaces, the method further includes:

If the target domain name space is the shared space, then enter the process of: if there is no conflicting domain name resolution data in the target domain name space, then store the domain name resolution data to be configured in the target domain name space; Steps of space;

If the target domain name space is the exclusive space, the domain name resolution data carried in the configuration request is stored in the exclusive space.

In this embodiment, the shared space is used to correspond to multiple user identifiers, that is, users corresponding to multiple user identifiers share the same domain name space. The exclusive space is used to correspond to one user identifier, that is, the exclusive space is only used for one user to configure domain name resolution data. In this way, multiple users will not configure domain name resolution data for the same domain name in the exclusive space. Exclusive space can be allocated to users with a large number of domain names, avoiding configuration conflicts that may occur when such users frequently configure domain name resolution data, thereby improving user experience.

In order to ensure high availability of the domain name space, in some implementations, as shown in FIG8 , the process of obtaining the multiple domain name spaces includes:

Get multiple name server domain names;

Dividing the plurality of name server domain names into a plurality of domain name combinations, each of the domain name combinations including at least one of the name server domain names;

The domain name combination is matched with the domain name space, and the name server domain name in the domain name combination is used to represent the name of the domain name space.

The name server domain name is used to represent the name of the domain name space. The primary domain name server can send the name server domain name to the local domain name server so that the local domain name server can find the domain name space represented by the name server domain name according to the name server domain name.

Multiple name server domain names can be obtained by registering with a registry. For example, in FIG8 , 1,000 name server domain names such as ns1.cn, ns2.cn, ... ns256.cn, ns1.com, ... ns256.com are pre-registered. Then, they are divided into 256 domain name combinations (domain name combinations 1 to 256) in groups of four. The name server domain name in each domain name combination is used to represent a domain name space. For example, the name server domain names ns1.cn, ns1.com, ns1.org, and ns1.net in domain name combination 1 can all be used to represent domain name space 0. The local domain name server can find domain name space 0 through ns1.cn, ns1.com, ns1.org, or ns1.net. In this way, when a first-level domain name server (for example, a .com first-level domain name server) fails, ns1.cn, ns1.org, or ns1.net can be returned through other first-level domain name servers (for example, a .cn first-level domain name server, a .org first-level domain name server, or a .net first-level domain name server), so that the local domain name server can normally find domain name space 0, thereby ensuring the high availability of the domain name space.

Accordingly, an embodiment of the present specification further provides a domain name resolution method, as shown in FIG9 , including:

S901: Obtain a resolution request carrying a domain name to be resolved and a domain name space identifier to be resolved; the domain name space identifier to be resolved is used to represent the domain name space to be resolved;

S902: According to the resolution request, determine a domain name space to be resolved from a plurality of domain name spaces isolated from each other in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services;

S903: Forward the resolution request to the domain name space to be resolved, where the resolution request is used to instruct the domain name space to be resolved to return an IP address corresponding to the domain name to be resolved.

The resolution request may be sent by the local domain name server. The domain name space identifier to be resolved carried in the resolution request may be sent by the primary domain name server to the local domain name server, or may be cached in the local domain name server. This specification does not limit this.

Optionally, the domain name space corresponds to a domain name combination, the domain name combination includes at least one name server domain name; the name server domain name in the domain name combination is used to represent the name of the domain name space; the domain name space identifier to be resolved includes a target name server domain name;

Determining, according to the resolution request, a domain name space to be resolved from the multiple domain name spaces comprises:

Among the multiple domain name spaces, the domain name space corresponding to the target domain name combination is determined as the domain name space to be resolved; the target domain name combination includes the target name server domain name.

The relevant limitations of the domain name space in the domain name resolution method can be referred to the relevant description above, and this manual will not elaborate on it here.

Exemplary Devices

Some embodiments of the present specification also provide a device for configuring domain name resolution data, as shown in FIG10, which is applied to a domain name resolution system, the domain name resolution system includes a plurality of domain name spaces isolated from each other, the domain name spaces are used to store domain name resolution data and provide domain name resolution services, and the device for configuring domain name resolution data includes:

The space determination module 1001 is used to respond to a configuration request carrying a user identifier and domain name resolution data to be configured, and determine a target domain name space corresponding to the user identifier among multiple domain name spaces; the domain name resolution data to be configured includes a mapping relationship between a domain name and an IP address;

The data storage module 1002 is used to store the domain name resolution data to be configured in the target domain name space if there is no conflicting domain name resolution data in the target domain name space;

The conflicting domain name resolution data includes domain name resolution data having a domain name that is the same as the domain name in the domain name resolution data to be configured.

In some embodiments, the data storage module is further used to: issue an authentication prompt if the conflicting domain name resolution data exists in the target domain name space; the authentication prompt is used to instruct the user to provide proof information of owning the domain name in the domain name resolution data to be configured.

In some implementations, after issuing the authentication prompt, the data storage module is further used to: if the certification information is received, overwrite the conflicting domain name resolution data in the target domain name space with the domain name resolution data to be configured.

In some implementations, the device for configuring domain name resolution data further includes:

a conflict resolution module, configured to reallocate a domain name space for the user identifier as a target domain name space for the user identifier if a configuration conflict event occurs a preset number of times in a configuration request carrying the same user identifier; the preset number of times is greater than or equal to 1;

The configuration conflict event includes: conflicting domain name resolution data exists in the target domain name space.

In some implementations, the multiple domain name spaces include a shared space and an exclusive space; the shared space corresponds to multiple user identifiers, and the exclusive space corresponds to one user identifier;

The configuration device of the domain name resolution data also includes:

A space determination module, configured to trigger the data storage module if the target domain name space is the shared space and if there is no conflicting domain name resolution data in the target domain name space;

If the target domain name space is the exclusive space, the domain name resolution data carried in the configuration request is stored in the exclusive space.

In some implementations, the process of acquiring the multiple domain name spaces includes:

Get multiple name server domain names;

Dividing the plurality of name server domain names into a plurality of domain name combinations, each of the domain name combinations including at least one of the name server domain names;

The domain name combination is matched with the domain name space, and the name server domain name in the domain name combination is used to represent the name of the domain name space.

Some implementations of this specification also provide a domain name resolution device, as shown in FIG11 , including:

Request acquisition module 1101, used to obtain the domain name to be resolved and the domain name space identifier to be resolved The to-be-resolved domain name space identifier is used to represent the to-be-resolved domain name space;

A resolution space module 1102 is used to determine a domain name space to be resolved from a plurality of domain name spaces isolated from each other in a domain name resolution system according to the resolution request; the domain name space is used to store domain name resolution data and provide domain name resolution services;

The request forwarding module 1103 is used to forward the resolution request to the domain name space to be resolved, and the resolution request is used to instruct the domain name space to be resolved to return the IP address corresponding to the domain name to be resolved.

In some embodiments, the domain name space corresponds to a domain name combination, the domain name combination includes at least one name server domain name; the name server domain name in the domain name combination is used to represent the name of the domain name space; the domain name space identifier to be resolved includes a target name server domain name;

The resolution space module determines, according to the resolution request, among the multiple domain name spaces, that the domain name space to be resolved is specifically used for:

Among the multiple domain name spaces, the domain name space corresponding to the target domain name combination is determined as the domain name space to be resolved; the target domain name combination includes the target name server domain name.

The domain name resolution data configuration device or domain name resolution device provided in the embodiments of this specification belongs to the same inventive concept as the domain name resolution data configuration method or domain name resolution method provided in the above embodiments of this specification. For technical details not fully described in this embodiment, please refer to the specific processing content of the domain name resolution data configuration method or domain name resolution method provided in the above embodiments of this specification, and will not be repeated here.

Exemplary Electronic Devices

Another embodiment of the present application further proposes an electronic device, as shown in Figure 12. An exemplary embodiment of the present specification also provides an electronic device, including: a memory and a processor, the memory storing a computer program, and the processor executing the computer program when executing the computer program performs the configuration method of domain name resolution data or the steps in the domain name resolution method according to various embodiments of the present specification described in the above embodiments of the present specification.

The internal structure of the electronic device may be as shown in FIG12 , and the electronic device includes a processor, a memory, a network interface, and an input device connected via a system bus. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the steps of the domain name resolution data configuration method or domain name resolution method according to various embodiments of the present specification are described in the above embodiments of the present specification.

The processor may include a main processor, and may also include a baseband chip, a modem, etc.

The memory stores a computer program for executing the technical solution of the present invention, and may also store an operating system and other key programs. Specifically, the computer program may include a program code, and the program code includes computer operation instructions. More specifically, the memory may include a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM), other types of dynamic storage devices that can store information and instructions, a disk storage, a flash, and the like.

The processor may be a general-purpose processor, such as a general-purpose processor (CPU), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the scheme of the present invention. It may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

The input device may include a device for receiving data and information input by a user, such as a keyboard, a mouse, a camera, a scanner, a light pen, a voice input device, a touch screen, a pedometer, or a gravity sensor.

Output devices may include means that allow information to be output to a user, such as display screens, printers, speakers, etc.

The communication interface may include using any transceiver or the like to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

The processor executes the computer program stored in the memory and calls other devices, which can be used to implement any one of the domain name resolution data configuration methods or various steps of the domain name resolution method provided in the above embodiments of the present application.

The electronic device may also include a display component and a voice component. The display component may be a liquid crystal display or an electronic ink display. The input device of the electronic device may be a touch layer covering the display component, or a button, trackball or touchpad provided on the housing of the electronic device, or an external keyboard, touchpad or mouse.

Those skilled in the art will appreciate that the structure shown in FIG. 12 is merely a block diagram of a portion of the structure related to the solution of this specification, and does not constitute a limitation on the electronic device to which the solution of this specification is applied. A specific electronic device may include more or fewer components than those shown in the figure, or a combination of components. certain components, or have a different arrangement of components.

Exemplary computer program products and computer-readable storage media

In addition to the above-mentioned methods and devices, the domain name resolution data configuration method or domain name resolution method provided in the embodiments of this specification may also be a computer program product, which includes a computer program, which, when executed by a processor, enables the processor to execute the steps of the domain name resolution data configuration method or domain name resolution method according to various embodiments of this specification described in the above "Exemplary Method" section of this specification.

The computer program product may be written in any combination of one or more programming languages to write program code for performing the operations of the embodiments of the present specification, including object-oriented programming languages such as Java, C++, etc., and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

In addition, an embodiment of the present specification also provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor to perform the steps in the domain name resolution data configuration method or the domain name resolution method according to various embodiments of the present specification described in the above "Exemplary Method" section of the present specification.

It should be understood that the specific examples in this article are only intended to help those skilled in the art better understand the implementation methods of this specification, rather than to limit the scope of this specification.

It can be understood that in the various implementations of this specification, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the implementation methods of this specification.

It can be understood that the various embodiments described in this specification can be implemented individually or in combination, and the embodiments of this specification are not limited to this.

Unless otherwise specified, all technical and scientific terms used in the embodiments of this specification have the same meanings as those commonly understood by those skilled in the art in the technical field of this specification. The terms used in this specification are only for the purpose of describing specific embodiments and are not intended to limit the scope of this specification. The term "and/or" used in this specification includes any and all of the related listed items. As used in the embodiments of the present specification and the appended claims, the singular forms "a", "an", "above", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It can be understood that the processor of the embodiment of this specification can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method implementation can be completed by the hardware integrated logic circuit in the processor or the instruction in the form of software. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiment of this specification can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of this specification can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor can be executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It is understood that the memory in the embodiments of this specification may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this specification.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method implementation methods and will not be repeated here.

In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

In addition, each functional unit in each embodiment of the present specification may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this specification, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of this specification. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

The above is only a specific implementation of this specification, but the protection scope of this specification is not limited to this. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in this specification, which should be included in the protection scope of this specification. Therefore, the protection scope of this specification should be based on the protection scope of the claims.

Claims (12)

A method for configuring domain name resolution data, characterized in that it is applied to a domain name resolution system, the domain name resolution system includes a plurality of domain name spaces isolated from each other, the domain name spaces are used to store domain name resolution data and provide domain name resolution services, and the method for configuring domain name resolution data includes: In response to a configuration request carrying a user identifier and domain name resolution data to be configured, determining a target domain name space corresponding to the user identifier from a plurality of domain name spaces; the domain name resolution data to be configured includes a mapping relationship between a domain name and an IP address; If there is no conflicting domain name resolution data in the target domain name space, storing the domain name resolution data to be configured in the target domain name space; The conflicting domain name resolution data includes domain name resolution data having a domain name that is the same as the domain name in the domain name resolution data to be configured. The method according to claim 1, further comprising: If the conflicting domain name resolution data exists in the target domain name space, an authentication prompt is issued; the authentication prompt is used to instruct the user to provide proof information of owning the domain name in the domain name resolution data to be configured. The method according to claim 2, characterized in that after issuing the authentication prompt, the method further comprises: If the certification information is received, the domain name resolution data to be configured is used to overwrite the conflicting domain name resolution data in the target domain name space. The method according to claim 1, further comprising: If a configuration conflict event occurs a preset number of times in a configuration request carrying the same user identifier, a domain name space is reallocated to the user identifier as a target domain name space for the user identifier; the preset number of times is greater than or equal to 1; The configuration conflict event includes: conflicting domain name resolution data exists in the target domain name space. The method according to claim 1 is characterized in that the multiple domain name spaces include a shared space and an exclusive space; the shared space corresponds to multiple user identifiers, and the exclusive space corresponds to one user identifier; The target domain name space corresponding to the user identifier is determined in the multiple domain name spaces. After that, it also includes: If the target domain name space is the shared space, then the step of storing the domain name resolution data to be configured in the target domain name space if there is no conflicting domain name resolution data in the target domain name space is entered; If the target domain name space is the exclusive space, the domain name resolution data carried in the configuration request is stored in the exclusive space. The method according to any one of claims 1 to 5, characterized in that the process of acquiring the multiple domain name spaces comprises: Get multiple name server domain names; Dividing the plurality of name server domain names into a plurality of domain name combinations, each of the domain name combinations including at least one of the name server domain names; The domain name combination is matched with the domain name space, and the name server domain name in the domain name combination is used to represent the name of the domain name space. A domain name resolution method, characterized by comprising: Obtaining a resolution request carrying a domain name to be resolved and a domain name space identifier to be resolved; the domain name space identifier to be resolved is used to represent the domain name space to be resolved; According to the resolution request, a domain name space to be resolved is determined in a plurality of domain name spaces isolated from each other in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services; The resolution request is forwarded to the domain name space to be resolved, where the resolution request is used to instruct the domain name space to be resolved to return an IP address corresponding to the domain name to be resolved. The method according to claim 7 is characterized in that the domain name space corresponds to a domain name combination, the domain name combination includes at least one name server domain name; the name server domain name in the domain name combination is used to represent the name of the domain name space; the domain name space identifier to be resolved includes a target name server domain name; Determining, according to the resolution request, a domain name space to be resolved from the multiple domain name spaces comprises: Among the multiple domain name spaces, the domain name space corresponding to the target domain name combination is determined as the domain name space to be resolved; the target domain name combination includes the target name server domain name. A configuration device for domain name resolution data, characterized in that it is applied to a domain name resolution system The domain name resolution system includes a plurality of domain name spaces isolated from each other, the domain name spaces are used to store domain name resolution data and provide domain name resolution services, and the configuration device of the domain name resolution data includes: A space determination module, configured to determine a target domain name space corresponding to the user identifier among a plurality of domain name spaces in response to a configuration request carrying a user identifier and domain name resolution data to be configured; the domain name resolution data to be configured includes a mapping relationship between a domain name and an IP address; A data storage module, configured to store the domain name resolution data to be configured in the target domain name space if there is no conflicting domain name resolution data in the target domain name space; The conflicting domain name resolution data includes domain name resolution data having a domain name that is the same as the domain name in the domain name resolution data to be configured. A domain name resolution device, comprising: A request acquisition module, used to acquire a resolution request carrying a domain name to be resolved and a domain name space identifier to be resolved; the domain name space identifier to be resolved is used to represent the domain name space to be resolved; A resolution space module, used to determine a domain name space to be resolved from a plurality of domain name spaces isolated from each other in a domain name resolution system according to the resolution request; the domain name space is used to store domain name resolution data and provide domain name resolution services; The request forwarding module is used to forward the resolution request to the domain name space to be resolved, and the resolution request is used to instruct the domain name space to be resolved to return the IP address corresponding to the domain name to be resolved. An electronic device, characterized in that it comprises: a processor and a memory; Wherein, the memory is connected to the processor, and the memory is used to store a computer program; The processor is used to implement the domain name resolution data configuration method according to any one of claims 1 to 6 or the domain name resolution method according to claim 7 or 8 by running the computer program stored in the memory. A computer program product, characterized in that it comprises: a computer program, the program being stored in a computer-readable storage medium; a processor of the computer device reading the computer program from the computer-readable storage medium, and the processor implementing the method for configuring domain name resolution data as described in any one of claims 1 to 6 or the steps of the domain name resolution method as described in claim 7 or 8 when executing the computer program.