WO2016177284A1

WO2016177284A1 - Domain name resolution method and device

Info

Publication number: WO2016177284A1
Application number: PCT/CN2016/079819
Authority: WO
Inventors: 刘岩
Original assignee: 阿里巴巴集团控股有限公司; 刘岩
Priority date: 2015-05-07
Filing date: 2016-04-21
Publication date: 2016-11-10
Also published as: CN106210159B; CN106210159A

Abstract

Disclosed in the present application are a domain name resolution method and device, including: receiving a domain name resolution request sent from an external server, wherein the domain name resolution request comprises an object to be processed; when the object to be processed is the domain name and it is confirmed that the object to be processed does not exist in a distributed cache database, resolving the object to be processed according to a mode to process domain name in parallel; when the object to be processed is a resolution record corresponding to the domain and it is confirmed that the domain name corresponding to the object to be processed exist in the distributed cache database, producing the object to be processed according to a producing time sequence of the resolution record corresponding to the domain name. So, when resolving the domain name, processing different domain names using the parallel processing mode in a particle size of domain name can effectively avoid the problem of domain name resolution processing flow stagnation caused by problems of domain name resolution failure or by the problem that the domain name cannot be resolved etc., and greatly improve the processing efficiency of the domain name processing flow.

Description

Domain name resolution method and device

Technical field

The present application relates to the field of communications technologies, and in particular, to a domain name resolution method and device.

Background technique

With the development of Internet technology, people can locate a computer in the Internet through an Internet Protocol (English: Internet Protocol; abbreviation: IP) address, that is, when an IP address is obtained, it can be determined by the IP address. A computer on the Internet that corresponds to the IP address.

However, since the IP address is not easily remembered by people, it is proposed to replace the IP address with a domain name. However, the domain name cannot be directly accessed by the domain name corresponding to the computer corresponding to the IP address. Therefore, when obtaining a domain name, the domain name resolution process is required to convert the obtained domain name into an IP address; and the obtained IP address is used to access the computer corresponding to the IP address.

Domain name resolution generally relies on the domain name service (English: Domain Name Service; abbreviation: DNS) system to complete. When performing DNS domain name resolution, the DNS system generates at least one parsing record for each valid domain name. Each parsing record includes a domain name, a lifetime, a record type, and an IP address corresponding to the domain name.

However, the timing requirements for domain name resolution are relatively high. Specifically, the general domain name parsing process includes: first sorting the acquired domain names according to the time and/or the set domain name processing order; secondly, parsing the obtained domain names according to the sort order of the domain names, and obtaining each domain name correspondingly Analytic record.

However, in the current domain name resolution process, once a domain name cannot be resolved or parsed, the domain name resolution process will be stagnant, or a large number of domain names after the domain name cannot be parsed, which greatly reduces the efficiency of domain name resolution.

Summary of the invention

In view of this, the embodiment of the present application provides a domain name resolution method and device, which are used to solve the problem of low domain name resolution efficiency in the prior art.

A method for domain name resolution, comprising:

Receiving a domain name resolution request sent by an external server, where the domain name resolution request includes a to-be-processed object;

When the object to be processed is a domain name, and it is determined that the object to be processed does not exist in the distributed cache database, the object to be processed is parsed according to the manner in which the domain name is processed in parallel;

When the to-be-processed object is a parsing record corresponding to the domain name, and determining that the domain name corresponding to the object to be processed exists in the distributed cache database, the object to be processed is performed according to the generation time sequence of the parsing records corresponding to the domain name. produce.

A domain name resolution device, including:

a receiving unit, configured to receive a domain name resolution request sent by an external server, where the domain name resolution request includes a to-be-processed object;

a parsing unit, configured to: when the object to be processed is a domain name, and determine that the object to be processed does not exist in the distributed cache database, parse the object to be processed according to a method of processing a domain name in parallel;

The beneficial effects of the application are as follows:

The embodiment of the present application receives a domain name resolution request sent by an external server, where the domain name resolution request includes an object to be processed; when the object to be processed is a domain name, and determines that the object to be processed does not exist in the distributed cache database, The object to be processed is parsed according to the manner in which the domain name is processed in parallel; when the object to be processed is a parsing record corresponding to the domain name, and the domain name corresponding to the object to be processed exists in the distributed cache database, The generation time of the corresponding analysis record is generated, and the object to be processed is produced. In this way, when the domain name is parsed, the domain name is used as the granularity, and the parallel processing is adopted for different domain names, thereby effectively avoiding the problem that the domain name parsing process is stagnated due to the failure of domain name resolution or the inability to resolve, and effectively improving the domain name resolution processing. Process Processing efficiency.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following drawings will be briefly described in the description of the embodiments. It is obvious that the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without paying for inventive labor.

FIG. 1 is a schematic flowchart of a domain name resolution method according to an embodiment of the present disclosure;

2 is a schematic flowchart of a DNS calling the locked parsing record;

3 is a schematic flowchart of parsing an object to be processed in the parsing queue again;

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

detailed description

For the purpose of improving the efficiency of the domain name resolution in the present application, the embodiment of the present application provides a domain name resolution method and device, and receives a domain name resolution request sent by an external server, where the domain name resolution request includes a to-be-processed object; If the object is a domain name, and the object to be processed is not in the distributed cache database, the object to be processed is parsed according to the way in which the domain name is processed in parallel; And determining that the domain name corresponding to the object to be processed exists in the distributed cache database, and the object to be processed is produced according to the generation time sequence of the parsing records corresponding to the domain name. In this way, when the domain name is parsed, the domain name is used as the granularity, and the parallel processing is adopted for different domain names, thereby effectively avoiding the problem that the domain name parsing process is stagnated due to the failure of domain name resolution or the inability to resolve, and effectively improving the domain name resolution processing. Process efficiency.

The various embodiments of the present application are further described in detail below with reference to the accompanying drawings. It is apparent that the described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. Based on the embodiments of the present invention, all of those obtained by those of ordinary skill in the art without creative efforts Other embodiments are within the scope of the invention.

FIG. 1 is a schematic flowchart diagram of a domain name resolution method according to an embodiment of the present disclosure. The method can be as follows.

Step 101: Receive a domain name resolution request sent by an external server.

The domain name resolution request includes a to-be-processed object.

The object to be processed includes a resolution record corresponding to the domain name and/or the domain name.

It should be noted that the external server can be tc_server.

In step 101, the parsing record corresponding to the domain name may be a parsing record that the tc_server parses the domain name.

Step 102: Determine whether the object to be processed is a domain name. If the object to be processed is a domain name, go to step 103. If the object to be processed is a resolution record corresponding to the domain name, go to step 106.

Step 103: It is further determined whether the to-be-processed object exists in the distributed cache database. If it is determined that the object to be processed exists in the distributed database, step 104 is performed; if it is determined that the object is not present in the distributed database, step 105 is performed.

Step 104: Add a parsing record related to the object to be processed in a cache queue corresponding to the object to be processed in the distributed database, and perform a locking operation on the parsing record.

The locking operation includes at least one of an adding operation, a deleting operation, and a modifying operation.

In step 105, the object to be processed is parsed according to the manner in which the domain name is processed in parallel, and the process proceeds to step 109.

In step 105, a parsing record related to the object to be processed is added to the distributed cache database in a manner of processing the domain name in parallel, and a locking operation is performed on the parsed record.

Specifically, in the distributed cache database, a cache queue is created for the object to be processed, and the cache queue is configured to store a parsed record corresponding to the to-be-processed object that is subsequently received.

Specifically, adding a parsing record related to the scheduled object to be processed may be adding a parsing record with the object to be processed as a key value.

Optionally, the recorded record status of the added parsed record is marked as a locked state.

Step 106: further determining whether there is a locked parsing record in the parsing record related to the domain name corresponding to the object to be processed in the distributed cache database, and if there is a locked parsing record, executing step 107; otherwise, performing steps 108.

Step 107: When it is determined that there is a locked parsing record, the object to be processed is added after the locked parsing record in the distributed cache database, and waiting for the locked parsing record to be sent to the domain name service The system DNS application interface API performs production, and when the production is successful, instructs the DNS API to directly schedule the to-be-processed object.

In step 107, the object to be processed is added after the locked parsing record, and the production operation is sequentially performed on the parsed parsed record according to the generation time of the parsing record.

After the locked parsing record is processed, the object to be processed is added after the locked parsing record is directly called.

Specifically, the object to be processed is added after the locked parsing record, and the method includes:

In the locked parsing record, a new parsing record is added, and the new parsing record takes a domain name corresponding to the object to be processed and a cache (for example, the domain name _Cache) as a key value.

Specifically, the manner in which the DNS invokes the locked parsing record may include:

As shown in FIG. 2, a schematic diagram of a process of calling the locked parsing record for DNS is shown.

S21: The interception production queue contains the locked parsing record.

S22: Send the intercepted parsed record to the DNS application programming interface (English: Application Programming Interface; abbreviation: API).

S23: When receiving the locked parsing record, the DNS API determines whether the locked parsing record is successfully produced. If the production is successful, executing S24; otherwise, executing S27.

In S23, the production success here may mean that the locked analytical record is an analytical record that meets the record type requirement, and the subsequent successful use of the analytical record.

The record type generally includes the A record type, the CNAME record type, the MX record type, the NS record type, etc., and will not be described in detail here.

S24: The DNS API determines, according to the domain name included in the locked parsing record, that the domain name included in the locked parsing record further includes other parsing records (ie, pending) when determining that the locked parsing record is successfully produced. Object), directly call the object to be processed.

It should be noted that the object to be processed is marked as a locked state.

S25: The DNS API performs a locking operation on the object to be processed.

S26: The DNS API sends the result of the lock operation to the production queue when the lock operation is successful, and the process proceeds to step 111. When it is determined that the lock operation fails, the object to be processed is sent to the parsing failure queue again. The jump proceeds to step 110.

S27: The DNS API sends the locked parsing record to the production queue when it is determined that the locked parsing record production fails, and the jump proceeds to S21.

If the result of the second determination is a production failure in S23, the analysis record is sent to the analysis failure queue.

It should be noted that the result of the locking operation includes the successful execution of the locking operation and the failure of the locking operation; if the locking operation is successful, the jump proceeds to step 111; if the locking operation fails, the jump proceeds to step 110.

Optionally, if the locking operation fails, the method may further include: triggering the repeatedly performing the locking operation, when the number of times the locking operation is repeatedly executed reaches a set value, at this time, if the locking operation is successful, the jump is performed. Step 111 is performed; if the locking operation fails, the process proceeds to step 110.

It should be noted that the set value may be determined according to actual needs, or may be determined according to experimental data. For example, the set value is 3, and the size of the set value is not limited herein.

Step 108: Add a parsing record related to the domain name corresponding to the object to be processed in the distributed cache database, and perform a locking operation on the parsing record, and execute the jump 109.

Step 109: Determine whether the locking operation is successful. When the locking operation fails, step 110 is performed. When the locking operation is successful, step 111 is performed.

Step 110: Send the parsing record before performing the locking operation to the parsing failure queue, so as to parse the parsing record in the parsing failure queue again within the set time.

The parsing failure queue is used to store the parsing record of the parsing failure.

In step 110, the parsed record in the parsing failure queue is parsed again, including:

And determining, according to the set domain name scheduling sequence and the domain name corresponding to each parsing record in the parsing failure queue, an order in which the parsing records in the parsing failure queue are scheduled;

Determining, by the parsing record of the current schedule, whether the domain name corresponding to the parsing record exists in the distributed cache database;

If the domain name corresponding to the parsing record does not exist in the distributed cache database, returning a domain name error message to the external server;

If the domain name corresponding to the parsing record exists in the distributed cache database, performing a locking operation on the parsed record that is scheduled;

When the locking operation is successful, the parsing record obtained after the performing the locking operation is sent to the parsing record queue, so that the domain name service system DNS invokes the parsing record in the parsing record queue;

When the locking operation fails, the parsing record before the lock operation is executed is sent to the parsing failure queue, so that the parsing record in the parsing failure queue is parsed again within the set time.

Specifically, the manner in which the object to be processed in the parsing queue is parsed again within a set time may be as follows:

As shown in FIG. 3, it is a schematic flowchart of parsing an object to be processed in the parsing queue again.

