WHOIS query method, system and storage medium

Abstract

The embodiment of the present invention discloses a WHOIS query method, which includes: receiving a domain name query request through a preset query client, obtaining a domain name to be queried corresponding to the domain name query request; calling a cache microservice gateway to perform a domain name query on the domain name to be queried, and obtaining a first query result, and the cache microservice gateway includes multiple first service nodes; judging whether the first query result contains domain name WHOIS information, if the first query result contains domain name WHOIS information, then returning the first query result to the query client; if the first query result does not contain domain name WHOIS information, then calling a domain name query microservice gateway to perform a domain name query, obtaining a second query result, and feeding back the second query result to the user, and the domain name query microservice gateway includes a number of second service nodes. In addition, the embodiment of the present invention also discloses a system and a storage medium for applying the WHOIS query method. The present invention can improve the query stability and security of WHOIS.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a WHOIS query method, system and storage medium. Background Art

[0002] A domain name is the name of a computer or computer group on the Internet, consisting of a string of names separated by dots, and is used to locate and identify computers during data transmission. With the development of the domain name industry, people often need to check whether a domain name is registered, as well as detailed information related to domain name registration.

[0003] The existing query service system uses the old WHOIS protocol (RFC3912) which was formulated and released by IETF in 2004. It adopts a single system, single-node server deployment, and single-node data database storage. However, the disadvantage of this method is that when the server fails or the database is lost or the data is damaged, the query service can no longer be provided, resulting in low stability and security of the query system.

[0004] It can be seen from this that how to achieve stable and secure WHOIS query is an urgent problem to be solved in existing technologies. Summary of the invention

[0005] In view of this, the present invention provides a WHOIS query method, system and storage medium, which are used to solve the problem of low security and stability of existing WHOIS query.

[0006] The specific technical solution of the embodiment of the present invention is:

[0007] In a first aspect, an embodiment of the present invention provides a WHOIS query method, including:

[0008] Receiving a domain name query request through a preset query client, and obtaining a domain name to be queried corresponding to the domain name query request;

[0009] Calling a cache microservice gateway to perform a domain name query on the domain name to be queried to obtain a first query result, wherein the cache microservice gateway includes multiple first service nodes;

[0010] Determine whether the first query result includes the domain name WHOIS information, and if the first query result includes the domain name WHOIS information, return the first query result to the query client;

[0011] If the first query result does not include the domain name WHOIS information, the domain name query microservice gateway is called to perform a domain name query, obtain a second query result, and feed back the second query result to the user. The domain name query microservice gateway includes a number of second service nodes.

[0012] Optionally, after receiving the domain name query request through a preset query client and obtaining the domain name to be queried corresponding to the domain name query request, the method further includes:

[0013] Determine whether the domain name to be queried conforms to the standard domain name format. If the domain name to be queried conforms to the standard domain name format, execute the step of calling the cache microservice gateway to perform a domain name query on the domain name to be queried;

[0014] If the domain name to be queried does not conform to the standard domain name format, the WHOIS query corresponding to the domain name query request is terminated.

[0015] Optionally, the calling of the cache microservice gateway to perform a domain name query on the domain name to be queried to obtain a first query result includes:

[0016] Establish an RPC connection between the cache microservice gateway and multiple Web server nodes to establish a first GRPC connection pool corresponding to the cache microservice gateway and the multiple Web server nodes;

[0017] Based on the first GRPC connection pool, transmitting the domain name to be queried to the first service node through the Web server node;

[0018] The first service node compares the domain name to be queried with the standard domain name stored in a preset cache database, and obtains the first query result according to the comparison result.

[0019] Optionally, the determining whether the first query result includes the domain name WHOIS information, and if the first query result includes the domain name WHOIS information, returning the first query result to the query client includes:

[0020] When the first query result includes the domain name WHOIS information, the first query result is returned to the Web server through the first service node, and the first query result is returned to the query client through the Web server node.

[0021] Optionally, if the first query result does not include the domain name WHOIS information, calling a domain name query microservice gateway to perform a domain name query includes:

[0022] When the first query result does not include the domain name WHOIS information, the Web server node sends a preset prompt message to the query client and executes the step of calling the domain name query microservice gateway to perform a domain name query.

[0023] Optionally, calling a domain name query microservice gateway to perform a domain name query to obtain a second query result includes:

[0024] Establish an RPC connection between the domain name query microservice gateway and the plurality of the Web server nodes to establish a second GRPC connection pool corresponding to the domain name query microservice gateway and the plurality of the Web server nodes;

[0025] Based on the second GRPC connection pool, transmitting the domain name to be queried to the second service node through the Web server node;

