CN110401686B - WHOIS query method, device, equipment and storage medium thereof - Google Patents
WHOIS query method, device, equipment and storage medium thereof Download PDFInfo
- Publication number
- CN110401686B CN110401686B CN201810382342.2A CN201810382342A CN110401686B CN 110401686 B CN110401686 B CN 110401686B CN 201810382342 A CN201810382342 A CN 201810382342A CN 110401686 B CN110401686 B CN 110401686B
- Authority
- CN
- China
- Prior art keywords
- query
- server
- whois
- domain name
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a WHOIS query method, a device, equipment and a storage medium thereof. The method comprises the following steps: the method is executed by an AMQP server, and receives a query domain name which is obtained by analyzing a WHOIS client from a WHOIS query request; determining a WHOIS server address corresponding to the top-level domain of the query domain name according to the top-level domain; acquiring a first query server set corresponding to the WHOIS server address according to the WHOIS server address; selecting any one first query server in the first query server set, and sending a query domain name to a WHOIS server corresponding to the address of the WHOIS server through the first query server; receiving a query result returned by the first query server, wherein the query result is information returned by the WHOIS server according to the query domain name; and adjusting the query strategy based on the query result to acquire WHOIS query information corresponding to the query domain name. According to the technical scheme of the embodiment of the application, the time loss caused by a WHOIS server blocking mechanism is greatly reduced, and therefore the user experience is improved.
Description
Technical Field
The present application relates generally to the field of computers, and more particularly, to the field of computer information processing, and more particularly, to a WHOIS query method, apparatus, device, and storage medium thereof.
Background
The WHOIS service is typically provided by the WHOIS system according to IETF standard requirements. The WHOIS system is a Client/Server system. Wherein the WHOIS client is mainly responsible for:
1) providing a user interface for accessing the WHOIS system;
2) generating a query and transmitting it to the WHOIS server in an appropriate format;
3) and receiving the response returned by the WHOIS server and outputting the response in a form readable by the user.
The WHOIS server is then primarily responsible for receiving requests from the WHOIS client and returning response data. Generally, the WHOIS server may receive three types of information queries: contacts, host, and domain names. The output of the WHOIS server should be consistent and stable for the same query.
However, the WHOIS server typically employs a blocking mechanism for a large number of queries over a short period of time, which results in a poor user experience.
Disclosure of Invention
In view of the above-mentioned drawbacks and deficiencies in the prior art, it is desirable to provide a technical solution for providing WHOIS query information for a WHOIS server lockout mechanism.
In a first aspect, an embodiment of the present application provides a WHOIS query method, where the method is performed by an advanced message queue protocol AMQP server, and the method includes:
receiving a query domain name, wherein the query domain name is obtained by analyzing a WHOIS client from a WHOIS query request;
determining a WHOIS server address corresponding to the top-level domain of the query domain name according to the top-level domain;
acquiring a first query server set corresponding to the WHOIS server address according to the WHOIS server address;
selecting any one first query server in the first query server set, and sending a query domain name to a WHOIS server corresponding to the address of the WHOIS server through the first query server;
receiving a query result returned by the first query server, wherein the query result is information returned by the WHOIS server according to the query domain name;
and adjusting the query strategy based on the query result to acquire WHOIS query information corresponding to the query domain name.
In a second aspect, an embodiment of the present application provides a WHOIS query apparatus, which is executed by an advanced message queue protocol AMQP server, and includes:
the first receiving module is used for receiving a query domain name, wherein the query domain name is obtained by analyzing a WHOIS query request by a WHOIS client;
the determining module is used for determining the address of the WHOIS server corresponding to the top-level domain of the query domain name according to the top-level domain;
The acquisition module is used for acquiring a first query server set corresponding to the WHOIS server address according to the WHOIS server address;
the selection module is used for selecting any one first query server in the first query server set and sending the query domain name to the WHOIS server corresponding to the address of the WHOIS server through the first query server;
the second receiving module is used for receiving a query result returned by the first query server, wherein the query result is information returned by the WHOIS server according to the query domain name;
and the adjusting module is used for adjusting the query strategy based on the query result so as to obtain WHOIS query information corresponding to the query domain name.
In a third aspect, embodiments of the present application provide a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the method as described in embodiments of the present application when executing the program.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, the computer program being configured to:
which when executed by a processor implements a method as described in embodiments of the present application.
According to the WHOIS query scheme provided by the embodiment of the application, the query strategy is adjusted by returning the information type of the query result to the AMQP server through the query server, so that the experience degree of a user is improved, the data processing speed is increased, and the time loss caused by a WHOIS server blocking mechanism is greatly reduced.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a schematic flowchart illustrating a WHOIS query method provided in an embodiment of the present application;
FIG. 2 shows a schematic flow chart of step 160 provided by another embodiment of the present application;
fig. 3 illustrates an exemplary block diagram of a WHOIS query apparatus provided in an embodiment of the present application;
FIG. 4 illustrates an exemplary block diagram of an adjustment module 360 provided in accordance with another embodiment of the present application;
FIG. 5 illustrates a schematic diagram of a computer system suitable for use in implementing a server according to embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a WHOIS query method provided in an embodiment of the present application. The method is performed by an advanced message queue protocol server.
As shown in fig. 1, the method includes:
In the embodiment of the application, a plurality of users send WHOIS query requests to a high-level message queue protocol server through a WHOIS client. The advanced message queue protocol server obtains the query domain name from the WHOIS query request. Wherein the WHOIS client may also be a WHOIS WEB page. The manner in which the user enters the WHOIS query request may be accomplished through interaction with the client.
The amqp (advanced Message Queuing protocol) is an application layer standard advanced Message Queuing protocol for providing unified Message service, is an open standard of the application layer protocol, and is designed for a Message-oriented middleware. The client and the message middleware based on the protocol can transfer messages and are not limited by conditions of different products, different development languages and the like of the client/middleware.
And step 120, determining the address of the WHOIS server corresponding to the top-level domain of the query domain name according to the top-level domain.
In the embodiment of the application, after receiving a plurality of WHOIS query requests, the AMQP server may obtain a query domain name from the WHOIS query requests, and then determine a corresponding WHOIS server address according to a top-level domain of the query domain name. The top level domain can be understood as the last part of the domain name, the letter combination after the last point of the domain name, and the type of the top level domain can be a top level domain of a country level region, a general top level domain, an infrastructure top level domain, a test top level domain and the like.
For example, on the Internet, top-level domain names such as ". com" and ". org".
And step 130, acquiring a first query server set corresponding to the WHOIS server address according to the WHOIS server address.
The mapping relationship between the query server and the WHOIS server may be established in the AMQP server according to various data structures. For example, a mapping relationship between the query server and an IP address is established according to the IP address provided by a certain WHOIS service provider. Wherein the same WHOIS service provider may provide multiple WHOIS server addresses. Each WHOIS server address may correspond to multiple query servers. Multiple query servers associated with the same WHOIS server address may be referred to as a query server set. For the sake of distinction, it may be defined by the terms first, second, etc., but not by the order of operations. For example, the first set of query servers and the second set of query servers may all be associated with the same WHOIS server address, and for example, the first set of query servers and the second set of query servers may also be referred to as a first subset of query servers or a second subset of query servers.
And the AMQP server selects one query server from the first query server set according to a preset selection algorithm, and the query server is used for sending the query domain name to the WHOIS server.
And 150, receiving a query result returned by the first query server, wherein the query result is information returned by the WHOIS server according to the query domain name.
After receiving the information returned by the query server, the AMQP server identifies the information. Because the same WHOIS server is queried for multiple times in a short time, the blocking mechanism of the WHOIS server blocks part or all query servers related to the WHOIS server, so that the AMQP server cannot acquire the result of the query request. For example, if one of the query servers associated with the WHOIS server is blocked, or all of the query servers associated with the WHOIS server are blocked, the AMQP server may identify the blocked result and then use a corresponding query policy to further obtain the result of the query request.
In the embodiment of the present application, the query result returned by the query server may be, for example, that part of the plurality of query servers associated with the WHOIS server is blocked, or that all query servers associated with the WHOIS server are blocked. Based on partial blocking or full blocking, the AMQP server may enable different query policies to further obtain WHOIS query information corresponding to the queried domain name. For example, if one of the plurality of query servers associated with the WHOIS server is blocked, the AMQP server may select another of the plurality of query servers to further forward the query request to the WHOIS server. Or after all the query servers associated with the WHOIS server are blocked, the AMQP server may also implement WHOIS query by starting a new query server, thereby improving user experience and greatly reducing query delay caused by a blocking mechanism.
Based on the above embodiment, the query policy is further adjusted by the query result to provide the query result to the WHOIS client. Referring to fig. 2, fig. 2 shows a schematic flow chart of the present application with respect to step 160.
As shown in figure 2 of the drawings, in which,
at step 210, the information type of the query result is identified.
and step 230, adjusting the query strategy according to the analysis result to acquire WHOIS query information corresponding to the queried domain name.
According to the method and the device, different query strategies are triggered by identifying the information type of the query result returned by the query server through the AMQP server. For example, the query server returns indication information to the AMQP server, which may be set as specified by the AMQP protocol, the contents of which include information indicating the status of each query server in the first set of query servers. The status of the query server is blocked, e.g. by the WHOIS server, with an identification information indication, or a status value indication, e.g. in the form of a binary value, e.g. 1 for blocking and 0 for unblocking.
The method comprises the steps of inquiring a database, acquiring ports of a plurality of inquiry servers associated with a certain WHOIS server address from the database, identifying whether the inquiry server corresponding to the port is blocked by the WHOIS server or not through a state identifier corresponding to the port, further judging whether the ports of the plurality of inquiry servers associated with the WHOIS server address are all blocked or not, and triggering different inquiry strategies based on the judgment result to improve the inquiry speed.
Step 230 may also include:
step 2301, if the analysis result is that each first query server in the first query server set is in a state of being blocked by a WHOIS server, selecting any second query server in the second query server set, and establishing communication with the WHOIS server through the second query server to obtain WHOIS query information corresponding to the queried domain name.
Step 2302, if the analysis result is that a part of the first query servers in the first query server set are in a state of being blocked by the WHOIS server, selecting any one of the first query servers in another part of the first query server set, and establishing communication with the WHOIS server through the first query server to acquire WHOIS query information corresponding to the queried domain name.
In the embodiment of the present application, if the AMQP server identifies that all query servers related to the WHOIS server are blocked by the AMQP server, in order to further increase the processing speed, a new query server may be started to obtain a query result. If the AMQP server identifies a portion associated with the WHOIS server, e.g., 1 or 2 query servers are blocked, then the other query servers associated with the WHOIS server are selected to obtain the query results.
According to the embodiment of the application, after the information type of the query result is identified to be the WHOIS query information, the WHOIS query information is directly sent to the WHOIS client, and the query result is presented to the user.
According to the method and the device, the AMQP server is triggered to adjust the query strategy to improve the query processing speed and improve the user experience degree by identifying the information type fed back to the AMQP server by the query server.
It should be noted that while the operations of the method of the present invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Rather, the steps depicted in the flowcharts may change order of execution. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
With further reference to fig. 3, fig. 3 shows an exemplary structural block diagram of the WHOIS query apparatus provided in the embodiment of the present application. The apparatus may be implemented by an advanced message queue protocol server.
As shown in fig. 3, the apparatus includes:
the first receiving module 310 is configured to receive a query domain name, where the query domain name is obtained by analyzing from a WHOIS query request by a WHOIS client.
In the embodiment of the application, a plurality of users send WHOIS query requests to a high-level message queue protocol server through a WHOIS client. The advanced message queue protocol server obtains the query domain name from the WHOIS query request. Wherein the WHOIS client may also be a WHOIS WEB page. The manner in which the user enters the WHOIS query request may be accomplished through interaction with the client.
The amqp (advanced Message Queuing protocol) is an application layer standard advanced Message Queuing protocol for providing unified Message service, is an open standard of the application layer protocol, and is designed for a Message-oriented middleware. The client and the message middleware based on the protocol can transfer messages and are not limited by conditions of different products, different development languages and the like of the client/middleware.
The determining module 320 is configured to determine, according to the top-level domain of the queried domain name, the WHOIS server address corresponding to the top-level domain.
In the embodiment of the application, after receiving a plurality of WHOIS query requests, the AMQP server may obtain a query domain name from the WHOIS query requests, and then determine a corresponding WHOIS server address according to a top-level domain of the query domain name. The top level domain can be understood as the last part of the domain name, the letter combination after the last point of the domain name, and the type of the top level domain can be a top level domain of a country level region, a general top level domain, an infrastructure top level domain, a test top level domain and the like.
For example, on the Internet, top-level domain names such as ". com" and ". org".
The obtaining module 330 is configured to obtain, according to the address of the WHOIS server, a first query server set corresponding to the WHOIS server.
The mapping relationship between the query server and the WHOIS server may be established in the AMQP server according to various data structures. For example, a mapping relationship between the query server and an IP address is established according to the IP address provided by a certain WHOIS service provider. Wherein the same WHOIS service provider may provide multiple WHOIS server addresses. Each WHOIS server address may correspond to multiple query servers. Multiple query servers associated with the same WHOIS server address may be referred to as a query server set. For the sake of distinction, it may be defined by the terms first, second, etc., but not by the order of operations. For example, the first query server set and the second query server set may be associated with the same WHOIS server address, and for example, the first query server set and the second query server set may also be referred to as a first subset of query servers or a second subset of query servers.
The selecting module 340 is configured to select any first query server in the first query server set, and send the query domain name to the WHOIS server corresponding to the address of the WHOIS server through the first query server.
And the AMQP server selects one query server from the first query server set according to a preset selection algorithm, and the query server is used for sending the query domain name to the WHOIS server.
A second receiving module 350, configured to receive a query result returned by the first query server, where the query result is information returned by the WHOIS server according to the query domain name.
After receiving the information returned by the query server, the AMQP server identifies the information. Because the same WHOIS server is queried for multiple times in a short time, a blocking mechanism of the WHOIS server blocks part or all query servers related to the WHOIS server, so that the AMQP server cannot acquire the result of the query request. For example, if one of the query servers associated with the WHOIS server is blocked, or all of the query servers associated with the WHOIS server are blocked, the AMQP server may identify the blocked result and then use a corresponding query policy to further obtain the result of the query request.
And an adjusting module 360, configured to adjust the query policy based on the query result to obtain WHOIS query information corresponding to the query domain name.
In the embodiment of the present application, the query result returned by the query server may be, for example, that part of the plurality of query servers associated with the WHOIS server is blocked, or that all query servers associated with the WHOIS server are blocked. Based on partial blocking or full blocking, the AMQP server may enable different query policies to further obtain WHOIS query information corresponding to the queried domain name. For example, if one of the plurality of query servers associated with the WHOIS server is blocked, the AMQP server may select another of the plurality of query servers to further forward the query request to the WHOIS server. Or after all the query servers associated with the WHOIS server are blocked, the AMQP server may also implement WHOIS query by starting a new query server, thereby improving user experience and greatly reducing query delay caused by a blocking mechanism.
On the basis of the above embodiment, the query policy is further adjusted by the query result to provide the query result to the WHOIS client. Referring to fig. 4, fig. 4 shows an exemplary block diagram of the adjusting module 360 according to the present application.
As shown in the figure 4 of the drawings,
and the identifying submodule 410 is used for identifying the information type of the query result.
The parsing sub-module 420 is configured to parse the indication information if the information type is indication information, where the indication information includes information used to indicate a status of each first query server in the first set of query servers; and
and the adjusting sub-module 430 is configured to adjust the query policy according to the analysis result to obtain WHOIS query information corresponding to the queried domain name.
According to the method and the device, different query strategies are triggered by identifying the information type of the query result returned by the query server through the AMQP server. For example, the query server returns to the AMQP server indication information, which may be set as specified by the AMQP protocol, whose contents include information indicating the status of each query server in the first set of query servers. The status of the query server is blocked, e.g. by the WHOIS server, with an identification information indication, or a status value indication, e.g. in the form of a binary value, e.g. 1 for blocking and 0 for unblocking.
The method comprises the steps of inquiring a database, acquiring ports of a plurality of inquiry servers associated with a certain WHOIS server address from the database, identifying whether the inquiry server corresponding to the port is blocked by the WHOIS server or not through a state identifier corresponding to the port, further judging whether the ports of the plurality of inquiry servers associated with the WHOIS server address are all blocked or not, and triggering different inquiry strategies based on the judgment result to improve the inquiry speed.
The adjustment sub-module 430 may further include:
a first selecting unit 4301, configured to select any one second query server in the second query server set if the analysis result indicates that each first query server in the first query server set is in a state of being blocked by a WHOIS server, and acquire WHOIS query information corresponding to the queried domain name by establishing communication between the second query server and the WHOIS server.
A second selecting unit 4302, configured to select any one of the first query servers in another part of the first query server set if the analysis result is that some of the first query servers in the first query server set are in a state of being blocked by the WHOIS server, and acquire WHOIS query information corresponding to the queried domain name by establishing communication between the first query server and the WHOIS server.
In the embodiment of the present application, if the AMQP server identifies that all query servers related to the WHOIS server are blocked by the AMQP server, in order to further increase the processing speed, a new query server may be started to obtain a query result. If the AMQP server identifies a portion associated with the WHOIS server, e.g., 1 or 2 query servers are blocked, then the other query servers associated with the WHOIS server are selected to obtain the query results.
A sending sub-module 440, after the identifying sub-module 410, configured to send the WHOIS query information to the WHOIS client if the information type is the WHOIS query information.
In the embodiment of the application, after the information type of the query result is identified as the WHOIS query information, the WHOIS query information is directly sent to the WHOIS client side, and the query result is presented to the user.
According to the method and the device, the AMQP server is triggered to adjust the query strategy to improve the query processing speed and improve the user experience degree by identifying the information type fed back to the AMQP server by the query server.
It should be understood that the units or modules recited in the apparatus 400 correspond to the various steps in the method described with reference to fig. 2. Thus, the operations and features described above with respect to the method are equally applicable to the apparatus 300-400 and the units included therein and will not be described again here. The apparatus 300-400 may be implemented in a browser or other security applications of the electronic device in advance, or may be loaded into the browser or other security applications of the electronic device by downloading or the like. The corresponding units in the apparatus 300-400 can cooperate with units in the electronic device to implement the solution of the embodiment of the present application.
Referring now to FIG. 5, a block diagram of a computer system 500 suitable for use in implementing a terminal device or server of an embodiment of the present application is shown.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, the processes described above with reference to fig. 1-2 may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method of fig. 1-2. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, and may be described as: a processor includes a first receiving module, a determining module, an obtaining module, a selecting module, a second receiving module, and an adjusting module. Where the names of such units or modules do not in some cases constitute a limitation on the unit or module itself, for example, an adjustment module may also be described as a "module for adjusting a query policy based on query results".
As another aspect, the present application also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the foregoing device in the foregoing embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer readable storage medium stores one or more programs for use by one or more processors in performing the WHOIS query method described herein.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention as defined above. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (10)
1. A WHOIS query method, performed by an advanced message queue protocol, AMQP, server, comprising:
receiving a query domain name, wherein the query domain name is obtained by analyzing a WHOIS query request by a WHOIS client;
determining a WHOIS server address corresponding to the top-level domain of the query domain name according to the top-level domain;
acquiring a first query server set corresponding to the WHOIS server address according to the WHOIS server address;
selecting any one first query server in the first query server set, and sending the query domain name to a WHOIS server corresponding to the address of the WHOIS server through the first query server;
receiving a query result returned by the first query server, wherein the query result is information returned by the WHOIS server according to the query domain name;
adjusting a query strategy based on the query result to acquire WHOIS query information corresponding to the query domain name;
identifying the information type of the query result;
if the information type is indication information which comprises information used for indicating the state of each first query server in the first query server set, analyzing the indication information; and
And adjusting the query strategy according to the analysis result to acquire WHOIS query information corresponding to the query domain name.
2. The method of claim 1, wherein the adjusting the query policy according to the parsing result to obtain WHOIS query information corresponding to the query domain name comprises:
and if the analysis result shows that each first query server in the first query server set is in a state of being blocked by the WHOIS server, selecting any second query server in a second query server set, and establishing communication with the WHOIS server through the second query server to acquire WHOIS query information corresponding to the query domain name.
3. The method of claim 1, wherein the adjusting the query policy according to the parsing result to obtain WHOIS query information corresponding to the query domain name comprises:
and if the analysis result is that part of the first query servers in the first query server set are in a state of being blocked by the WHOIS server, selecting any one of the first query servers in the other part of the first query server set, and establishing communication with the WHOIS server through the first query server to acquire WHOIS query information corresponding to the query domain name.
4. The method of claim 1, wherein the adjusting the query policy based on the query result to obtain WHOIS query information corresponding to the query domain name comprises:
and identifying the information type of the query result, and if the information type is WHOIS query information, sending the WHOIS query information to the WHOIS client.
5. A WHOIS query apparatus, executed by an advanced message queue protocol, AMQP, server, comprising:
the first receiving module is used for receiving a query domain name, wherein the query domain name is obtained by analyzing a WHOIS query request by a WHOIS client;
the determining module is used for determining the address of the WHOIS server corresponding to the top-level domain of the query domain name according to the top-level domain;
the acquisition module is used for acquiring a first query server set corresponding to the WHOIS server address according to the WHOIS server address;
a selection module, configured to select any one of the first query servers in the first query server set, and send the query domain name to the WHOIS server corresponding to the address of the WHOIS server through the first query server;
a second receiving module, configured to receive a query result returned by the first query server, where the query result is information returned by the WHOIS server according to the query domain name;
The adjusting module is used for adjusting the query strategy based on the query result so as to obtain WHOIS query information corresponding to the query domain name;
the adjustment module includes:
the identification submodule is used for identifying the information type of the query result;
the analysis submodule is used for analyzing the indication information if the information type is indication information which contains information used for indicating the state of each first query server in the first query server set; and
and the adjusting sub-module is used for adjusting the query strategy according to the analysis result so as to acquire WHOIS query information corresponding to the query domain name.
6. The apparatus of claim 5, wherein the adjustment submodule comprises:
a first selecting unit, configured to select any one of second query servers in a second query server set if an analysis result indicates that each first query server in the first query server set is in a state of being blocked by the WHOIS server, and acquire WHOIS query information corresponding to the query domain name by establishing communication between the second query server and the WHOIS server.
7. The apparatus of claim 6, wherein the adjustment submodule comprises:
A second selecting unit, configured to select any one of the first query servers in another part of the first query server set if the analysis result is that some first query servers in the first query server set are in a state of being blocked by the WHOIS server, and acquire WHOIS query information corresponding to the query domain name by establishing communication between the first query server and the WHOIS server.
8. The apparatus of claim 5, wherein the adjustment module further comprises:
the identification submodule is used for identifying the information type of the query result;
and the sending submodule is used for sending the WHOIS inquiry information to the WHOIS client if the information type is the WHOIS inquiry information.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-4 when executing the program.
10. A computer-readable storage medium having stored thereon a computer program for:
the computer program, when executed by a processor, implementing the method as claimed in any one of claims 1-4.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810382342.2A CN110401686B (en) | 2018-04-25 | 2018-04-25 | WHOIS query method, device, equipment and storage medium thereof |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810382342.2A CN110401686B (en) | 2018-04-25 | 2018-04-25 | WHOIS query method, device, equipment and storage medium thereof |
Publications (2)
Publication Number | Publication Date |
---|---|
CN110401686A CN110401686A (en) | 2019-11-01 |
CN110401686B true CN110401686B (en) | 2022-06-14 |
Family
ID=68320183
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201810382342.2A Active CN110401686B (en) | 2018-04-25 | 2018-04-25 | WHOIS query method, device, equipment and storage medium thereof |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110401686B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113378031B (en) * | 2021-06-24 | 2022-06-28 | 深圳海域信息技术有限公司 | WHOIS query method and system based on global network distributed processing |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6338082B1 (en) * | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
CN106385469A (en) * | 2016-08-25 | 2017-02-08 | 厦门易名科技股份有限公司 | Concurrent processing based WHOIS query method and device |
CN107231454A (en) * | 2017-07-06 | 2017-10-03 | 深圳互联先锋科技有限公司 | The method and device of domain name high-volume asynchronous query |
CN107547670A (en) * | 2016-06-28 | 2018-01-05 | 阿里巴巴集团控股有限公司 | The querying method and device of a kind of domain-name information |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9065855B2 (en) * | 2012-06-29 | 2015-06-23 | Verisign, Inc. | Systems and methods for automatically providing Whois service to top level domains |
-
2018
- 2018-04-25 CN CN201810382342.2A patent/CN110401686B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6338082B1 (en) * | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
CN107547670A (en) * | 2016-06-28 | 2018-01-05 | 阿里巴巴集团控股有限公司 | The querying method and device of a kind of domain-name information |
CN106385469A (en) * | 2016-08-25 | 2017-02-08 | 厦门易名科技股份有限公司 | Concurrent processing based WHOIS query method and device |
CN107231454A (en) * | 2017-07-06 | 2017-10-03 | 深圳互联先锋科技有限公司 | The method and device of domain name high-volume asynchronous query |
Also Published As
Publication number | Publication date |
---|---|
CN110401686A (en) | 2019-11-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8321503B2 (en) | Context-specific network resource addressing model for distributed services | |
US8495220B2 (en) | Managing CDN registration by a storage provider | |
WO2019165665A1 (en) | Domain name resolution method, server and system | |
US7827280B2 (en) | System and method for domain name filtering through the domain name system | |
CN110636115B (en) | Cross-cloud service calling processing method, gateway server and requester server | |
US9883002B2 (en) | Method and system for accessing website | |
CN108737515B (en) | Request routing in a networked environment | |
CN110049022B (en) | Domain name access control method and device and computer readable storage medium | |
US20160142367A1 (en) | Managing content delivery network service providers | |
US9311281B2 (en) | Methods for facilitating web page image hotspots and devices thereof | |
US20090235283A1 (en) | Global api deployment and routing | |
US9166945B1 (en) | Content provided DNS resolution validation and use | |
CN102402558A (en) | Method and system for providing message containing website | |
CN104980446A (en) | Detection method and system for malicious behavior | |
US20120102221A1 (en) | System and method for redirecting a request for a non-canonical web page | |
WO2017166524A1 (en) | Domain name parsing method and apparatus | |
US20090172107A1 (en) | Proxy content for submitting web service data in the user's security context | |
CN110580305A (en) | Method, apparatus, system, and medium for generating identifier | |
CN112597039A (en) | Virtual machine access method, system, device and computer readable storage medium | |
US20070209042A1 (en) | Grid computing architecture & associated method of invoking/registering network services for subscription | |
CN109471713B (en) | Method and device for inquiring information | |
CN110401686B (en) | WHOIS query method, device, equipment and storage medium thereof | |
CN108494870A (en) | Dynamic data loading method based on CDN and device | |
CN112565238A (en) | Method for popping privacy policy, client and computer-readable storage medium | |
FR2931268A1 (en) | DEVICE AND METHOD FOR MANAGING AVAILABILITY OF ACCESS TO DIGITAL DATA |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |