Domain name resolution data configuration method, domain name resolution method, and related apparatus

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

[0001] This application claims priority to 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 into this application. Technical Field

[0002] The embodiments 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

[0003] An IP address (Internet Protocol Address) is a unified address format. On the Internet, an IP address is the logical address of an Internet participant. Each Internet participant can access other Internet participants by accessing their IP addresses. However, IP addresses typically consist of a string of numbers separated by dots, making them difficult to remember and unable to reveal the names and nature of Internet participants. To address this, domain names were designed and the Domain Name System (DNS) was used to map domain names to IP addresses, making it easier for users to access the Internet through domain names.

[0004] The Domain Name Resolution System (DNS) is a platform that provides domain name resolution management services. It helps users manage and configure domain name resolution data. By configuring domain name resolution data in the DNS, users can establish a mapping between domain names and IP addresses, making it easier to configure DNS data and significantly improving the user experience.

[0005] Summary of the Invention

[0006] Multiple embodiments 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.

[0007] In a first aspect, one embodiment of this specification provides a method for configuring domain name resolution data, which is applied to a domain name resolution system. The domain name resolution system includes multiple isolated domain name spaces, each of which is used to store domain name resolution data and provide domain name resolution services. The method for configuring domain name resolution data includes:

[0008] 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;

[0009] 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;

[0010] The conflicting domain name resolution data includes domain name resolution data having a domain name identical to the domain name in the domain name resolution data to be configured.

[0011] In a second aspect, an embodiment of this specification provides a domain name resolution method, including:

[0012] 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;

[0013] Determining, based on the resolution request, a domain name space to be resolved from a plurality of mutually isolated domain name spaces in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services;

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

[0015] In a third aspect, one embodiment of the present specification provides a device for configuring domain name resolution data, which is applied to a domain name resolution system. The domain name resolution system includes multiple isolated domain name spaces, each of which is used to store domain name resolution data and provide domain name resolution services. The device for configuring domain name resolution data includes:

[0016] a space determination module, configured to determine, in response to a configuration request carrying a user identifier and domain name resolution data to be configured, 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;

[0017] a data storage module, configured to store the to-be-configured domain name resolution data in the target domain name space if no conflicting domain name resolution data exists in the target domain name space;

[0018] The conflicting domain name resolution data includes domain name resolution data having a domain name identical to the domain name in the domain name resolution data to be configured.

[0019] In a fourth aspect, an embodiment of this specification provides a domain name resolution device, including:

[0020] A request acquisition module, configured 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;

[0021] A resolution space module, configured to determine, based on the resolution request, a domain name space to be resolved from a plurality of mutually isolated domain name spaces in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services;

[0022] The request forwarding module is used to 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 the IP address corresponding to the domain name to be resolved.

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

[0024] The memory is connected to the processor, and is used to store computer programs;

[0025] The processor is configured to implement any of the above-mentioned methods for configuring domain name resolution data or any of the above-mentioned methods for domain name resolution by running the computer program stored in the memory.

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

[0027] 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 when the processor executes the computer program, the above-mentioned domain name resolution data configuration method or domain name resolution method steps are implemented.

[0028] 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 mutually isolated domain name spaces in a domain name resolution system. When a configuration request for a domain name is received from a user, a target domain name space corresponding to the user identifier of the user is determined in the plurality of domain name spaces, and when no conflicting domain name resolution data exists 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 domain name resolution data in a certain domain name space, thereby improving the user's convenience in configuring domain name resolution data and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0030] FIG2 is a schematic diagram of the DNS resolution process;

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

[0032] 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;

[0033] FIG5 is a flow chart of a method for configuring domain name resolution data provided in one embodiment of this specification;

[0034] 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 according to an embodiment of the present specification;

[0035] FIG7 is a flowchart of a method for configuring domain name resolution data provided in another embodiment of this specification;

[0036] FIG8 is a schematic diagram of a process for obtaining a domain name space according to one embodiment of this specification;