[0026] Sending query request data corresponding to the suffix of the domain name to be queried to an Internet Assigned Numbers Agency connected to the domain name query microservice gateway through the second service node, obtaining mapping data of the registry RDAP query address corresponding to the suffix of the domain name to be queried returned by the Internet Assigned Numbers Agency, and storing the mapping data in the cache database;

[0027] Sending, through the second service node, the HTTP request data corresponding to the domain name to be queried to a registry RDAP query server corresponding to the registry RDAP query address, where the registry RDAP query server includes a number of registered domain names;

[0028] When the registered domain name corresponding to the HTTP request data is included in the registry RDAP query server, the registry RDAP query server sends the domain name WHOIS information that complies with RDAP to the second service node, and the second service node uses the domain name WHOIS information as the second query result and returns it to the user;

[0029] When the registry RDAP query server does not include the registered domain name corresponding to the HTTP request data, the registry RDAP query server sends a preset HTTP status code to prompt the user that the domain name to be queried does not exist.

[0030] Optionally, calling the domain name query microservice gateway to perform a domain name query and obtaining the second query result further includes:

[0031] The domain name WHOIS information corresponding to the second query result is added to a preset domain name message queue, and the domain name message queue is stored in the cache database.

[0032] Optionally, the method further comprises:

[0033] The cache database and the domain name message queue are constructed based on a preset configuration file.

[0034] In a second aspect, an embodiment of the present invention provides a WHOIS query system, including a WHOIS client, a load balancing host and a backup host, multiple Web server nodes, a cache microservice gateway, and a domain name query microservice gateway, wherein:

[0035] The WHOIS client is used to receive a domain name query request;

[0036] The load balancing host and standby machine are used to send the domain name query request to the Web server node;

[0037] The Web server node is used to parse the domain name query request to obtain a domain name to be queried corresponding to the domain name query request;

[0038] The cache microservice gateway is used to perform a domain name query on the domain name to be queried to obtain a first query result;

[0039] When the first query result does not include the domain name WHOIS information, a domain name query is performed on the domain name to be queried through the domain name query microservice gateway to obtain a second query result.

[0040] In a third aspect, an embodiment of the present invention further provides a computer-readable storage medium, comprising computer instructions, which, when executed on a computer, enables the computer to execute the WHOIS query method as described in any one of the above items.

[0041] Implementing the embodiments of the present invention will have the following beneficial effects:

[0042] After adopting the above WHOIS query method, system and storage medium, after receiving the domain name query request, the corresponding domain name to be queried is obtained by parsing, based on the domain name to be queried, the domain name to be queried is first queried by calling the cache microservice gateway, and the corresponding first query result is obtained; and the first query result is judged whether it contains the domain name WHOIS information. When the domain name WHOIS information is contained, it indicates that the WHOIS query result corresponding to the domain name query request can be achieved by calling the cache microservice gateway; on the contrary, if the first query result does not contain the domain name WHOIS information, the domain name query microservice gateway is called to perform a domain name query, and the corresponding second query result is obtained as the WHOIS query result corresponding to the domain name query request. The embodiment of the present invention can ensure the stability of the WHOIS query by calling the cache microservice gateway or calling the domain name query microservice gateway to perform a domain name query. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] in:

[0045] Figure 1 A schematic diagram of the structure of a WHOIS query system in one embodiment;

[0046] Figure 2 A schematic diagram of a flow chart of a WHOIS query method in one embodiment;

[0047] Figure 3 A schematic diagram of a process for determining the format of a domain name to be queried in one embodiment;

[0048] Figure 4 A schematic diagram of a process for implementing WHOIS query by a cache microservice gateway in one embodiment;

[0049] Figure 5 A schematic diagram of a process for implementing WHOIS query by a domain name query microservice gateway described in an embodiment;

[0050] Figure 6 FIG. 1 is a schematic diagram of the internal structure of a computer device for running the above-mentioned WHOIS query method in an embodiment. DETAILED DESCRIPTION

[0051] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0052] In order to solve the problem in the prior art that WHOIS query cannot be performed when the server fails or the database is lost or the data is damaged during the WHOIS query process, a WHOIS query system is proposed in this embodiment. The WHOIS query system can implement WHOIS query operations through a cache microservice gateway and a domain name query microservice gateway.

[0053] Specifically, Figure 1As shown, the WHOIS query system includes a WHOIS client, a load balancing host and a backup machine, multiple Web server nodes, a cache microservice gateway, a domain name query microservice gateway, and multiple cache databases; after the WHOIS client receives a domain name query request, the load balancing host and the backup machine send the request to the cache microservice gateway or the domain name query microservice gateway through the Web server node, that is, the WHOIS query operation is implemented by calling the cache microservice gateway or the domain name query microservice gateway.

[0054] Among them, multiple service nodes are set in the cache microservice gateway and the domain name query microservice gateway; when the Web server node sends a domain name query request to the cache microservice gateway, the cache microservice gateway implements the WHOIS query operation through the multiple service nodes in combination with the cache database; and when the Web server node sends a domain name query request to the domain name query microservice gateway, the domain name query microservice gateway implements the WHOIS query operation by combining the Internet Assigned Numbers Authority and the registry RDAP (Registration Data Access Protocol) server.

[0055] In one embodiment, Figure 2 As shown, based on the above WHOIS query system, a corresponding WHOIS query method is proposed, including the following steps:

[0056] Step S10: receiving a domain name query request through a preset query client, and obtaining a domain name to be queried corresponding to the domain name query request.

[0057] Specifically, the query client refers to a terminal device such as a mobile phone, tablet, computer, PDA, notebook or desktop, or a preset APP or browser on a terminal device such as a mobile phone, tablet, computer, etc., which is not limited or fixed in this embodiment of the present invention.

[0058] A domain name query request refers to a domain name entered by a user through the above-mentioned mobile phones, tablets, computers and other terminal devices. For example, www.baidu.com is a common domain name, and others may be .COM, .CN, .NET, .ORG, etc. To obtain the domain name to be queried corresponding to the domain name query request, "PING" may be entered in a DOS system, a LINUX system, etc. for analysis, that is, the domain name query request is analyzed to obtain the corresponding domain name to be queried, so as to facilitate subsequent WHOIS query operations.

[0059] In one embodiment, after the domain name to be queried is determined, the format of the domain name to be queried needs to be determined, such as Figure 3 As shown, the following steps are included:

[0060] Step S20: Determine whether the domain name to be queried conforms to the standard domain name format. If the domain name to be queried conforms to the standard domain name format, execute the step of calling the cache microservice gateway to perform a domain name query on the domain name to be queried; and Step S21: If the domain name to be queried does not conform to the standard domain name format, terminate the WHOIS query corresponding to the domain name query request.

[0061] The standard domain name format refers to the corresponding format designated by the international community for use in achieving network security. Generally, a domain name can only include 26 letters, 10 numbers from 0 to 9, and the hyphen "-". For domain names in different national languages ​​such as Chinese, Japanese, and Korean, it is also possible to protect and must contain the text characters corresponding to that country.

[0062] For example, the general domain name format is www.baidu.com, where the domain name is a second-level domain name, baidu is the main body of the domain name, .com is the suffix of the domain name, and com itself is an international domain name. It can be seen that only when the domain name conforms to the preset standard domain name format can the corresponding WHOIS query request be made.

[0063] It can be seen that in terminal devices such as mobile phones, tablets, and computers, users can initiate domain name query requests through HTTP such as browsers, where users can initiate domain name requests by, for example, clicking a mouse or by touch clicking on the terminal device.

[0064] By receiving the corresponding domain name query request through query terminals such as mobile phones, tablets, and computers, and parsing the domain name query request, the format of the corresponding domain name to be queried is judged, and only when the query domain name conforms to the standard domain name format can the corresponding WHOIS query operation be performed, which is beneficial to improving the security of the network and the security of WHOIS query.

[0065] Step S11: calling a cache microservice gateway to perform a domain name query on the domain name to be queried to obtain a first query result, wherein the cache microservice gateway includes multiple first service nodes.

[0066] Generally, after a query request is entered in a terminal device such as a mobile phone, tablet, or computer, the corresponding request will be sent to the gateway, and the gateway will implement corresponding query, control, and other operations based on the request. Based on this, after a user enters a corresponding domain name query request through a terminal device such as a mobile phone, tablet, or computer, the domain name query request will be transmitted to the corresponding gateway, and the WHOIS query operation will be implemented through the gateway.

[0067] In one embodiment, a domain name query operation is performed on the domain name to be queried through a cache microservice gateway to obtain a corresponding first query result. Specifically, multiple first service nodes are set in each cache microservice gateway, and a preset cache database storing multiple domain names is traversed and queried through the first service node to obtain a first query result corresponding to the domain name to be queried.

[0068] In the process of obtaining the first query result, the first service node compares the domain name to be queried with all the domain names in the cache database, so as to determine the first query result corresponding to the domain name to be queried.

[0069] In addition, since there are many domain name query requests at the same time point, in order to ensure the smoothness and balance of the domain name query operation, in the process of performing WHOIS query through the first service node, all domain name query requests received from terminal devices such as mobile phones, tablets, and computers are sent to multiple first service nodes according to a balancing strategy, so as to ensure the work balance of each first service node and the utilization efficiency of each first service node.

[0070] In one embodiment, Figure 4 As shown, the steps of performing a WHOIS query by calling the cache microservice gateway include:

