CN116938877B

CN116938877B - Domain name resolution data configuration method, domain name resolution method and related device

Info

Publication number: CN116938877B
Application number: CN202311197280.5A
Authority: CN
Inventors: 唐文旭
Original assignee: Alibaba Cloud Computing Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2023-09-15
Filing date: 2023-09-15
Publication date: 2024-01-05
Anticipated expiration: 2043-09-15
Also published as: CN116938877A

Abstract

The embodiment of the specification provides a configuration method of domain name resolution data, a domain name resolution method and a related device, wherein the configuration method of the domain name resolution data divides a plurality of isolated domain name spaces in a domain name resolution system, when a configuration request of a user for configuring a domain name is received, a target domain name space corresponding to a user identification of the user is determined in the plurality of domain name spaces, and when conflict domain name resolution data does not exist in the target domain name space, the domain name resolution data to be configured is stored in the target domain name space. Therefore, the domain name resolution system can support the requirement that different users configure the same domain name in different domain name spaces, the probability of conflicting domain name resolution data when the users configure the domain name resolution data in a certain domain name space is also reduced, the convenience of configuring the domain name resolution data by the users is improved, and the use experience of the users is improved.

Description

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

Technical Field

Embodiments in the present disclosure relate to the field of computer application technologies, and in particular, to a domain name resolution technology in the field of computer application technologies, and more particularly, to a method for configuring domain name resolution data, a domain name resolution method, and a related device.

Background

The IP address (Internet Protocol Address ) is a unified address format, in the internet, the IP address is a logical address of the internet participants, and each internet participant can access other internet participants by accessing their IP addresses. But IP addresses are typically composed of a string of numbers separated by dots, are inconvenient to remember, and cannot display the names and properties of internet participants. For this reason, domain names (Domain names) have been designed and the Domain names and IP addresses are mapped to each other through a Domain Name system (Domain Name System) so that users can more conveniently access the internet through the Domain names.

The domain name resolution system is a platform providing domain name resolution management services, which can help users manage and configure domain name resolution data. The user can establish the mapping relation between the domain name and the IP address by configuring the domain name resolution data in the domain name resolution system, so that the configuration convenience of the domain name resolution data is improved, and the method has important significance for improving the user experience.

Disclosure of Invention

Various embodiments in the present disclosure provide a method for configuring domain name resolution data, a domain name resolution method, and related devices, so as to achieve the purpose of improving the convenience of configuring domain name resolution data.

In a first aspect, an embodiment of the present disclosure provides a method for configuring domain name resolution data, which is applied to a domain name resolution system, where the domain name resolution system includes a plurality of domain name spaces isolated from each other, the domain name spaces are used for storing domain name resolution data and providing domain name resolution services, and the method for configuring domain name resolution data includes:

responding to a configuration request carrying a user identifier and domain name resolution data to be configured, and determining a target domain name space corresponding to the user identifier in a plurality of domain name spaces; the domain name resolution data to be configured comprises a mapping relation between a domain name and an IP address;

if the conflict domain name resolution data does not exist 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 a domain name in the domain name resolution data to be configured.

In a second aspect, an embodiment of the present specification provides a domain name resolution method, including:

acquiring an analysis request carrying a domain name to be analyzed and a domain name space identifier to be analyzed; the domain name space identifier to be resolved is used for representing the domain name space to be resolved;

Determining a domain name space to be resolved in a plurality of isolated domain name spaces of a domain name resolution system according to the resolution request; the domain name space is used for storing domain name resolution data and providing domain name resolution service;

and forwarding the resolution request to the domain name space to be resolved, wherein the resolution request is used for indicating 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 configuration apparatus of domain name resolution data, which is applied to a domain name resolution system including a plurality of domain name spaces isolated from each other, the domain name spaces storing domain name resolution data and providing a domain name resolution service, the configuration apparatus of domain name resolution data comprising:

the space determining module is used for responding to a configuration request carrying a user identifier and domain name resolution data to be configured, and determining a target domain name space corresponding to the user identifier in a plurality of domain name spaces; the domain name resolution data to be configured comprises a mapping relation between a domain name and an IP address;

the data storage module is used for storing the domain name resolution data to be configured in the target domain name space if the conflict domain name resolution data does not exist in the target domain name space;

In a fourth aspect, an embodiment of the present specification provides a domain name resolution apparatus, including:

the request acquisition module is used for acquiring an analysis request carrying a domain name to be analyzed and a domain name space identifier to be analyzed; the domain name space identifier to be resolved is used for representing the domain name space to be resolved;

the resolution space module is used for determining a domain name space to be resolved in a plurality of isolated domain name spaces of a domain name resolution system according to the resolution request; the domain name space is used for storing domain name resolution data and providing domain name resolution service;

and the request forwarding module is used for forwarding the resolution request to the domain name space to be resolved, and the resolution request is used for indicating the domain name space to be resolved to return an IP address corresponding to the domain name to be resolved.

In a fifth aspect, one embodiment of the present specification provides an electronic device comprising a processor and a memory;

wherein the memory is connected with the processor and is used for storing a computer program;

the processor is configured to implement the method for configuring domain name resolution data according to any one of the above or the method for domain name resolution according to any one of the above by running a computer program stored in the memory.

In a sixth aspect, an embodiment of the present disclosure provides a computer readable storage medium, where a computer program is stored, where the computer program is executed by a processor to implement a method for configuring domain name resolution data or a method for domain name resolution as described above.

In a seventh aspect, one embodiment of the present specification provides a computer program product or a computer program, the computer program product comprising a computer program 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 method for configuring domain name resolution data or the steps of the domain name resolution method when executing the computer program.

The embodiments provided in the present disclosure provide a method for configuring domain name resolution data, a domain name resolution method, and a related device, where the method for configuring domain name resolution data divides a plurality of isolated domain name spaces in a domain name resolution system, determines a target domain name space corresponding to a user identifier of a user from among the plurality of domain name spaces when a configuration request for configuring a domain name is received, and stores domain name resolution data to be configured in the target domain name space when no conflict domain name resolution data exists in the target domain name space. Therefore, the domain name resolution system can support the requirement that different users configure the same domain name in different domain name spaces, the probability of conflicting domain name resolution data when the users configure the domain name resolution data in a certain domain name space is also reduced, the convenience of configuring the domain name resolution data by the users is improved, and the use experience of the users is improved.

Drawings

Fig. 1 is a schematic structural diagram of a domain name.

Fig. 2 is a schematic diagram of a DNS resolution process.

Fig. 3 is a possible application scenario of a method for configuring domain name resolution data according to an embodiment of the present disclosure.

Fig. 4 is a schematic structural diagram of a domain name resolution system according to an embodiment of the present disclosure, where the domain name resolution system includes multiple domain namespaces.

Fig. 5 is a flowchart of a method for configuring domain name resolution data according to an embodiment of the present disclosure.

Fig. 6 is a schematic diagram of a case where 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 disclosure.

Fig. 7 is a flowchart of a method for configuring domain name resolution data according to another embodiment of the present disclosure.

Fig. 8 is a schematic diagram of a domain name space obtaining process according to an embodiment of the present disclosure.

Fig. 9 is a flow chart of a domain name resolution method according to an embodiment of the present disclosure.

Fig. 10 is a schematic structural diagram of a configuration device for domain name resolution data according to an embodiment of the present disclosure.

Fig. 11 is a schematic structural diagram of a domain name resolution device according to an embodiment of the present disclosure.

Fig. 12 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

Unless defined otherwise, technical or scientific terms used in the embodiments of the present specification should be given the ordinary meaning as understood by one of ordinary skill in the art to which the present specification belongs. The terms "first," "second," and the like, as used in the embodiments of the present disclosure, do not denote any order, quantity, or importance, but rather are used to avoid intermixing of the components.

Throughout the specification, unless the context requires otherwise, the word "plurality" means "at least two", and the word "comprising" is to be construed as open, inclusive meaning, i.e. as "comprising, but not limited to. In the description of the present specification, the terms "one embodiment," "some embodiments," "example embodiments," "examples," "particular examples," or "some examples," etc., 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 present specification. The schematic representations of the above terms do not necessarily refer to the same embodiment or example.

The technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

SUMMARY

Referring to fig. 1, a domain name is essentially a path of a large reverse tree, which may also be referred to as a domain namespace. A "domain" is a partition in the domain namespace that can be managed. In grammar, each domain name is composed of a sequence of labels (label) separated by dots (decimal points). The domain name can be divided into sub-domains, and the sub-domains can be further divided into sub-domains of the sub-domains, so that a primary domain name, a main domain name, a sub-domain name and the like are formed.

For example, in fig. 1, ".com" is a primary domain name, "xx.com" is a primary domain name (also referred to as a hosted primary domain name), "yyy.xx.com" is a sub-domain name (also referred to as a hosted secondary domain name), "www.yyy.xx.com" is a sub-domain of the sub-domain name (also referred to as a hosted tertiary domain name).

The DNS system may be a hierarchical structure corresponding to the domain name, and the DNS system may include a plurality of DNS servers in a hierarchical structure corresponding to the DNS system. With domain name structures, DNS servers are also required to resolve domain names, and are required to be resolved by DNS servers throughout the world, which are in fact hosts hosting the domain name system. The domain name resolution process involves 4 DNS servers, which may be: root DNS server (Root name server), primary domain name server (TldNameserver), authoritative domain name server (Authoritative Nameserver), and Local domain name server (DNS resolution or Local DNS).

Wherein the local domain name server may be used to respond to resolution requests from clients (clients) and eventually track DNS servers until resolution results are obtained. And when the local domain name server can not inquire the analysis result locally, inquiring the root DNS server, and acquiring the IP address of the primary domain name server. The authoritative domain name server has uniqueness in a specific area and is responsible for maintaining the mapping relation between the domain name and the IP address in the area. The primary domain name server is responsible for managing the secondary domain names registered under the primary domain name server.

Specifically, referring to fig. 2, the usage of each DNS server is described below in a single DNS resolution procedure, where the result of a DNS query is typically cached in a local domain name server, and if there is a cache in the local domain name server, the local domain name server directly returns the cached resolution result. The following example outlines the 8 steps required for DNS queries in the case where the local domain name server does not have a cache:

1. the user enters "example. Com" in the Web browser, and the recursive query is started by the local domain name server.

2. The local domain name Server adopts an iterative query method to query a Root domain name Server (Root Server).

3. The root Domain name server tells the local Domain name server the IP address of the next Level Domain name server (TLD) com that should be queried.

4. The local domain name server queries the primary domain name server com.

5. Com tells the local domain name server that next queries the example.

6. The local domain name Server sends a query to an example.

7. The example.com authoritative domain name server tells the local domain name server the host IP address to query.

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

Once 8 steps of the DNS query return the IP address of example.

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

10. the Web Server at the IP (Web Server) returns the Web page to be rendered in the browser.

The domain name resolution system may include a DNS server to provide a user with DNS resolution services and configuration services for domain name resolution data (i.e., the mapping of domain names to IP addresses). The DNS server included in the domain name resolution system may specifically be an authoritative domain name server, where the authoritative domain name server generally only has complete information about a portion of a domain name space, and this portion is referred to as a zone (zone), where the content of the zone may be loaded from a file or another authoritative domain name server, and after the loading, the authoritative domain name server may declare that the zone has authority (authority), and one authoritative domain name server may simultaneously have authority for multiple zones. In this specification, the domain name resolution system may refer to a system having a function of providing a domain name resolution service to a user, that is, the domain name resolution system may return a mapping relationship between a domain name and an IP address in response to a resolution request.

After the user purchases a domain name (for example, an example may be an example a.com), the user may configure an authoritative domain name server domain name on the domain name platform, where the authoritative domain name server domain name is used to characterize the name of the authoritative domain name server that owns the domain name resolution qualification. 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 the domain name resolution system to configure the correspondence of the domain name example a.com and the IP address. When other users access the domain name example A.com, the domain name resolution system returns the mapping relation between the example A.com and the IP address to the local domain name server, and the local domain name server returns the mapping relation to the browser of the user, so that the user can access the IP address finally.

Currently, domain name resolution systems do not support multiple users to configure domain name resolution data for the same domain name, which may result in reduced convenience of configuration for the users. For example, in some cases, the following may occur: the user A purchases and registers a domain name exeb.com, and configures a mapping relation between the exeb.com and an IP address B in a domain name resolution system; after that, the user B purchases the domain name example b.com from the user a hand, and registers at the registry. However, when the user B wants to configure the mapping relationship between the exeb.com and the IP address C in the same domain name resolution system, because the mapping relationship between the exeb.com and the IP address B already exists in the domain name resolution system, in order to avoid the problem of resolution anomaly, the domain name resolution system may reject the configuration requirement of the user B on the domain name resolution data of the exeb.com, or require the user B to provide the proof information having the domain name of exeb.com, which brings negative effects to the configuration convenience degree of the user B and is unfavorable for bringing good use experience to the user B.

In order to solve this problem, the inventors found through studies that a plurality of domain name spaces isolated from each other may be partitioned in a domain name resolution system, and when a configuration request for configuring a certain domain name by a user is received, a target domain name space corresponding to a user identification of the user is determined among the plurality of domain name spaces, and when conflicting domain name resolution data does not exist in the target domain name space, domain name resolution data to be configured is stored in the target domain name space. Therefore, the domain name resolution system can support the requirement that different users configure the same domain name in different domain name spaces, the probability of conflicting domain name resolution data when the users configure the domain name resolution data in a certain domain name space is also reduced, the convenience of configuring the domain name resolution data by the users is improved, and the use experience of the users is improved.

Based on the above concept, the present embodiment provides a method for configuring domain name resolution data, and the method for configuring domain name resolution data will be exemplarily described with reference to the accompanying drawings.

Exemplary scenario

Referring to fig. 3, fig. 3 is a possible application scenario of a method for configuring domain name resolution data, in fig. 3, a user (e.g., a domain name owner 11 in fig. 3) registers domain name resolution data with a domain name resolution system 10, and the domain name resolution system 10 responds to resolution requests of other users (e.g., a visitor 12 in fig. 3) based on the resolution data, and returns to an IP address mapped to the domain name in the resolution request, thereby meeting access requirements of other users.

The resolution request responded by the domain name resolution system may be directly sent to the domain name resolution system by a user or may be sent by a local domain name server, which is not limited in this specification.

In fig. 3, a domain name owner 11 and a visitor 12 may access a domain name resolution system 10 through clients, which may include a plurality of servers, which may include authoritative domain name servers. The client may be an electronic device with network access capabilities. Specifically, for example, the client may be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, or the like. Wherein, intelligent wearable device includes but is not limited to intelligent bracelet, intelligent wrist-watch, intelligent glasses etc..

The server may be an electronic device with some arithmetic processing capability. Which may have a network communication module, a processor, memory, and the like. Of course, the server may also refer to software running in the electronic device. The server may also be a distributed server, and may be a system having a plurality of processors, memories, network communication modules, etc. operating in concert. Alternatively, the server may be a server cluster formed for several servers. Or, with the development of science and technology, the server may also be a new technical means capable of realizing the corresponding functions of the embodiment of the specification. For example, a new form of "server" based on quantum computing implementation may be possible.

Exemplary method

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 namespaces isolated from each other, where the domain namespaces are used for storing domain name resolution data and providing domain name resolution services, and the embodiment of the present disclosure provides a method for configuring domain name resolution data, as shown in fig. 5, where the method for configuring domain name resolution data includes:

s501: responding to a configuration request carrying a user identifier and domain name resolution data to be configured, and determining 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 of a domain name and an IP address.

The user identification may be a unique identification of the user in the domain name resolution system, and the user identification may be used to characterize the identity of the user in the domain name resolution system. In some possible embodiments, the user identification may be, for example, a user name, a user ID, etc.

The domain name resolution data to be configured comprises the mapping relation between the domain name to be configured by the user and the IP address, and in most cases, the user represented by the user identifier has ownership of the domain name in the domain name resolution data to be configured. For example, user a purchased a domain name: example c.com and want to build a mapping relationship between example c.com and IP address 10.186.Xxx.102, so that other users can achieve access to IP address 10.186.Xxx.102 by typing example c.com in the browser. In the process of establishing the mapping relationship, the user a may send a configuration request carrying the mapping relationship between the example ec.com and the IP address 10.186.Xxx.102 to the domain name resolution system, and request the domain name resolution system to store the domain name resolution data to be configured, so that when the domain name resolution system receives the resolution request for the example ec.com, the domain name resolution system may return the IP address corresponding to the example ec.com to the requester.

The domain name space may be a plurality of spaces separated from each other and isolated from each other by users, which are divided in the domain name resolution system. The domain name space may be used to store domain name resolution data and may provide domain name resolution services. In some implementations, the domain name space may include one or more servers, which may be authoritative domain name servers, each storing information for at least a portion of the domain name space. Each domain name space can be used for storing domain name resolution data configured by a plurality of users, and can support the configuration of the domain name resolution data of the same domain name by different users in different domain name spaces, so that the domain name resolution system can support the requirement of different users for configuring the same domain name in different domain name spaces, the probability of conflicting domain name resolution data when the users configure the domain name resolution data in a certain domain name space is also reduced, the convenience of configuring the domain name resolution data by the users is improved, and the use experience of the users is improved.

S502: if the conflict domain name resolution data does not exist in the target domain name space, storing the domain name resolution data to be configured in the target domain name space;

When the domain name resolution data to be configured is stored, only whether the conflict domain name resolution data exists in the target domain name space is considered, so that the probability of occurrence of the conflict domain name resolution data when a user configures the domain name resolution data is reduced, the convenience of the user in configuring the domain name resolution data is improved, and the use experience of the user is improved.

For example, referring to fig. 6, assume that a user a purchases a domain name a, and configures a mapping relationship of the domain name a and an IP address a in a domain name space 255 of a domain name resolution system, and then registers an authoritative server of the domain name a as the domain name space 255 at a domain name registry. In this case, when other users request resolution for domain name a, the primary domain name server returns domain name space 255 as an authoritative domain name server to the user's local domain name server, which requests that domain name space 255 return IP address a having a mapping relationship with domain name a.

Then, assuming that the user B purchases the domain name a from the user a, the user B provides the certification information of the domain name a to the registry, registers the authoritative domain name server of the domain name a as the domain name space 0, and stores the mapping relationship between the domain name a and the IP address B in the domain name space 0 of the domain name resolution system. Since the domain name space 0 and the domain name space 255 are isolated from each other, the mapping relationship of the domain name a and the IP address B stored in the domain name space 0 does not conflict with the mapping relationship of the domain name a and the IP address a stored in the domain name space 255. And normal access to domain name a by other users is not affected. Specifically, in this case, when the other user requests resolution for the domain name a, since the user B has registered the authoritative domain name server of the domain name a as the domain name space 0, the primary domain name server returns the domain name space 0 as the authoritative domain name server to the user's local domain name server, which requests the domain name space 0 to return the IP address B having a mapping relationship with the domain name a.

Therefore, different domain name spaces of the domain name resolution system can support configuration requirements on domain name resolution data of the same domain name, when a user B configures the domain name resolution data of the domain name A in the domain name resolution system, the user B cannot be required to provide proof information again due to the mapping relation between the existing domain name A and the IP address A in the domain name resolution system, probability of conflicting domain name resolution data when the user configures the domain name resolution data is reduced, convenience in configuring the domain name resolution data by the user is improved, and use experience of the user is improved.

In order to solve the problem of configuring domain name resolution data when there is conflicting domain name resolution data, in some embodiments, as shown in fig. 7, the method for configuring domain name resolution data further includes:

if the conflict domain name resolution data exists in the target domain name space, an authentication prompt is sent out; the authentication prompt is used for indicating a user to provide proving information of the domain name in the domain name resolution data to be configured.

In this embodiment, when conflicting domain name resolution data exists in the target domain name space, an authentication prompt may be issued to prompt the user to provide proof information of the domain name in the domain name resolution data to be configured, so that the domain name resolution system may decide how to process the domain name resolution data to be configured according to the proof information.

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

and if the proving information is received, covering conflict domain name resolution data in the target domain name space by utilizing the domain name resolution data to be configured.

In this embodiment, it is assumed that the domain name resolution system has stored the mapping relationship between the domain name D and the IP address D in the domain name space 1, then the user E purchases the domain name D, and the target domain name space of the user E is also the domain name space 1, and wants to store the mapping relationship between the domain name D and the IP address E in the domain name space 1, where the mapping relationship between the domain name D and the IP address D in the domain name space 1 is the conflicting domain name resolution data of the domain name resolution data to be configured submitted to the domain name resolution system by the user E. The domain name resolution system can send an authentication prompt to the user E to indicate that the user E provides the proving information with the domain name D, if the user E provides the proving information, the domain name resolution system can consider the user E as the current legal owner of the domain name D, and the mapping relation between the domain name D and the IP address E can be utilized to cover the original mapping relation between the domain name D and the IP address D. Therefore, when conflicting domain name resolution data exists in a domain name space, the requirement that a user who currently owns a domain name normally configures the domain name resolution data of the domain name can be met.

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

if the configuration request carrying the same user identifier has configuration conflict events with preset times, reassigning a domain name space for the user identifier as a target domain name space of the user identifier; the preset times are greater than or equal to 1 time;

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

In this embodiment, if a configuration request submitted by the same user has a preset number of configuration conflict events in a domain name space, the target domain name space can be replaced for the user, so that the problem that the configuration request submitted by the user frequently has configuration conflicts is avoided, and the user experience is improved.

For example, assuming that the target namespaces of user F and user G are namespaces 3, and user F purchases a large number of different domain names from the hands of user G, in this case, a configuration conflict event frequently occurs when user F wants to configure the domain name resolution data of these domain names in namespaces 3. In order to solve the problem, after the configuration request submitted by the user F has configuration conflict events of a preset number, the target domain name space corresponding to the user identifier corresponding to the user F is replaced by the domain name space 5, so that the probability of the configuration conflict events when the user F configures domain name resolution data in the target domain name space can be reduced, and the user experience is improved.

In some embodiments, after the target domain name space is replaced for a certain user, the domain name resolution data configured in the original target domain name space by the user can be transferred to a new target domain name space, so that the user does not need to repeatedly configure the domain name resolution data, and the user experience is improved.

Some users have huge numbers of domain names, and a domain name space can be set for the users independently, so that the users can be guaranteed to smoothly process configuration domain name resolution data, for example, in some embodiments, the domain name spaces comprise a shared space and an exclusive space; the shared space corresponds to a plurality of user identifications, and the exclusive space corresponds to one user identification;

the determining, among the plurality of domain namespaces, a target domain namespace corresponding to the user identifier further includes:

if the target domain name space is the shared space, entering a step of storing the domain name resolution data to be configured in the target domain name space if conflict domain name resolution data does not exist in the target domain name space;

and if the target domain name space is the exclusive space, storing the domain name resolution data carried by the configuration request in the exclusive space.

In this embodiment, the shared space is used to correspond to a plurality of user identifiers, that is, users corresponding to the plurality of user identifiers share the same domain name space. The exclusive space is used for corresponding to one user identifier, namely, the exclusive space is only used for one user to configure domain name resolution data, so that the situation that a plurality of users configure domain name resolution data for the same domain name cannot occur in the exclusive space, the exclusive space can be allocated for the users with a large number of domain names, configuration conflict events which can occur when the users frequently configure the domain name resolution data are avoided, and user experience is improved.

To guarantee high availability of domain name space, in some embodiments, as shown in fig. 8, the multiple domain name space acquisition process includes:

acquiring a plurality of name server domain names;

dividing the plurality of name server domain names into a plurality of groups of domain name combinations, wherein the domain name combinations comprise at least one name server domain name;

and the domain name combination is corresponding to the domain name space, and the name server domain name in the domain name combination is used for representing the name of the domain name space.

The name server domain name is used for representing the name of the domain name space, and the primary domain name server can enable the local domain name server to find the domain name space represented by the name server domain name according to the name server domain name by sending the name server domain name to the local domain name server.

The plurality of name server domain names may be obtained by registering with a registry. For example, in fig. 8, 1000 name server domain names such as ns1.Cn, ns2.Cn … … ns256.Cn, ns1.Com … … ns256.Com and the like are registered in advance. Then dividing the domain name into 256 domain name combinations (1-256 of the domain name combinations) according to each four of the domain name combinations, wherein the domain name of the name server in each domain name combination is used for representing a domain name space, for example, the domain name of the name server in the domain name combination 1, ns1.com, ns1.org and ns1.net can be used for representing the domain name space 0, and the local domain name server can find the domain name space 0 through ns1.cn, ns1.com, ns1.org or ns1.net, so that when one of the primary domain name servers (for example, the com primary domain name server) fails, the other primary domain name servers (for example, the cn primary domain name server, the org primary domain name server or the net primary domain name server) can return to the domain name space 0 through the other primary domain name servers, so that the local domain name server can normally find the domain name space 0, and the high availability of the domain name space is ensured.

Accordingly, an embodiment of the present disclosure further provides a domain name resolution method, as shown in fig. 9, including:

S901: acquiring an analysis request carrying a domain name to be analyzed and a domain name space identifier to be analyzed; the domain name space identifier to be resolved is used for representing the domain name space to be resolved;

s902: determining a domain name space to be resolved in a plurality of isolated domain name spaces of a domain name resolution system according to the resolution request; the domain name space is used for storing domain name resolution data and providing domain name resolution service;

s903: and forwarding the resolution request to the domain name space to be resolved, wherein the resolution request is used for indicating 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 a local domain name server. The domain name space identifier to be resolved carried by the resolving request can be sent to the local domain name server by the primary domain name server or can be cached in the local domain name server. The present specification is not limited thereto.

Optionally, the domain name space corresponds to a domain name combination, the domain name combination including at least one name server domain name; the name server domain name in the domain name combination is used for representing the name of the domain name space; the domain name space identification to be resolved comprises a domain name of a target name server;

The determining, according to the resolution request, a domain name space to be resolved in a plurality of domain name spaces includes:

determining a domain name space corresponding to a target domain name combination as the domain name space to be resolved in a plurality of domain name spaces; the target domain name combination comprises the target name server domain name.

The description of the domain name space in the domain name resolution method may be referred to above, and the description is omitted herein.

Exemplary apparatus

Some embodiments of the present disclosure further provide a configuration apparatus for domain name resolution data, as shown in fig. 10, which is applied to a domain name resolution system, where the domain name resolution system includes a plurality of domain name spaces isolated from each other, the domain name spaces are used for storing domain name resolution data and providing domain name resolution services, and the configuration apparatus for domain name resolution data includes:

a space determining module 1001, 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 among a plurality of domain name spaces; the domain name resolution data to be configured comprises a mapping relation between a domain name and an IP address;

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

In some embodiments, the data storage module is further to: if the conflict domain name resolution data exists in the target domain name space, an authentication prompt is sent out; the authentication prompt is used for indicating a user to provide proving information of the domain name in the domain name resolution data to be configured.

In some embodiments, the data storage module is further configured to, after issuing the authentication prompt: and if the proving information is received, covering conflict domain name resolution data in the target domain name space by utilizing the domain name resolution data to be configured.

In some embodiments, the configuration device of domain name resolution data further includes:

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

In some embodiments, the plurality of domain namespaces includes a shared space and an exclusive space; the shared space corresponds to a plurality of user identifications, and the exclusive space corresponds to one user identification;

the configuration device of domain name resolution data further comprises:

the space determining module is used for entering into the data storage module if the conflict domain name resolution data does not exist in the target domain name space if the target domain name space is the shared space;

In some embodiments, the acquiring of the plurality of domain namespaces includes:

acquiring a plurality of name server domain names;

Some embodiments of the present disclosure further provide a domain name resolution apparatus, as shown in fig. 11, including:

a request acquisition module 1101, configured to acquire an 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 for representing the domain name space to be resolved;

the resolution space module 1102 is configured to determine, according to the resolution request, 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 for storing domain name resolution data and providing domain name resolution service;

a 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.

In some embodiments, the domain name space corresponds to a domain name combination comprising at least one name server domain name; the name server domain name in the domain name combination is used for representing the name of the domain name space; the domain name space identification to be resolved comprises a domain name of a target name server;

the resolution space module determines that the domain name space to be resolved is specifically used for:

The configuration device or the domain name resolution device for domain name resolution data provided in the embodiments of the present disclosure belongs to the same inventive concept as the configuration method or the domain name resolution method for domain name resolution data provided in the embodiments of the present disclosure. Technical details not described in detail in this embodiment may refer to the configuration method of domain name resolution data or specific processing content of the domain name resolution method provided in the foregoing embodiments of the present disclosure, which are not described herein again.

Exemplary electronic device

Another embodiment of the present application further provides an electronic device, referring to fig. 12, and an exemplary embodiment of the present specification further provides an electronic device, including: the system includes a memory storing a computer program, and a processor that executes steps in a domain name resolution data configuration method or a domain name resolution method according to various embodiments of the present specification described in the above embodiments of the present specification when the processor executes the computer program.

The internal structure of the electronic device may be as shown in fig. 12, and the electronic device includes a processor, a memory, a network interface, and an input device connected through a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic device includes a nonvolatile 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 programs in the non-volatile storage media. The network interface of the electronic device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, performs the steps in the method for configuring domain name resolution data or the method for domain name resolution according to the various embodiments of the present specification described in the above embodiments of the present specification.

The processor may include a host processor, and may also include a baseband chip, modem, and the like.

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

The processor may be a general-purpose processor, such as a general-purpose processor (CPU), microprocessor, or the like, or may be an Application-specific integrated circuit (ASIC), or one or more integrated circuits, that control the execution of programs in accordance with aspects of the present invention. But may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

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

The output device may include means, such as a display screen, printer, speakers, etc., that allow information to be output to the user.

The communication interface may include means, such as any transceiver, for communicating 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 invokes other devices, which can be used to implement any of the configuration methods of domain name resolution data or the steps of the domain name resolution methods provided in the embodiments of the present application.

The electronic equipment can also comprise a display component and a voice component, wherein the display component can be a liquid crystal display screen or an electronic ink display screen, an input device of the electronic equipment can be a touch layer covered on the display component, can also be a key, a track ball or a touch pad arranged on a shell of the electronic equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structure shown in fig. 12 is merely a block diagram of a portion of the structure associated with the present description and does not constitute a limitation of the electronic device to which the present description is applied, and that a particular electronic device may include more or less components than those shown, or may combine some components, or have a different arrangement of components.

Exemplary computer program product and computer readable storage Medium

In addition to the methods and apparatus described above, the domain name resolution data configuration method or domain name resolution method provided by the embodiments of the present specification may also be a computer program product comprising a computer program which, when executed by a processor, causes the processor to perform the steps in the domain name resolution data configuration method or domain name resolution method according to the various embodiments of the present specification described in the "exemplary method" section of the present specification.