[0037] FIG9 is a flowchart of a domain name resolution method provided in accordance with one embodiment of the present disclosure;

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

[0039] FIG11 is a schematic diagram of the structure of a domain name resolution device provided in one embodiment of this specification;

[0040] FIG12 is a schematic structural diagram of an electronic device provided in accordance with one embodiment of this specification. DETAILED DESCRIPTION

[0041] Unless otherwise defined, technical or scientific terms used in the embodiments of this specification should have the same ordinary meaning as those understood by persons of ordinary skill in the art to which this specification pertains. The terms "first," "second," and similar terms used in the embodiments of this specification do not denote any order, quantity, or importance, but are provided solely to avoid confusion between constituent elements.

[0042] Unless the context requires otherwise, throughout this specification, the term "plurality" means "at least two," and "including" is to be interpreted as open and inclusive, meaning "including, but not limited to." Throughout this specification, the terms "one embodiment," "some embodiments," "exemplary embodiments," "example," "specific example," 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 this specification. The schematic representations of these terms do not necessarily refer to the same embodiment or example.

[0043] 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 embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this specification.

[0044] Overview

[0045] 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 within the domain namespace. Syntactically, each domain name consists of a sequence of labels separated by periods (decimal points). Domain names can be divided into subdomains, which can be further divided into subdomains of subdomains, thus forming top-level domains, primary domains, and subdomains.

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

[0047] 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 have a corresponding hierarchical structure. With the domain name structure, DNS servers are also needed to resolve domain names, and these resolutions need to be performed by DNS servers all over the world. The DNS server is actually the host computer equipped with the domain name system. The domain name resolution process involves four DNS servers, which can be: the root DNS server (Root Nameserver), the first-level domain name server (Tld Nameserver), the authoritative domain name server (Authoritative Nameserver) and the local domain name server (DNS Resolver or Local DNS).

[0048] The local domain name server responds to resolution requests from clients and ultimately tracks the DNS server that retrieves the resolution result. If the local domain name server cannot find the resolution result locally, it queries the root DNS server and obtains the IP address of the first-level domain name server. The authoritative domain name server is unique within a specific region and is responsible for maintaining the mapping between domain names and IP addresses within that region. The first-level domain name server manages the second-level domain names registered under that first-level domain name server.

[0049] Specifically, referring to Figure 2, the following uses a DNS resolution process to illustrate the purpose of each DNS server. The results of a DNS query are usually cached in the local domain name server. If the local domain name server has a cache, the local domain name server will directly return the cached resolution result. The following example outlines the eight steps required for a DNS query when the local domain name server does not have a cache:

[0050] 1. The user enters "example.com" in the web browser, and the local domain name server begins a recursive query.

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

[0052] 3. The root domain name server tells the local domain name server the IP address of the top level domain (TLD).com) that should be queried next.

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

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

[0055] 6. The local name server sends a query to the authoritative name server for example.com.

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

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

[0058] 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:

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

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

[0061] 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. This part is called a zone. The content of the zone can be loaded from a file or another authoritative domain name server. After loading, the authoritative domain name server can claim to have authority over the zone. An authoritative domain name server can 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 can respond to resolution requests and return the mapping relationship between domain names and IP addresses.

[0062] After a user purchases a domain name (for example, exampleA.com) on a domain name platform, they can configure the authoritative domain name server domain name on the domain name platform. This authoritative domain name server domain name represents the name of the authoritative domain name server that is qualified to resolve the domain name. The domain name platform will send this 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 mapping 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 between exampleA.com and the IP address to the local domain name server. The local domain name server will return this mapping to the user's browser, ultimately enabling the user to access the IP address.

[0063] Currently, the domain name resolution system does not support multiple users configuring domain name resolution data for the same domain name, which may reduce user 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 between exampleB.com and IP address B in the domain name resolution system. Later, 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 between exampleB.com and IP address C in the same domain name resolution system, because the domain name resolution system already has a mapping between exampleB.com and IP address B, to avoid resolution anomalies and other issues, the domain name resolution system will reject User B's request to configure domain name resolution data for exampleB.com, or require User B to provide proof of ownership of the domain name exampleB.com. This has a negative impact on User B's configuration convenience and is not conducive to providing User B with a good user experience.