S31: Schedule the to-be-processed object in sequence from the parsing failure queue according to the set domain name scheduling sequence.

S32: Determine, for the currently scheduled object to be processed, whether the domain name corresponding to the object to be processed exists in the distributed cache database, if not, execute S33; otherwise, execute S34.

S33: If the domain name corresponding to the object to be processed does not exist in the distributed cache database, return a domain name error message to the external server.

S34: If the domain name corresponding to the object to be processed exists in the distributed cache database, parse the scheduled object to be processed, and perform a locking operation on the parsed record.

Specifically, parsing the to-be-processed object to be scheduled may include:

If the domain name corresponding to the object to be processed exists in the distributed cache database, a new parsing record is obtained according to the domain name corresponding to the object to be processed. The new parsing record is obtained by using the domain name corresponding to the to-be-processed object as a key value, and the key value corresponding to the to-be-processed object is obtained by replacing the key value of the domain name and the cached parsing record, and the object to be processed is The corresponding key value is the key value of the domain name and the cached parsing record.

Performing a locking operation on the parsed parsed record may include:

Perform a lock operation on the resulting new parsed record.

When the locking operation is successful, the parsing record after the locking operation is sent to the parsing record queue;

When the locking operation fails, the pending object is sent again to the parsing failure queue.

It should be noted that the result of performing the locking operation on the obtained new parsing record includes the successful execution of the locking operation and the execution failure of the locking operation; if the locking operation is successful, the jump proceeds to step 111; if the locking operation fails, the jump Go to step 110.

Optionally, if the locking operation fails to be performed, the method may further include: triggering the repeated execution of the lock In the operation, when the number of times the lock operation is repeatedly executed reaches the set value, at this time, if the lock operation is successful, the jump proceeds to step 111; if the lock operation fails, the jump proceeds to step 110.

Step 111: Send a lock operation result to the production queue, so that the DNS API calls the lock operation result in the production queue.

In step 111, upon successfully parsing the object to be processed, the result of the locking operation is sent to the production queue, so that the DNS API calls the locking operation result in the production queue.

Receiving, by the solution described in the present application, a domain name resolution request sent by an external server, where the domain name resolution request includes an object to be processed; when the object to be processed is a domain name, and determining that the object to be processed does not exist in the distributed cache In the database, the object to be processed is parsed according to the way in which the domain name is processed in parallel; when the object to be processed is a parsing record corresponding to the domain name, and the domain name corresponding to the object to be processed is determined to exist in the distributed cache database. The object to be processed is produced according to the generation time sequence of the parsing records corresponding to the domain name. In this way, when the domain name is parsed, the domain name is used as the granularity, and the parallel processing is adopted for different domain names, thereby effectively avoiding the problem that the domain name parsing process is stagnated due to the failure of domain name resolution or the inability to resolve, and effectively improving the domain name resolution processing. Process efficiency.

FIG. 4 is a schematic structural diagram of a domain name resolution device according to an embodiment of the present disclosure. The domain name resolution device includes: a receiving unit 41 and a parsing unit 42, wherein:

The receiving unit 41 is configured to receive a domain name resolution request sent by an external server, where the domain name resolution request includes an object to be processed;

The parsing unit 42 is configured to: when the object to be processed is a domain name, and determine that the object to be processed does not exist in the distributed cache database, parse the object to be processed according to a method of processing a domain name in parallel;

When the to-be-processed object is a parsing record corresponding to the domain name, and determining that the domain name corresponding to the object to be processed exists in the distributed cache database, the generation time of the parsing record corresponding to the domain name is The production of the object to be processed is performed.

Specifically, the parsing unit 42 parses the object to be processed according to the manner in which the domain name is processed in parallel, and is specifically used to:

Adding a parsing record related to the object to be processed in the distributed cache database, and performing a locking operation on the parsing record, wherein the locking operation includes at least an adding operation and deleting Operate, modify at least one of the operations.

Specifically, the parsing unit 42 performs the production of the object to be processed according to the generation time sequence of the parsing records corresponding to the domain name, specifically for:

Determining whether there is a locked parsing record in the parsing record related to the domain name corresponding to the object to be processed in the distributed cache database;