[0071] Step S30: Establish an RPC connection between the cache microservice gateway and multiple Web server nodes to establish a first GRPC connection pool corresponding to the cache microservice gateway and the multiple Web server nodes.

[0072] Since there may be multiple domain name query requests at the same time point, that is, different Web servers will send different domain name requests to the cache microservice gateway at the same time to perform corresponding WHOIS queries, based on this, an RPC (Romote Procedure Call) connection is constructed between the cache microservice gateway and multiple Web server nodes; and a GPRC (Group Romote Procedure Call) connection pool is further constructed between the cache microservice gateway and the Web server nodes, which is recorded as the first GRPC connection pool.

[0073] Among them, building the GRPC connection pool specifically injects the corresponding service address through a preset configuration file; for example, when a terminal device such as a computer or a mobile phone is started, the corresponding file configuration is generally performed to obtain a Web server that the terminal device such as the computer or mobile phone can connect to.

[0074] In practice, the Web server nodes are arranged in a load balancing system including a host machine, a backup machine and a plurality of Web server nodes; and the plurality of Web server nodes can be dynamically increased or decreased according to actual needs to enhance the flexibility of domain name query.

[0075] In a specific embodiment, by constructing the first GRPC connection pool, it can be ensured that if there is a query result corresponding to the domain name to be queried in the first GRPC connection pool, the corresponding Web server and the cache microservice gateway can be directly called by multiplexing, which is conducive to shortening the connection time between the cache microservice gateway and multiple Web server nodes, thereby improving the speed and efficiency of the query. Furthermore, by reusing the first GRPC connection pool, the resource overhead of frequent creation and closing of connections is reduced, which is conducive to improving the rapid response of the network.

[0076] Step S31: Based on the first GRPC connection pool, the domain name to be queried is transmitted to the first service node through the Web server node; and Step S32: The domain name to be queried is compared with the standard domain name stored in a preset cache database through the first service node, and the first query result is obtained according to the comparison result.

[0077] Specifically, when the Web server node receives the domain name to be queried sent by the above-mentioned terminal device, it distributes all the domain names to be queried to multiple first service nodes in the cache microservice gateway in a balancing strategy; the first service node traverses the domain name to be queried in all cache databases, that is, compares the domain name to be queried with the standard domain name in the cache database. After the comparison operation, if there is a standard domain name that matches the domain name to be queried, the standard domain name is returned to the Web server node as the first query result, and is returned by the Web server node to the terminal, that is, returned to the user.

[0078] On the contrary, if no standard domain name matching the domain name to be queried is found after the comparison operation of the first service node, other preset indication information is returned to the terminal device / user to facilitate further implementation of the domain name query operation.

[0079] In addition, since the Web server nodes can be dynamically increased or decreased according to actual needs, it means that the first GRPC connection pool can be dynamically increased or decreased. For example, when a first service node and / or Web server node fails, the corresponding first service node and / or Web server node can be deleted; conversely, if the domain name query operation is not performed through the first service node and / or Web server node in the first GRPC connection pool, the newly added first service node / or Web server node can be added to the first GRPC connection pool, thereby realizing the capacity expansion operation of the first GRPC connection pool.

[0080] It should be noted that the way in which the Web server node sends the domain name to be queried to the cache microservice gateway is that the Web server node constructs the domain name information to be queried into a service request data object and then sends it to the cache microservice gateway.

[0081] Furthermore, the cache database is designed in a distributed manner to realize distributed caching of standard domain names. For example, standard domain names with different suffixes can be distributed cached according to the different suffixes of different domain names. This can reduce the storage pressure of the cache server on the one hand; on the other hand, it facilitates fast and efficient queries; and distributed operations can be realized by building corresponding mirror cache databases in different regions, which is beneficial to improving data security.

[0082] From the above, it can be seen that through the first GRPC connection pool built based on Web server nodes and cache microservice gateways, flexible operation of domain name query can be realized to improve the anti-concurrency capability in the domain name query process; and the domain name query requests are evenly distributed through a balancing strategy, which can reduce the pressure on each Web server node and / or the first service node, and ensure the high concurrency processing capability of the domain name query process.

[0083] Step S12: determining whether the first query result includes the domain name WHOIS information; if the first query result includes the domain name WHOIS information, returning the first query result to the query client.

[0084] Domain names need to be registered to ensure the reasonable use of domain names, that is, to ensure the security and stability of the network, based on the existing domain name usage standards, it is necessary to determine whether a domain name is registered. Generally, the domain name is determined by whether it contains the domain name WHOIS information, where the domain name WHOIS information corresponding to the domain name to be queried complies with RDAP.

[0085] Based on this, in this embodiment, only when the first query result includes the domain name WHOIS information, can the first query result be used as the WHOIS query result corresponding to the domain name query request, that is, the domain name query result; thereby, the first query result is returned to the Web server node, and then the first query result is returned to the query client, that is, the user, through the Web server node; thereby completing the entire WHOIS query operation.