[0064] To address this issue, the inventors discovered through research that a domain name resolution system can be divided into multiple, isolated domain name spaces. Upon receiving a configuration request from a user for a domain name, the system determines the target domain name space corresponding to the user's user ID from among the multiple domain name spaces. If no conflicting domain name resolution data exists in the target domain name space, the domain name resolution data to be configured is stored in the target domain name space. This allows the domain name resolution system to support different users configuring the same domain name in different domain name spaces, while also reducing the probability of conflicting domain name resolution data appearing when a user configures domain name resolution data within a specific domain name space. This increases the user's ease of configuring domain name resolution data and improves the user experience.

[0065] Based on the above concept, an embodiment of this specification provides a method for configuring domain name resolution data. The method for configuring domain name resolution data will be exemplarily described below with reference to the accompanying drawings.

[0066] Example scenarios

[0067] 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 domain name resolution data with the domain name resolution system 10. Based on the resolution data, the domain name resolution system 10 responds to the resolution requests of other users (such as the visitor 12 in Figure 3) and returns the IP address mapped to the domain name in the resolution request to meet the access needs of other users.

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

[0069] In Figure 3, domain name owner 11 and visitor 12 can access domain name resolution system 10 through a client. The domain name resolution system may include multiple servers, including authoritative domain name servers. A client can be an electronic device with network access capabilities. Specifically, for example, a client can be a desktop computer, tablet computer, laptop computer, smartphone, digital assistant, smart wearable device, etc. Smart wearable devices include, but are not limited to, smart bracelets, smart watches, and smart glasses.

[0070] A server can be an electronic device with certain computing and processing capabilities. It can have a network communication module, a processor, and memory, etc. Of course, the server can also refer to software running on the electronic device. The server can also be a distributed server, which can be a system with multiple processors, memories, network communication modules, etc. operating in coordination. Alternatively, the server can be a server cluster formed by multiple 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 embodiments of this specification. For example, it can be a new form of "server" based on quantum computing.

[0071] Exemplary Methods

[0072] Taking the domain name resolution system 10 applied to the application scenario shown in FIG3 as an example, as shown in FIG4 , the domain name resolution system includes multiple domain name spaces isolated from each other, and 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 FIG5 , and the method for configuring domain name resolution data includes:

[0073] 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 multiple domain name spaces; the domain name resolution data includes a mapping relationship between a domain name and an IP address.

[0074] 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 represent 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, or the like.

[0075] 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 resolution data to be configured, 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.

[0076] A domain name space can be a plurality of independent spaces in a domain name resolution system, and users are isolated from each other. A domain name space can be used to store domain name resolution data and provide domain name resolution services. In some embodiments, a domain name space can include one or more servers, which can specifically be authoritative domain name servers, and each authoritative domain name server stores information about at least part of the domain name space. Each domain name space can be used to store domain name resolution data configured by multiple users. Different domain name spaces can support different users to configure domain name resolution data for the same domain name. 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 users configure domain name resolution data in a certain domain name space, thereby improving the user's convenience in configuring domain name resolution data and improving the user experience.

[0077] 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;

[0078] The conflicting domain name resolution data includes domain name resolution data having a domain name identical to the domain name in the domain name resolution data to be configured.

[0079] 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. This 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.

[0080] For example, referring to Figure 6, assume that user A purchases domain name A and configures a mapping between domain name A and IP address A in namespace 255 of the domain name resolution system. The user then registers the authoritative server for domain name A with the domain name registry as namespace 255. In this case, when another user requests resolution for domain name A, the primary domain name server will return namespace 255 as the authoritative name server to the user's local domain name server. The user's local domain name server will then request namespace 255 to return IP address A, which is mapped to domain name A.

[0081] Later, assuming user B purchases domain name A from user A, user B will provide proof of ownership of domain name A to the registry, register the authoritative domain name server for domain name A as domain name space 0, and store the mapping between domain name A and IP address B in domain name space 0 of the domain name resolution system. Because domain name space 0 and domain name space 255 are isolated from each other, the mapping between domain name A and IP address B stored in domain name space 0 will not conflict with the mapping between domain name A and IP address A stored in domain name space 255. This will also 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 for 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. The user's local domain name server will then request domain name space 0 to return IP address B, which is mapped to domain name A.

[0082] 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 because the domain name resolution system already has a mapping relationship between domain name A and IP address A. This reduces the probability of conflicting domain name resolution data when the user configures the domain name resolution data, improves the user's convenience in configuring the domain name resolution data, and is conducive to improving the user experience.

[0083] In order to solve the problem of configuring domain name resolution data when conflicting domain name resolution data exists, in some embodiments, the method for configuring domain name resolution data further includes:

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

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

[0086] After the user provides proof of domain name ownership, in some embodiments, issuing the authentication prompt further includes:

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

[0088] In this embodiment, assume that the domain name resolution system has already stored a mapping between domain name D and IP address D in domain name space 1. Later, user E purchases domain name D, and user E's target domain name space is also domain name space 1. User E wishes to store the mapping between domain name D and IP address E in domain name space 1. At this point, the mapping between domain name D and IP address D in domain name space 1 is the conflicting domain name resolution data that user E submitted to the domain name resolution system for configuration. The domain name resolution system can issue an authentication prompt to user E, instructing user E to provide proof of ownership of domain name D. If user E provides this proof, the domain name resolution system can deem user E the current legal owner of domain name D and can overwrite the existing mapping between domain name D and IP address D with the new mapping between domain name D and IP address E. This allows the current owner of a domain name to configure its domain name resolution data normally when conflicting domain name resolution data exists in a certain domain name space.

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

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

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

[0092] In this embodiment, in a domain name space, if a configuration request submitted by the same user encounters 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.

[0093] For example, suppose that both user F and user G target domain name space 3, and user F purchases a large number of different domain names from user G. In this case, when user F attempts to configure domain name resolution data for these domain names in domain name space 3, configuration conflicts will frequently occur. To address this issue, after a preset number of configuration conflicts occur in a configuration request submitted by user F, the target domain name space corresponding to the user identifier corresponding to user F can be changed to domain name space 5. This reduces the probability of configuration conflicts occurring when user F configures domain name resolution data in the target domain name space, thereby improving the user experience.

[0094] In some implementations, when the target domain name space is changed for a 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.

[0095] Some users have a large number of domain names. A separate domain name space can be set up for them to ensure that these users can smoothly configure domain name resolution data. For example, in some embodiments, 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;

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

[0097] 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 no conflicting domain name resolution data exists in the target domain name space is entered;

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

[0099] In this embodiment, a shared space is used to correspond to multiple user identifiers, that is, users corresponding to multiple user identifiers share the same domain name space. A dedicated space is used to correspond to one user identifier, that is, a dedicated space is only used by 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 dedicated space. Dedicated 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.

[0100] To ensure high availability of the domain name space, in some embodiments, as shown in FIG8 , the process of obtaining the multiple domain name spaces includes:

[0101] Get multiple name server domain names;

[0102] 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;

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

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

[0105] Multiple name server domain names can be obtained by registering with a registry. For example, in Figure 8, 1,000 name server domain names, including ns1.cn, ns2.cn, ns256.cn, ns1.com, and ns256.com, are pre-registered. These domain names are then divided into 256 combinations (combinations 1 to 256), each consisting of four. The name server domain names in each combination represent a domain name space. For example, the name server domain names ns1.cn, ns1.com, ns1.org, and ns1.net in combination 1 can all represent domain name space 0. Local domain name servers can find domain name space 0 through ns1.cn, ns1.com, ns1.org, or ns1.net. In this way, if a first-level domain name server (e.g., a .com first-level domain name server) fails, it can return ns1.cn, ns1.org, or ns1.net through other first-level domain name servers (e.g., a .cn first-level domain name server, a .org first-level domain name server, or a .net first-level domain name server), allowing the local domain name server to normally find domain name space 0, thereby ensuring high availability of the domain name space.

[0106] Accordingly, an embodiment of this specification further provides a domain name resolution method, as shown in FIG9 , including:

[0107] 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;

[0108] S902: Determine, based on the resolution request, a domain name space to be resolved from a plurality of mutually isolated domain name spaces in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services;

[0109] 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 the IP address corresponding to the domain name to be resolved.

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

[0111] 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;

[0112] Determining, according to the resolution request, a domain name space to be resolved from the multiple domain name spaces includes:

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

[0114] The relevant limitations of the domain name space in the domain name resolution method can be found in the relevant description above, and this manual will not elaborate on them here.

[0115] Exemplary devices

[0116] Some embodiments of this specification further provide a device for configuring domain name resolution data, as shown in FIG10 . The device is applied to a domain name resolution system, wherein the domain name resolution system includes multiple domain name spaces isolated from each other, the domain name spaces being used to store domain name resolution data and provide domain name resolution services. The device for configuring domain name resolution data includes:

[0117] A domain name determination module 1001 is configured to determine, in response to a configuration request carrying a user identifier and domain name resolution data to be configured, a target domain name space corresponding to the user identifier from 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;

[0118] A data storage module 1002 is configured to store the to-be-configured domain name resolution data in the target domain name space if no conflicting domain name resolution data exists in the target domain name space;

[0119] The conflicting domain name resolution data includes domain name resolution data having a domain name identical to the domain name in the domain name resolution data to be configured.

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

[0121] In some embodiments, after issuing the authentication prompt, the data storage module is further configured 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.

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

[0123] a conflict resolution module configured to reallocate one of the domain name spaces to the user identifier as the target domain name space for the user identifier if a preset number of configuration conflict events occur in configuration requests carrying the same user identifier; the preset number of times being greater than or equal to one;

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

[0125] In some embodiments, the multiple domain name spaces include a shared space and a dedicated space; the shared space corresponds to multiple user identifiers, and the dedicated space corresponds to one user identifier;

[0126] The configuration device for domain name resolution data further includes:

[0127] a space determination module, configured to, if the target domain name space is the shared space, enter and trigger the data storage module if no conflicting domain name resolution data exists in the target domain name space;

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

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

[0130] Get multiple name server domain names;

[0131] 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;

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

[0133] Some embodiments of this specification further provide a domain name resolution device, as shown in FIG11 , including:

[0134] The request acquisition module 1101 is configured 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;

[0135] A resolution space module 1102 is configured to determine, based on the resolution request, a domain name space to be resolved from a plurality of mutually isolated domain name spaces in a domain name resolution system; the domain name space is used to store domain name resolution data and provide domain name resolution services;

[0136] The request forwarding module 1103 is configured to 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.

[0137] 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;

[0138] The resolution space module determines, based on the resolution request, a domain name space to be resolved from among the multiple domain name spaces, specifically for:

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

[0140] The domain name resolution data configuration device or domain name resolution device provided in the embodiments of this specification is based on the same inventive concept as the domain name resolution data configuration method or domain name resolution method provided in the aforementioned 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 aforementioned embodiments of this specification and will not be further elaborated here.

[0141] Exemplary electronic devices

[0142] Another embodiment of the present application further proposes an electronic device, as shown in Figure 12. An exemplary embodiment of the present specification further 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 steps of 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 embodiments of the present specification.

[0143] The internal structure of the electronic device can be shown in Figure 12. The electronic device includes a processor, a memory, a network interface and an input device connected through a system bus. Among them, 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 computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it follows the steps in the domain name resolution data configuration method or domain name resolution method according to various embodiments of the present specification as described in the above embodiments of the present specification.

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

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