When it is determined that there is a locked parsing record, the object to be processed is added after the locked parsing record in the distributed cache database, and waiting for the locked parsing record to be sent to the domain name service system DNS application The interface API performs production, and when the production is successful, instructing the DNS API to directly schedule the to-be-processed object;

When it is determined that there is no locked parsing record, a parsing record related to the domain name corresponding to the object to be processed is added to the distributed cache database, and a locking operation is performed on the parsing record, wherein the locking operation is at least Contains at least one of an increase operation, a delete operation, and a modification operation.

Optionally, the domain name resolution device further includes: a sending unit 43, where:

The sending unit 43 is configured to send a lock operation result to a production queue when the locking operation is performed successfully, so that the DNS API invokes the locking operation result in the production queue;

When the execution of the lock operation fails, the parsing record that fails the lock execution operation is sent to the parsing failure queue, so that the parsing record in the parsing failure queue is parsed again within a set time, wherein the parsing failure queue Used to store parsing records for parsing failures.

Specifically, the parsing unit 42 parses the parsed record in the parsing failure queue again, specifically for:

It should be noted that the domain name resolution device provided by the embodiment of the present disclosure may be implemented by using a hardware, or may be implemented by using a software, which is not limited herein. The domain name resolution device receives the domain name resolution request sent by the external server, where the domain name resolution request includes the object to be processed; when the object to be processed is a domain name, and determines that the object to be processed does not exist in the distributed cache database, The method of processing the domain name in parallel, parsing the object to be processed; when the object to be processed is a parsing record corresponding to the domain name, and determining that the domain name corresponding to the object to be processed exists in the distributed cache database, corresponding to the domain name The generation time sequence of the analysis records is performed, and the object to be processed is produced. In this way, when the domain name is parsed, the domain name is used as the granularity, and the parallel processing is adopted for different domain names, thereby effectively avoiding the problem that the domain name parsing process is stagnated due to the failure of domain name resolution or the inability to resolve, and effectively improving the domain name resolution processing. Process efficiency.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, apparatus (device), or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can be employed in one or more of its A computer program product embodied on a computer usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the preferred embodiment of the present application has been described, it will be apparent that those skilled in the art can make further changes and modifications to the embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A domain name resolution method, comprising:

Receiving a domain name resolution request sent by an external server, where the domain name resolution request includes a to-be-processed object;

When the object to be processed is a domain name, and it is determined that the object to be processed does not exist in the distributed cache database, the object to be processed is parsed according to the manner in which the domain name is processed in parallel;

When the to-be-processed object is a parsing record corresponding to the domain name, and determining that the domain name corresponding to the object to be processed exists in the distributed cache database, the object to be processed is performed according to the generation time sequence of the parsing records corresponding to the domain name. produce.
The domain name resolution method according to claim 1, wherein the parsing of the object to be processed according to the way of processing the domain name in parallel comprises:

Adding a parsing record related to the object to be processed in the distributed cache database, and performing a locking operation on the parsing record, wherein the locking operation includes at least an adding operation and deleting Operate, modify at least one of the operations.
The domain name resolution method according to claim 1, wherein the production of the object to be processed is performed according to a generation time sequence of the analysis records corresponding to the domain name, including:

Determining whether there is a locked parsing record in the parsing record related to the domain name corresponding to the object to be processed in the distributed cache database;

When it is determined that there is a locked parsing record, the object to be processed is added after the locked parsing record in the distributed cache database, and waiting for the locked parsing record to be sent to the domain name service system DNS application The interface API performs production, and when the production is successful, instructing the DNS API to directly schedule the to-be-processed object;

When it is determined that there is no locked parsing record, a parsing record related to the domain name corresponding to the object to be processed is added to the distributed cache database, and a locking operation is performed on the parsing record, wherein the locking operation is at least Contains at least one of an increase operation, a delete operation, and a modification operation.
The domain name resolution method according to claim 2 or 3, wherein after performing the locking operation on the parsing record, the method further comprises:

When the locking operation is successful, the result of the locking operation is sent to the production queue, so that the DNS API calls the locking operation result in the production queue;