[0086] By judging the domain name WHOIS information of the first query result of the cache microservice gateway, that is, judging whether the standard domain name stored in the cache database corresponding to the first query result is registered, the legal application of the domain name is ensured, that is, the security and stability of the network are guaranteed.

[0087] Step S13: If the first query result does not contain the domain name WHOIS information, call the domain name query microservice gateway to perform a domain name query, obtain a second query result, and feed back the second query result to the user, and the domain name query microservice gateway includes a number of second service nodes.

[0088] Specifically, when the first query result does not contain the domain name WHOIS information, it is impossible to judge whether the standard domain name corresponding to the first query result is legal; or it is impossible to judge whether the standard domain name corresponding to the domain name to be queried complies with RDAP. Based on this, this embodiment performs a domain name query operation by calling the domain name query microservice gateway to obtain the corresponding second query result, and after returning the corresponding second query result to the Web server node, the second query result is returned to the terminal device, that is, the user, through the Web server node, so that the user knows the actual WHOIS query result.

[0089] The first query result does not include the domain name WHOIS information, including: the cache database does not originally include the domain name WHOIS information corresponding to the domain name to be queried, and the WHOIS information corresponding to the domain name to be queried has expired.

[0090] It should be noted that in order to improve the stability and balance of the query, a number of second service nodes are set in the domain name query microservice gateway, and the domain name query microservice gateway implements the query operation of the second query result based on the number of second service nodes.

[0091] In one embodiment, Figure 5 As shown, calling the domain name query microservice gateway to perform domain name query specifically includes the following steps:

[0092] Step S40: Establish an RPC connection between the domain name query microservice gateway and the multiple Web server nodes to establish a second GRPC connection pool corresponding to the domain name query microservice gateway and the multiple Web server nodes.

[0093] Similar to the above construction of the cache microservice gateway and the first GRPC connection pool between multiple Web server nodes, the second GRPC connection pool is constructed by injecting the corresponding service address through a preset configuration file; for example, when a terminal device such as a computer or a mobile phone is started, the corresponding file configuration is generally performed to obtain a Web server that the terminal device such as the computer or mobile phone can connect to.

[0094] That is, by constructing the second GRPC connection pool, it can be ensured that if there is a query result corresponding to the domain name to be queried in the second GRPC connection pool, the corresponding Web server and the domain name query microservice gateway can be directly called by multiplexing, which is conducive to shortening the connection time between the domain name query microservice gateway and multiple Web server nodes, thereby improving the speed and efficiency of the query. Furthermore, by reusing the second GRPC connection pool, the resource overhead of frequent creation and closing of connections is reduced, which is conducive to improving the rapid response of the network.

[0095] In addition, the Web server nodes and the second service nodes can be dynamically increased or decreased according to actual needs, which can help improve the flexibility of domain name query through the domain name query microservice gateway.

[0096] Step S41: Based on the second GRPC connection pool, the domain name to be queried is transmitted to the second service node through the Web server node.

[0097] Specifically, when the first query result is returned from the cache database by calling the cache microservice gateway to query the domain name, the first query result does not include the domain name WHOIS information. At this time, the Web server node distributes the corresponding domain name to be queried to multiple second service nodes in the domain name query microservice gateway in a balanced strategy.

[0098] Step S42: Send query request data corresponding to the suffix of the domain name to be queried to the Internet Assigned Numbers Agency connected to the domain name query microservice gateway through the second service node, and obtain the mapping data of the registry RDAP query address corresponding to the suffix of the domain name to be queried returned by the Internet Assigned Numbers Agency; and Step S43: Send the HTTP request data corresponding to the domain name to be queried to the registry RDAP query server corresponding to the registry RDAP query address through the second service node, and the registry RDAP query server includes a number of registered domain names.

[0099] For the coordination and security of the global network, domain name registration is generally classified according to different suffixes, which can be specifically coordinated by the Internet Assigned Numbers Authority (IANA). Based on this, the suffix of the domain name to be queried is sent to IANA through the second service node, so as to obtain the mapping data of the registry RDAP query address corresponding to the suffix of the domain name to be queried, and the mapping data corresponds to the data in the registry RDAP server, wherein the registry RDAP server contains all registered domain names, so that it is possible to query whether the domain name to be queried is registered.

[0100] Among them, since the Web server nodes can be dynamically increased or decreased according to actual needs, it means that the second GRPC connection pool can be dynamically increased or decreased. For example, when a second service node and / or Web server node fails, the corresponding second service node and / or Web server node can be deleted; conversely, if the domain name query operation is not performed through the second service node and / or Web server node in the second GRPC connection pool, the newly added second service node / or Web server node can be added to the second GRPC connection pool, thereby realizing the expansion operation of the second GRPC connection pool.