[0146] The processor may be a general-purpose processor, such as a CPU or microprocessor, or an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program 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 device, discrete gate or transistor logic device, or discrete hardware components.

[0147] Input devices may include devices that receive data and information input by a user, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer, or gravity sensor.

[0148] Output devices may include means that allow information to be output to a user, such as display screens, printers, speakers, and the like.

[0149] The communication interface may include any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0150] The processor executes the computer program stored in the memory and calls other devices, which can be used to implement any domain name resolution data configuration method or each step of the domain name resolution method provided in the above embodiments of the present application.

[0151] The electronic device may further 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.

[0152] Those skilled in the art will understand that the structure shown in Figure 12 is merely a block diagram of a portion of the structure related to the scheme of this specification, and does not constitute a limitation on the electronic device to which the scheme of this specification is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0153] Exemplary computer program products and computer-readable storage media

[0154] 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-mentioned "Exemplary Method" section of this specification.

[0155] The computer program product may be written in any combination of one or more programming languages ​​to implement the operations of the embodiments of this specification, including object-oriented programming languages ​​such as Java, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's computing device, as a stand-alone 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.

[0156] In addition, an embodiment of this 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 domain name resolution method according to various embodiments of this specification described in the above "Exemplary Method" section of this specification.

[0157] It should be understood that the specific examples in this document are only intended to help those skilled in the art better understand the implementation methods of this specification, and are not intended to limit the scope of this specification.

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

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

[0160] Unless otherwise indicated, all technical and scientific terms used in the embodiments of this specification have the same meaning 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 combinations of one or more related listed items. The singular forms "a", "above", and "the" used in the embodiments of this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0161] It is understood that the processor in the embodiments of this specification can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, 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, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of this specification can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this specification can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0162] It will be 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 memories. 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.

[0163] 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. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this specification.

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

[0165] 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 embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

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

[0167] In addition, each functional unit in each embodiment of this 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.

[0168] 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 and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute 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.

[0169] The above description is merely a specific embodiment of this specification, but the scope of protection of this specification is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this specification should be included in the scope of protection of this specification. Therefore, the scope of protection of this specification should be based on the scope of protection of the claims.

Claims

1. A method for configuring domain name resolution data, characterized in that: 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 method of 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.

2. The method according to claim 1, characterized in that Also includes: If the conflicting domain name resolution data exists in the target domain name space, issuing an authentication prompt; 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.

3. The method according to claim 2, characterized in that 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.

4. The method according to claim 1, characterized in that: Also includes: If a configuration request carrying the same user identifier has a preset number of configuration conflict events, reallocate one of the domain name spaces for the user identifier as the 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.

5. The method according to claim 1, 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.

6. The method according to any one of claims 1 to 5, characterized in that: 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.

7. A domain name resolution method, characterized in that: include: Obtain a resolution request carrying the domain name to be resolved and the identifier of the domain name space to be resolved; The to-be-resolved domain name space identifier is used to represent the to-be-resolved domain name space; According to the resolution request, determining 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; 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.

8. The method according to claim 7, characterized in that The domain name space corresponds to a domain name combination, and 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 identifier of the domain name space to be resolved includes the domain name of the target name server; Determining, according to the resolution request, a domain name space to be resolved from among 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.

9. A device for configuring domain name resolution data, characterized in that: 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 respond to a configuration request carrying a user identifier and domain name resolution data to be configured, and to determine a target domain name space corresponding to the user identifier among 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; 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.

10. A domain name resolution device, characterized in that: include: A request acquisition module, used to acquire a resolution request carrying a domain name to be resolved and an identifier of a domain name space 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, configured 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.

11. An electronic device, characterized in that: include: Processor and 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.

12. A computer program product, characterized in that include: A computer program, the program being stored in a computer-readable storage medium; The processor of the computer device reads the computer program from the computer-readable storage medium, and when the processor executes the computer program, the method for configuring domain name resolution data according to any one of claims 1 to 6 or the steps of the domain name resolution method according to claim 7 or 8 are implemented.

Images