When the execution of the lock operation fails, the parsing record that fails the lock execution operation is sent to the parsing failure queue, so that the parsing record in the parsing failure queue is parsed again within a set time, wherein the parsing failure queue Used to store parsing records for parsing failures.
The domain name resolution method according to claim 1, wherein the parsing record in the parsing failure queue is parsed again, including:

And determining, according to the set domain name scheduling sequence and the domain name corresponding to each parsing record in the parsing failure queue, an order in which the parsing records in the parsing failure queue are scheduled;

Determining, by the parsing record of the current schedule, whether the domain name corresponding to the parsing record exists in the distributed cache database;

If the domain name corresponding to the parsing record does not exist in the distributed cache database, returning a domain name error message to the external server;

If the domain name corresponding to the parsing record exists in the distributed cache database, performing a locking operation on the parsed record that is scheduled;

When the locking operation is successful, the parsing record obtained after the performing the locking operation is sent to the parsing record queue, so that the domain name service system DNS invokes the parsing record in the parsing record queue;

When the locking operation fails, the parsing record before the lock operation is executed is sent to the parsing failure queue, so that the parsing record in the parsing failure queue is parsed again within the set time.
A domain name resolution device, comprising:

a receiving unit, configured to receive a domain name resolution request sent by an external server, where the domain name resolution request includes a to-be-processed object;

a parsing unit, configured to: when the object to be processed is a domain name, and determine that the object to be processed does not exist When the domain name is processed in parallel, the object to be processed is parsed;

When the to-be-processed object is a parsing record corresponding to the domain name, and determining that the domain name corresponding to the object to be processed exists in the distributed cache database, the object to be processed is performed according to the generation time sequence of the parsing records corresponding to the domain name. produce.
The domain name resolution device according to claim 6, wherein the parsing unit parses the object to be processed in a manner of processing a domain name in parallel, and is specifically configured to:

Adding a parsing record related to the object to be processed in the distributed cache database, and performing a locking operation on the parsing record, wherein the locking operation includes at least an adding operation and deleting Operate, modify at least one of the operations.
The domain name resolution device according to claim 6, wherein the parsing unit performs the production of the object to be processed according to the generation time sequence of the parsing records corresponding to the domain name, specifically for:

Determining whether there is a locked parsing record in the parsing record related to the domain name corresponding to the object to be processed in the distributed cache database;

When it is determined that there is a locked parsing record, the object to be processed is added after the locked parsing record in the distributed cache database, and waiting for the locked parsing record to be sent to the domain name service system DNS application The interface API performs production, and when the production is successful, instructing the DNS API to directly schedule the to-be-processed object;

When it is determined that there is no locked parsing record, a parsing record related to the domain name corresponding to the object to be processed is added to the distributed cache database, and a locking operation is performed on the parsing record, wherein the locking operation is at least Contains at least one of an increase operation, a delete operation, and a modification operation.
The domain name resolution device according to claim 7 or 8, wherein the domain name resolution device further comprises: a sending unit, wherein:

The sending unit is configured to send a lock operation result to a production queue when the locking operation is performed successfully, so that the DNS API invokes the locking operation result in the production queue;

When the execution of the lock operation fails, the parsing record that fails the lock execution operation is sent to the parsing failure queue, so that the parsing record in the parsing failure queue is parsed again within a set time, wherein the parsing failure queue Used to store parsing records for parsing failures.
The domain name resolution device according to claim 6, wherein the parsing unit parses the parsing record in the parsing failure queue again, specifically for:

And determining, according to the set domain name scheduling sequence and the domain name corresponding to each parsing record in the parsing failure queue, an order in which the parsing records in the parsing failure queue are scheduled;

Determining, by the parsing record of the current schedule, whether the domain name corresponding to the parsing record exists in the distributed cache database;

If the domain name corresponding to the parsing record does not exist in the distributed cache database, returning a domain name error message to the external server;

If the domain name corresponding to the parsing record exists in the distributed cache database, performing a locking operation on the parsed record that is scheduled;

When the locking operation is successful, the parsing record obtained after the performing the locking operation is sent to the parsing record queue, so that the domain name service system DNS invokes the parsing record in the parsing record queue;

When the locking operation fails, the parsing record before the lock operation is executed is sent to the parsing failure queue, so that the parsing record in the parsing failure queue is parsed again within the set time.