[0101] It should be noted that the way in which the Web server node sends the domain name to be queried to the domain name query microservice gateway is: the Web server node constructs the domain name information to be queried into a service request data object and then sends it to the domain name query microservice gateway.

[0102] At the same time, after obtaining the mapping data of the registry RDAP query address corresponding to the domain name suffix to be queried, the mapping data can be stored in the cache database; the specific storage method in the cache database can be performed according to the storage method of different suffixes, so as to facilitate the next WHOIS query operation through the Internet Assigned Numbers Authority.

[0103] From the above, it can be seen that through the second GRPC connection pool constructed based on the Web server node and the domain name query microservice gateway, when the first query result is obtained by querying the cache microservice gateway, but the first query result does not include the domain name WHOIS information, the corresponding domain name to be queried is queried whether it is registered, so as to obtain the corresponding second query result; that is, this embodiment enriches the function of WHOIS query, and can perform the corresponding WHOIS query by calling the domain name query microservice gateway when a network failure occurs, for example, when the WHOIS query cannot be performed by calling the cache microservice gateway, thereby improving the stability of the WHOIS query.

[0104] Moreover, among the multiple second service nodes included in the domain name query microservice gateway, when a second service node fails, it can be deleted at any time, and other second service nodes can be called to perform WHOIS query operations, which is conducive to ensuring the stability of the query; and by integrating domain names according to different suffixes and storing them in the cache database, it is conducive to improving the query efficiency and user experience and shortening the query time.

[0105] In addition, by evenly distributing domain name query requests through a balancing strategy, the pressure on each Web server node and / or the second service node can be reduced, ensuring the high concurrent processing capability of the domain name query process; and using the new generation of RDAP as the WHOIS query protocol can better support internationalization, thereby supporting the data expansion mechanism.

[0106] Step S44: when the registered domain name corresponding to the HTTP request data is included in the registry RDAP query server, the registry RDAP query server sends the domain name WHOIS information that complies with RDAP to the second service node, and the second service node uses the domain name WHOIS information as the second query result and returns it to the user; and Step S45: when the registered domain name corresponding to the HTTP request data is not included in the registry RDAP query server, the registry RDAP query server sends a preset HTTP status code to prompt the user that the domain name to be queried does not exist.

[0107] Specifically, the second service node sends HTTP request data to the RADP address of the registry. If the domain name to be queried has not been registered at the registry's RDAP server, data indicating that the domain name does not exist is returned to the Web server node, as well as a corresponding HTTP status code, which may be 404, etc.; if the domain name to be queried has been registered at the registry's RDAP server, the registry's RDAP server returns corresponding JSON serialized data that complies with RDAP; if the JSON serialized data includes the RDAP address of the registrar of the domain name to be queried, it means that the domain name WHOIS information of the domain name can be obtained by querying the RDAP server of the domain name registrar; if it does not include the RDAP address of the domain name registrar, it means that the domain name WHOIS information that complies with RDAP sent by the registry's RDAP query server is complete, and the domain name query operation is completed.

[0108] By implementing the domain name query operation through the above-mentioned domain name query microservice gateway, it can be seen that the flexibility of domain name query can be improved, and by using the new generation of WHOIS protocol, it can better support internationalization and data expansion mechanism.

[0109] In one embodiment, in order to facilitate domain name query and improve the speed and efficiency of domain name query, after each corresponding WHOIS query operation is implemented through the domain name query microservice gateway, the domain name WHOIS information corresponding to the second query result can be added to the preset domain name message queue; specifically, the domain name WHOIS information is stored in the cache database, so that the query operation of the corresponding domain name to be queried can be implemented only through the cache microservice gateway, which is conducive to improving the speed and efficiency of domain name query.

[0110] In addition, it should be specially noted that the above-mentioned cache database and domain name queue messages are constructed through preset configuration files, which are specifically implemented during the startup process of the terminal device and will not be elaborated here.

[0111] In summary, this embodiment can realize the WHOIS query operation by combining the cache microservice gateway and the domain name query microservice gateway; wherein, after each WHOIS query is performed through the domain name query microservice gateway, the corresponding query result, that is, the corresponding domain name WHOIS information and other information corresponding to the domain name can be stored in the cache database, so that when the WHOIS query is performed next time, if the same domain name is encountered, it is only necessary to call the cache microservice gateway to realize a fast WHOIS query operation, which can effectively improve the query efficiency.

[0112] In addition, by integrating the cache microservice gateway and the domain name query service gateway, the cache microservice gateway, the domain name query service gateway, and the cache database all use a distributed approach to implement query operations, which is beneficial to improving data security, and is beneficial to the dynamic expansion of queries and improving the high concurrency capabilities of queries.