The computer program product may write program code for performing the operations of embodiments of the present description in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server.

Furthermore, the embodiments of the present specification also provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the steps in the configuration method or the domain name resolution method of domain name resolution data according to the various embodiments of the present specification described in the above-described "exemplary method" section of the present specification.

It will be appreciated that the specific examples herein are intended only to assist those skilled in the art in better understanding the embodiments of the present description and are not intended to limit the scope of the present description.

It should be understood that, in various embodiments of the present disclosure, the sequence number of each process does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

It will be appreciated that the various embodiments described in this specification may be implemented either alone or in combination, and are not limited in this regard.

Unless defined otherwise, all technical and scientific terms used in the embodiments of this specification have the same meaning as commonly understood by one of ordinary skill in the art to which this specification belongs. The terminology used in the description is for the purpose of describing particular embodiments only and is not intended to limit the scope of the description. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It will be appreciated that the processor of the embodiments of the present description may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital signal processor (Digital SignalProcessor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in the embodiments of this specification may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory, among others. The volatile memory may be Random Access Memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present specification.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and unit may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present specification may be essentially or portions contributing to the prior art or portions of the technical solutions may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.

The foregoing is merely specific embodiments of the present disclosure, but the scope of the disclosure is not limited thereto, and any person skilled in the art who is skilled in the art can easily think about variations or substitutions within the scope of the disclosure of the present disclosure, and it is intended to cover the variations or substitutions within the scope of the disclosure. Therefore, the protection scope of the present specification shall be subject to the protection scope of the claims.

Claims

1. A method for configuring domain name resolution data, applied to a domain name resolution system, the domain name resolution system including a plurality of domain name spaces isolated from each other, the domain name spaces storing domain name resolution data and providing domain name resolution services, the method for configuring domain name resolution data comprising:

the multiple domain name spaces comprise a shared space, and if the target domain name space is the shared space, the method enters a step of storing the domain name resolution data to be configured in the target domain name space if conflict domain name resolution data does not exist in the target domain name space; the shared space corresponds to a plurality of user identifications;

2. The method as recited in claim 1, further comprising:

3. The method of claim 2, wherein the issuing an authentication prompt further comprises:

4. The method as recited in claim 1, further comprising:

5. The method of claim 1, wherein the plurality of domain namespaces comprises a shared space and an exclusive space; the shared space corresponds to a plurality of user identifications, and the exclusive space corresponds to one user identification;

6. The method according to any one of claims 1 to 5, wherein the acquiring the plurality of domain namespaces includes:

acquiring a plurality of name server domain names;

7. A method for domain name resolution, comprising:

Determining a domain name space to be resolved in a plurality of isolated domain name spaces of a domain name resolution system according to the resolution request; the domain name space is used for storing domain name resolution data and providing domain name resolution service; the domain name resolution system comprises a plurality of domain name spaces, wherein the plurality of domain name spaces comprise a shared space and an exclusive space; the shared space corresponds to a plurality of user identifications, and the exclusive space corresponds to one user identification;

8. The method of claim 7, wherein the domain name space corresponds to a domain name combination, the domain name combination comprising at least one name server domain name; the name server domain name in the domain name combination is used for representing the name of the domain name space; the domain name space identification to be resolved comprises a domain name of a target name server;

9. A configuration apparatus of domain name resolution data, applied to a domain name resolution system including a plurality of domain name spaces isolated from each other, the domain name spaces storing domain name resolution data and providing a domain name resolution service, the configuration apparatus of domain name resolution data comprising:

the data storage module is used for storing the domain name resolution data to be configured in the target domain name space if the conflict domain name resolution data does not exist in the target domain name space under the condition that the target domain name space is the shared space;

10. A domain name resolution device, comprising:

The resolution space module is used for determining a domain name space to be resolved in a plurality of isolated domain name spaces of a domain name resolution system according to the resolution request; the domain name space is used for storing domain name resolution data and providing domain name resolution service; the domain name resolution system comprises a plurality of domain name spaces, wherein the plurality of domain name spaces comprise a shared space and an exclusive space; the shared space corresponds to a plurality of user identifications, and the exclusive space corresponds to one user identification;

11. An electronic device, comprising: a processor and a memory;

the processor is configured to implement the method for configuring domain name resolution data according to any one of claims 1 to 6 or the method for domain name resolution according to claim 7 or 8 by running a computer program stored in the memory.

12. A computer-readable storage medium, comprising: the computer readable storage medium stores a computer program, which when executed by a processor, implements 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.