[0113] Based on the same inventive concept, an embodiment of the present invention provides a WHOIS query system 100. The WHOIS query system 100 implements a WHOIS query operation based on the WHOIS query method described in any of the above embodiments.

[0114] In one embodiment, Figure 1As shown, the WHOIS query system 100 includes: a WHOIS client, a load balancing host and a standby machine, multiple Web server nodes, a cache microservice gateway and a domain name query microservice gateway, wherein the WHOIS client is used to receive a domain name query request; the load balancing host and the standby machine are used to send the domain name query request to the Web server node; the Web server node is used to obtain and parse the domain name query request to obtain a domain name to be queried corresponding to the domain name query request; the cache microservice gateway is used to perform a domain name query on the domain name to be queried to obtain a first query result; when the first query result does not contain the domain name WHOIS information, a domain name query is performed on the domain name to be queried through the domain name query microservice gateway to obtain a second query result.

[0115] Among them, the cache microservice gateway is provided with corresponding multiple first service nodes, and the domain name query microservice gateway is provided with corresponding multiple second service nodes; specifically, the Web server node, multiple first service nodes, and multiple second service nodes all adopt a distributed design, so that the cache microservice gateway and the domain name query microservice gateway can be dynamically increased or decreased, so as to call resources according to actual conditions and realize the rational application of resources.

[0116] In addition, since the WHOIS query system 100 realizes the integration of the cache microservice gateway and the domain name query microservice gateway, in order to realize the mutual switching between the two and ensure the smoothness of the domain name query, a scheduling unit is also provided to realize the switching between the cache microservice gateway and the domain name query microservice gateway according to actual needs to obtain the best domain name query operation.

[0117] It should be noted that the implementation of the WHOIS query system 100 is consistent with the implementation concept of the above WHOIS query method, and the principle of implementing the WHOIS query will not be repeated here. For details, please refer to the corresponding content in the above WHOIS query method.

[0118] After adopting the above WHOIS query method, system and storage medium, after receiving the domain name query request, the corresponding domain name to be queried is obtained by parsing, based on the domain name to be queried, the domain name to be queried is first queried by calling the cache microservice gateway, and the corresponding first query result is obtained; and the first query result is judged whether it contains the domain name WHOIS information. When the domain name WHOIS information is contained, it indicates that the WHOIS query result corresponding to the domain name query request can be achieved by calling the cache microservice gateway; on the contrary, if the first query result does not contain the domain name WHOIS information, the domain name query microservice gateway is called to perform a domain name query, and the corresponding second query result is obtained as the WHOIS query result corresponding to the domain name query request. The embodiment of the present invention can ensure the stability of the WHOIS query by calling the cache microservice gateway or calling the domain name query microservice gateway to perform a domain name query.

[0119] Figure 6 FIG. 1 shows an internal structure diagram of a computer device in an embodiment. The computer device may be a server or a terminal. Figure 6 As shown, the computer device includes a processor, a memory and a network interface connected via a system bus. The memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program. When the computer program is executed by the processor, the processor may implement the WHOIS query method. The internal memory may also store a computer program. When the computer program is executed by the processor, the processor may implement the WHOIS query method. Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the present application scheme, and does not constitute a limitation on the computer device to which the present application scheme is applied. The specific computer device may include Figure 6 More or fewer components may be shown, or certain components may be combined, or may have a different arrangement of components.

[0120] In one embodiment, the WHOIS query method provided by the present application can be implemented in the form of a computer program. The computer program can be Figure 6The computer device shown in the figure is run on the computer device. The memory of the computer device can store various program modules that constitute the WHOIS query system. For example, a Web server node, etc. In one embodiment, a computer device is proposed, including a memory and a processor and the above-mentioned WHOIS query system 100, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the following steps: receiving a domain name query request through a preset query client, and obtaining a domain name to be queried corresponding to the domain name query request; calling a cache microservice gateway to perform a domain name query on the domain name to be queried, and obtaining a first query result, wherein the cache microservice gateway includes a plurality of first service nodes; determining whether the first query result contains the domain name WHOIS information, and if the first query result contains the domain name WHOIS information, returning the first query result to the query client; if the first query result does not contain the domain name WHOIS information, calling a domain name query microservice gateway to perform a domain name query, obtaining a second query result, and feeding back the second query result to the user, wherein the domain name query microservice gateway includes a plurality of second service nodes.

[0121] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0122] The above disclosure is only the preferred embodiment of the present invention, which certainly cannot be used to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims

1. A WHOIS query method, characterized in that: include: Receiving a domain name query request through a preset query client, and obtaining a domain name to be queried corresponding to the domain name query request; Calling a cache microservice gateway to perform a domain name query on the domain name to be queried to obtain a first query result, wherein the cache microservice gateway includes multiple first service nodes; Determine whether the first query result includes the domain name WHOIS information, and if the first query result includes the domain name WHOIS information, return the first query result to the query client; If the first query result does not include the domain name WHOIS information, the domain name query microservice gateway is called to perform a domain name query, obtain a second query result, and feed back the second query result to the user. The domain name query microservice gateway includes a number of second service nodes.

2. The WHOIS query method according to claim 1, characterized in that: After receiving the domain name query request through the preset query client and obtaining the domain name to be queried corresponding to the domain name query request, the method includes: Determine whether the domain name to be queried conforms to the standard domain name format. If the domain name to be queried conforms to the standard domain name format, execute the step of calling the cache microservice gateway to perform a domain name query on the domain name to be queried; If the domain name to be queried does not conform to the standard domain name format, the WHOIS query corresponding to the domain name query request is terminated.

3. The WHOIS query method according to claim 1, characterized in that: The calling cache microservice gateway performs a domain name query on the domain name to be queried to obtain a first query result, including: Establish an RPC connection between the cache microservice gateway and multiple Web server nodes to establish a first GRPC connection pool corresponding to the cache microservice gateway and the multiple Web server nodes; Based on the first GRPC connection pool, transmitting the domain name to be queried to the first service node through the Web server node; The first service node compares the domain name to be queried with the standard domain name stored in a preset cache database, and obtains the first query result according to the comparison result.

4. The WHOIS query method according to claim 3, characterized in that: The determining whether the first query result includes the domain name WHOIS information, and if the first query result includes the domain name WHOIS information, returning the first query result to the query client includes: When the first query result includes the domain name WHOIS information, the first query result is returned to the Web server node through the first service node, and the first query result is returned to the query client through the Web server node.

5. The WHOIS query method according to claim 3, characterized in that: If the first query result does not include the domain name WHOIS information, calling the domain name query microservice gateway to perform a domain name query, including: When the first query result does not include the domain name WHOIS information, the Web server node sends a preset prompt message to the query client and executes the step of calling the domain name query microservice gateway to perform a domain name query.

6. The WHOIS query method according to claim 5, characterized in that: The domain name query microservice gateway is called to perform a domain name query to obtain a second query result, including: Establish an RPC connection between the domain name query microservice gateway and the plurality of the Web server nodes to establish a second GRPC connection pool corresponding to the domain name query microservice gateway and the plurality of the Web server nodes; Based on the second GRPC connection pool, transmitting the domain name to be queried to the second service node through the Web server node; Sending query request data corresponding to the suffix of the domain name to be queried to an Internet Assigned Numbers Agency connected to the domain name query microservice gateway through the second service node, obtaining mapping data of the registry RDAP query address corresponding to the suffix of the domain name to be queried returned by the Internet Assigned Numbers Agency, and storing the mapping data in the cache database; Sending, through the second service node, the HTTP request data corresponding to the domain name to be queried to a registry RDAP query server corresponding to the registry RDAP query address, where the registry RDAP query server includes a number of registered domain names; When the registered domain name corresponding to the HTTP request data is included in the registry RDAP query server, the registry RDAP query server sends the domain name WHOIS information that complies with RDAP to the second service node, and the second service node uses the domain name WHOIS information as the second query result and returns it to the user; When the registry RDAP query server does not include the registered domain name corresponding to the HTTP request data, the registry RDAP query server sends a preset HTTP status code to prompt the user that the domain name to be queried does not exist.

7. The WHOIS query method according to claim 3, characterized in that: The method further includes calling the domain name query microservice gateway to perform a domain name query and obtaining the second query result: The domain name WHOIS information corresponding to the second query result is added to a preset domain name message queue, and the domain name message queue is stored in the cache database.

8. The WHOIS query method according to claim 7, characterized in that: The method further comprises: The cache database and the domain name message queue are constructed based on a preset configuration file.

9. A WHOIS query system, characterized in that: It includes WHOIS client, load balancing host and backup machine, multiple web server nodes, cache microservice gateway and domain name query microservice gateway, among which: The WHOIS client is used to receive a domain name query request; The load balancing host and standby machine are used to send the domain name query request to the Web server node; The Web server node is used to parse the domain name query request to obtain a domain name to be queried corresponding to the domain name query request; The cache microservice gateway is used to perform a domain name query on the domain name to be queried to obtain a first query result; When the first query result does not include the domain name WHOIS information, a domain name query is performed on the domain name to be queried through the domain name query microservice gateway to obtain a second query result.

10. A computer-readable storage medium comprising computer instructions, which, when executed on a computer, enables the computer to execute the WHOIS query method according to any one of claims 1 to 8.

Images