CN114465926A - Recursive server monitoring method, device, device and storage medium - Google Patents

Abstract

The invention belongs to the technical field of computers, and discloses a recursive server monitoring method, device, equipment and storage medium. In the present invention, the domain name to be accessed is obtained from a preset domain name set, and the domain name to be accessed is a non-existing top-level domain name; the target recursive server is accessed according to the domain name to be accessed, and the domain name resolution result fed back by the target recursive server is received; the domain name resolution is generated according to the domain name resolution result log, and write the domain name resolution log into the preset log file; determine the unavailable period of the target recursive server based on the preset log file. Since the non-existent top-level domain name is used to access the target recursive server, the current available status of the target recursive server can be determined according to the feedback domain name resolution result, and then the domain name resolution log generated according to the domain name resolution result is written into the preset log file, and the statistical prediction The unavailable period of the target recursive server can be determined by setting the domain name resolution results corresponding to each domain name resolution log in the log file.

Description

Recursive server monitoring method, device, device and storage medium

technical field

The present invention relates to the field of computer technology, and in particular, to a recursive server monitoring method, apparatus, device and storage medium.

Background technique

The traditional way of judging that the recursive server service is unavailable can only be through the browser to request a specific website, and then it is found that the website cannot resolve the IP normally, and then the service is found to be unavailable, but it is impossible to accurately know that the service is unavailable. It is also difficult to locate the time period and length of service unavailability, the impact of service unavailability, and the possible reasons for service unavailability.

The above content is only used to assist the understanding of the technical solutions of the present invention, and does not mean that the above content is the prior art.

SUMMARY OF THE INVENTION

The main purpose of the present invention is to provide a recursive server monitoring method, device, equipment and storage medium, aiming to solve the technical problem that the recursive server unavailable period cannot be determined in the prior art.

To achieve the above object, the invention provides a kind of recursive server monitoring method, described method comprises the following steps:

Obtain a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a non-existent top-level domain name;

Access the target recursive server according to the domain name to be accessed, and receive the domain name resolution result fed back by the target recursive server;

Generate a domain name resolution log according to the domain name resolution result, and write the domain name resolution log into a preset log file;

The unavailable period of the target recursive server is determined based on the preset log file.

Optionally, the step of generating a domain name resolution log according to the domain name resolution result and writing the domain name resolution log into a preset log file includes:

Read the previous parsing log from the preset log file;

If the domain name resolution result is inconsistent with the domain name resolution result in the previous resolution log, a domain name resolution log is generated according to the domain name resolution result, and the domain name resolution log is written into a preset log file.

Optionally, the step of determining the unavailable period of the target recursive server based on the preset log file includes:

Reading the domain name resolution log whose corresponding domain name resolution result is the first type result in the preset log file, to obtain the first type log;

searching forward from the first type of log in the preset log file for a domain name resolution log whose corresponding domain name resolution result is the second type of result, to obtain a second type of log corresponding to the first type of log;

The unavailable period of the target recursive server is determined according to the first type of log and the second type of log.

Optionally, the step of accessing the target recursive server according to the domain name to be accessed includes:

Obtain the preset instruction template, and obtain the access address of the target recursive server;

Filling the preset instruction template according to the access address and the domain name to be accessed to obtain a domain name access instruction;

Access the target recursive server through the domain name access instruction.

Optionally, after the step of accessing the target recursive server according to the domain name to be accessed, and receiving the domain name resolution result fed back by the target recursive server, the method further includes:

If the domain name resolution result is the third type result, perform existence check on the domain names in the preset domain name set;

Remove the domain name that has passed the existence check from the preset domain name set, and return to the step of obtaining the domain name to be accessed from the preset domain name set, where the domain name to be accessed is a non-existent top-level domain name.

Optionally, the step of performing existence verification on the domain names in the preset domain name set includes:

Traverse the preset domain name set, and use the traversed domain name as the domain name to be verified;

Access the root domain name server according to the domain name to be verified, and receive the domain name verification result fed back by the root domain name server;

Determine whether the domain name to be verified exists according to the domain name verification result;

If the domain name to be verified exists, it is determined that the domain name to be verified has passed the existence check;

It is detected whether there are untraversed domain names in the preset domain name set, and if there is no untraversed domain name, the traversal of the preset domain name set is ended.

Optionally, the step of obtaining the domain name to be accessed from the preset domain name set, where the domain name to be accessed is a non-existing top-level domain name, includes:

obtaining a preset detection period, and generating a domain name detection condition according to the preset detection period;

The real-time monitoring system running time, when the system running time meets the domain name detection condition, obtains the domain name to be accessed from the preset domain name set, and the domain name to be accessed is a non-existing top-level domain name.

In addition, in order to achieve the above object, the present invention also proposes a recursive server monitoring device, the recursive server monitoring device includes the following modules:

a domain name obtaining module, configured to obtain a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a non-existent top-level domain name;

a service access module, configured to access a target recursive server according to the domain name to be accessed, and receive a domain name resolution result fed back by the target recursive server;

a log generation module, configured to generate a domain name resolution log according to the domain name resolution result, and write the domain name resolution log into a preset log file;

A period determination module, configured to determine the unavailable period of the target recursive server based on the preset log file.

In addition, in order to achieve the above object, the present invention also proposes a recursive server monitoring device, the recursive server monitoring device includes: a processor, a memory, and a recursive server monitoring device stored on the memory and running on the processor A program, when the recursive server monitoring program is executed by the processor, implements the steps of the recursive server monitoring method as described above.

In addition, in order to achieve the above object, the present invention also proposes a computer-readable storage medium, where a recursive server monitoring program is stored on the computer-readable storage medium, and when the recursive server monitoring program is executed, the above-mentioned recursive server monitoring is implemented steps of the method.

The present invention obtains the domain name to be accessed from the preset domain name set, and the domain name to be accessed is a non-existent top-level domain name; accesses the target recursive server according to the domain name to be accessed, and receives the domain name resolution result fed back by the target recursive server; generates domain name resolution according to the domain name resolution result log, and write the domain name resolution log into the preset log file; determine the unavailable period of the target recursive server based on the preset log file. Since the non-existent top-level domain name is used to access the target recursive server, the current available status of the target recursive server can be determined according to the feedback domain name resolution result, and then the domain name resolution log generated according to the domain name resolution result is written into the preset log file, and the statistical prediction The unavailable period of the target recursive server can be determined by setting the domain name resolution results corresponding to each domain name resolution log in the log file.

Description of drawings

1 is a schematic structural diagram of an electronic device of a hardware operating environment involved in an embodiment of the present invention;

2 is a schematic flowchart of a first embodiment of a recursive server monitoring method according to the present invention;

3 is a schematic flowchart of a second embodiment of a recursive server monitoring method according to the present invention;

FIG. 4 is a structural block diagram of the first embodiment of the recursive server monitoring apparatus according to the present invention.

The realization, functional characteristics and advantages of the present invention will be further described with reference to the accompanying drawings in conjunction with the embodiments.

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

Referring to FIG. 1 , FIG. 1 is a schematic structural diagram of a recursive server monitoring device of a hardware operating environment involved in an embodiment of the present invention.

As shown in FIG. 1 , the electronic device may include: a processor 1001 , such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002 , a user interface 1003 , a network interface 1004 , and a memory 1005 . Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (eg, a Wireless-Fidelity (WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or may be a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the structure shown in FIG. 1 does not constitute a limitation on the electronic device, and may include more or less components than the one shown, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module and a recursive server monitoring program.

In the electronic device shown in FIG. 1, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the electronic device of the present invention can be set in In the recursive server monitoring device, the electronic device invokes the recursive server monitoring program stored in the memory 1005 through the processor 1001, and executes the recursive server monitoring method provided by the embodiment of the present invention.

An embodiment of the present invention provides a recursive server monitoring method. Referring to FIG. 2 , FIG. 2 is a schematic flowchart of a first embodiment of a recursive server monitoring method according to the present invention.

In this embodiment, the recursive server monitoring method includes the following steps:

Step S10: Obtain a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a top-level domain name that does not exist.

It should be noted that the execution body of this embodiment may be the recursive server monitoring device, and the recursive server monitoring device may be an electronic device such as a personal computer, a server, or other devices that can implement the same or similar functions. The embodiment does not limit this. In this embodiment and the following embodiments, the recursive server monitoring method of the present invention is described by taking a recursive server monitoring device as an example.

It should be noted that the preset domain name set may be a set aggregated by a large number of non-existing top-level domain names, and the preset domain name set may be preset by the administrator of the recursive server monitoring device. Among them, the non-existing top-level domain name can be a top-level domain name that is not used by any individual or institution.

In the specific implementation, the monitoring of the recursive server is continuous. Therefore, the target recursive server needs to be accessed periodically. The period can be set in advance by the administrator of the recursive server monitoring device. Therefore, in this embodiment, the The step S10 may include:

obtaining a preset detection period, and generating a domain name detection condition according to the preset detection period;

The real-time monitoring system running time, when the system running time meets the domain name detection condition, obtains the domain name to be accessed from the preset domain name set, and the domain name to be accessed is a non-existing top-level domain name.

It should be noted that the preset detection period can be set in advance by the administrator of the recursive server monitoring device according to actual needs. For example, if the preset detection period is set to 1 second, the generated domain name detection conditions are: starting from the system Fired every second when running.

It can be understood that if the system running time meets the domain name detection conditions, it means that it is necessary to detect whether the target recursive server is available at this time. Therefore, the domain name to be accessed needs to be obtained from the preset domain name server, and the subsequent steps are performed.

Step S20: Access the target recursive server according to the domain name to be accessed, and receive the domain name resolution result fed back by the target recursive server.

It should be noted that the target recursive server may be a recursive server that needs to be monitored, and the target recursive server may be designated by the administrator of the recursive server monitoring device. When the target recursive server receives the domain name to be accessed, it will perform domain name resolution on the domain name to be accessed, try to obtain information such as the server IP address corresponding to the domain name to be accessed, and then return the specific domain name resolution result.

Domain name resolution results can be divided into first type results, second type results and third type results. Among them, if the target recursive server can resolve the domain name normally, and the corresponding server IP address is not found, the first type of result will be returned, for example: NXDOMAIN; if the target recursive server cannot be resolved normally or the access timed out, the second type of result will be returned. For example: return SERVFAIL or TIMEOUT; if the target recursive server can resolve the domain name normally, and can find the corresponding server IP address, it will return the third type of result, for example: return the domain name and the server IP address corresponding to the domain name.

It is understandable that if the domain name to be accessed is a non-existent top-level domain name, the target recursive server will access the root domain name server, and obtain the domain name resolution result corresponding to the domain name to be accessed from the root domain name server, and the root domain name server is maintained by an authority. It is basically impossible to be inaccessible. Therefore, it can be determined whether the target domain name server can be accessed normally according to the domain name resolution result.

In a specific implementation, in order to improve the monitoring efficiency of the target recursive server, a relatively efficient instruction can be used to access the target recursive server. At this time, the steps of accessing the target recursive server according to the domain name to be accessed in this embodiment may include:

Obtain the preset instruction template, and obtain the access address of the target recursive server;

Filling the preset instruction template according to the access address and the domain name to be accessed to obtain a domain name access instruction;

Access the target recursive server through the domain name access instruction.

It should be noted that the access address of the target recursive server may be the IP address of the target recursive server. The preset instruction template can be an instruction template constructed according to the generation rule of the access instruction of the efficient recursive server. For example, if the dig instruction has high access to the recursive server, the instruction template can be constructed according to the generation rule of the dig instruction. Set the instruction template as: "dig @${recursive_ip} @${tdl_name}", where @${recursive_ip} is the placeholder corresponding to the access address of the domain name server to be accessed, and @${tdl_name} is the domain name to be accessed the corresponding placeholder.

In actual use, the preset command template is filled according to the access address and the domain name to be accessed, and the domain name access command can be obtained by replacing the placeholders in the preset command template according to the access address and the domain name to be accessed, so as to obtain domain name access instruction. To access the target recursive server through the domain name access instruction may be to run the domain name access instruction to access the target recursive server.

Step S30: Generate a domain name resolution log according to the domain name resolution result, and write the domain name resolution log into a preset log file.

It should be noted that the preset log file may be a file for storing domain name resolution logs. Generating the domain name resolution log according to the domain name resolution result may be obtaining the generation time corresponding to the domain name resolution result, and then filling the preset log template according to the domain name resolution result and the corresponding generation time, thereby obtaining the domain name resolution log.

For example: Assuming that the domain name resolution result is NXDOMAIN, and the corresponding generation time is 00:05:36 on November 27, 2021, the preset log template can be filled at this time to obtain a domain name resolution log "[2021-11 -2700:05:36 status: NXDOMAIN]".

In actual use, writing the domain name resolution log to the preset log file may be writing the domain name resolution log to the end of the file of the preset log file. Of course, the specific writing rule can be adjusted according to actual needs, which is not limited in this embodiment.

Step S40: Determine the unavailable period of the target recursive server based on the preset log file.

It should be noted that since the domain name to be accessed is a non-existent top-level domain name, the target recursive server will access the root domain name server, and obtain the domain name resolution result corresponding to the domain name to be accessed from the root domain name server, and the root domain name server is maintained by the authority. , it is basically impossible to be inaccessible, and it can be judged whether the target domain name server can be accessed normally according to the results of domain name resolution. Therefore, according to the domain name resolution results corresponding to each domain name resolution log stored in the preset log file, it can be determined whether the target recursive server is available when the domain name resolution log is generated, and the status can be counted to determine the unavailable period of the target recursive server. .

For example: Assuming that there are 40 domain name resolution logs in the preset log file, the domain name resolution results corresponding to the 1st to 3rd domain name resolution logs are the first type results, and the 4th to 10th domain name resolution logs corresponding to the domain name resolution results are The second type of result, the domain name resolution result corresponding to the 11-40th domain name resolution log is the first type result, which means that the target recursive server is available when the 1-3 domain name resolution log is generated, and the 4-10th domain name is generated when the target recursive server is available. The target recursive server is unavailable when parsing the log, and the target recursive server is available when the 11th to 40th domain name resolution logs are generated, then the generation time corresponding to the fourth domain name resolution log is the start of the unavailable period of the target recursive server. Article 11 The corresponding generation time of the domain name resolution log is the end time of the unavailable period of the target recursive server.

Further, it is clear from the above example that when the domain name resolution results corresponding to multiple consecutive domain name resolution logs are of the same type, the only log that actually determines the time period is the one that can be used to determine the state of the target recursive server has changed, that is, The first one of multiple consecutive domain name resolution logs. Therefore, not all domain name resolution logs need to be stored. At this time, step S30 in this embodiment may include:

Read the previous parsing log from the preset log file;

If the domain name resolution result is inconsistent with the domain name resolution result in the previous resolution log, a domain name resolution log is generated according to the domain name resolution result, and the domain name resolution log is written into a preset log file.

It should be noted that the previous resolution log may be the domain name resolution log currently located at the end of the file in the preset log file.

In actual use, if the domain name resolution result is inconsistent with the domain name resolution result in the resolution log of the previous day, it means that the status of the target recursive server has changed at this time, for example: from available to unavailable or from unavailable to available. Therefore, at this time, a domain name resolution log can be generated according to the domain name resolution result, and then the domain name resolution log can be written into a preset log file.

It is understandable that only keeping the domain name resolution logs that can be used to determine that the status of the target recursive server has changed will not affect the determination of the unavailability period of the target recursive server, and can reduce the number of logs in the preset log file and save equipment. of storage space.

In specific implementation, since the law of log storage has changed, correspondingly, the method of determining the unavailable period of the target recursive server according to the preset log file can also be changed accordingly, then step S40 described in this embodiment is at this time. , which can include:

Reading the domain name resolution log whose corresponding domain name resolution result is the first type result in the preset log file, to obtain the first type log;

searching forward from the first type of log in the preset log file for a domain name resolution log whose corresponding domain name resolution result is the second type of result, to obtain a second type of log corresponding to the first type of log;

The unavailable period of the target recursive server is determined according to the first type of log and the second type of log.

It should be noted that if the domain name resolution result corresponding to the domain name resolution log is the first type result, it means that the target recursive server is available when the domain name resolution log is generated; if the domain name resolution result corresponding to the domain name resolution log is the second type result, It means that the target recursive server is unavailable when the domain name resolution log is generated; and when writing the domain name resolution log to the preset log file, it is written by writing to the end of the file. Therefore, in the preset log file The second type of log is searched forward from the first type of log, so as to determine the specific time period during which the status of the target recursive server is unavailable.

Search forward from the first type of log in the preset log file for the domain name resolution log whose corresponding domain name resolution result is the second type of result, and obtain the second type of log corresponding to the first type of log. The first type of log is forwarded, and the domain name resolution log whose domain name resolution result corresponding to the previous first type of log is the second type of result is regarded as the second type of log corresponding to the first type of log.

Among them, since there are many types of second-type results, such as SERVFAIL and TIMEOUT, multiple domain name resolution logs whose corresponding domain name resolution results are the second-type results may be found. If there are multiple domain name resolution logs whose resolution result is the second type result, the one with the earliest generation time is used as the second type log.

For example: Assuming that the first type of log B is searched forward, there are domain name resolution logs C and D whose domain name resolution result is the second type result between the previous first type log A and the domain name resolution log C and D, where C is generated earlier For D, at this time, C is used as the second type of log corresponding to B.

In actual use, determining the unavailability period of the target recursive server according to the first type log and the second type log may be the generation time corresponding to the second type log as the unavailability start time, and the generation time corresponding to the first type log as the unavailability start time. The unavailable end time, and then the period between the unavailable start time and the unavailable end time is taken as the unavailable time period.

For example: Assuming that the generation time of a first-type log is 00:08:49 on November 27, 2021, the generation time of the first second-type log found forward from the first-type log is: At 00:05:36 on November 27, 2021, the unavailable period of the target recursive server at this time is [2021-11-27 00:05:36]-[2021-11-27 00:08:49], Unavailable time is 3 minutes and 13 seconds.

In this embodiment, the domain name to be accessed is obtained from the preset domain name set, and the domain name to be accessed is a non-existing top-level domain name; the target recursive server is accessed according to the domain name to be accessed, and the domain name resolution result fed back by the target recursive server is received; the domain name is generated according to the domain name resolution result Parse the log, and write the domain name resolution log into the preset log file; determine the unavailable period of the target recursive server based on the preset log file. Since the non-existent top-level domain name is used to access the target recursive server, the current available status of the target recursive server can be determined according to the feedback domain name resolution result, and then the domain name resolution log generated according to the domain name resolution result is written into the preset log file, and the statistical prediction The unavailable period of the target recursive server can be determined by setting the domain name resolution results corresponding to each domain name resolution log in the log file.

Referring to FIG. 3 , FIG. 3 is a schematic flowchart of a second embodiment of a recursive server monitoring method according to the present invention.

Based on the above-mentioned first embodiment, the recursive server monitoring method of this embodiment, after the step S20, further includes:

Step S30': if the domain name resolution result is the third type result, perform existence check on the domain names in the preset domain name set.

It should be noted that, over time, some TLDs that did not exist may be used by some individuals or organizations. At this time, such TLDs may be cached by the target recursive server, and the target recursive server may no longer be available. It is necessary to access the root domain name server. At this time, it is impossible to determine whether the target recursive server is available according to the domain name resolution result. Therefore, corresponding processing is required to remove such top-level domain names from the preset domain name set.

It can be understood that if the domain name resolution result is the third type result, it means that the domain name to be accessed at this time has already been used by an individual or organization, and the domain name resolution result obtained by using the domain name to be accessed at this time is difficult to be used to determine the target recursion. Whether the server is available, and it is uncertain whether there are other top-level domain names in the preset domain name set that have been used by individuals or institutions, therefore, it is necessary to perform an existence check on the domain names in the preset domain name set.

In a specific implementation, in order to ensure the reliability of performing existence verification on domain names, the step of performing existence verification on domain names in the preset domain name set described in this embodiment may include:

Traverse the preset domain name set, and use the traversed domain name as the domain name to be verified;

Access the root domain name server according to the domain name to be verified, and receive the domain name verification result fed back by the root domain name server;

Determine whether the domain name to be verified exists according to the domain name verification result;

If the domain name to be verified exists, it is determined that the domain name to be verified has passed the existence check;

Detecting whether there is an untraversed domain name in the preset domain name set, and if there is no untraversed domain name, ending the traversal of the preset domain name set.

It is understandable that since the root domain name server is maintained by an authoritative organization, it is basically impossible for the root domain name server to be inaccessible. Therefore, the domain name to be verified can be sent to the root domain name server for parsing and verification, and then passed The domain name verification result fed back by the root domain name server determines whether the domain name to be verified exists. If the domain name to be verified exists, it means that the domain name to be verified has been used by some individuals or institutions at this time, that is, the domain name to be verified exists. It already exists. Therefore, it can be determined that the domain name to be verified has passed the existence verification.

It can be understood that if there is no untraversed domain name in the preset domain name set, it means that all domain names in the preset domain name set have been checked for existence, and the traversal of the preset domain name set can be stopped at this time. . If there are domain names that have not been traversed in the preset domain name set, it means that there are domain names in the preset domain name set that have not been checked for existence, and the preset domain name set can be traversed at this time.

Step S40': remove the domain name that has passed the existence check from the preset domain name set, and return to the step of obtaining the domain name to be accessed from the preset domain name set, and the domain name to be accessed is a non-existing top-level domain name.

It should be noted that if a domain name passes the existence check, it means that this domain name is already in use by an individual or organization, that is, the domain name already exists, and the domain name resolution result obtained by accessing the target recursive server based on this domain name cannot be used for judgment. Whether the target recursive server is available, therefore, it is necessary to remove the domain name that has passed the existence check from the preset domain name set, and then obtain the domain name to be accessed from the preset domain name set again, and re-access the target recursive server.

In this embodiment, when the domain name resolution result is a result of the third type, existence verification is performed on the domain names in the preset domain name set; the domain names that have passed the existence verification are removed from the preset domain name set, and returning to the step of obtaining the domain name to be accessed from the preset domain name set, where the domain name to be accessed is a non-existing top-level domain name. Since the domain name resolution result is the third type result, it means that the domain name used to access the target recursive server has already been used by an individual or institution. The domain name of the property check is removed from the preset domain name set to ensure that the domain names in the preset domain name set are all non-existent top-level domain names, thereby ensuring the normal operation of the recursive server monitoring method of the present invention.

In addition, an embodiment of the present invention further provides a storage medium, on which a recursive server monitoring program is stored, and when the recursive server monitoring program is executed by a processor, implements the steps of the recursive server monitoring method described above.

Referring to FIG. 4, FIG. 4 is a structural block diagram of the first embodiment of the recursive server monitoring apparatus of the present invention.

As shown in FIG. 4 , the recursive server monitoring device proposed by the embodiment of the present invention includes:

a domain name obtaining module 10, configured to obtain a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a non-existing top-level domain name;

A service access module 20, configured to access a target recursive server according to the domain name to be accessed, and receive a domain name resolution result fed back by the target recursive server;

A log generation module 30, configured to generate a domain name resolution log according to the domain name resolution result, and write the domain name resolution log into a preset log file;

The period determination module 40 is configured to determine the unavailable period of the target recursive server based on the preset log file.

In this embodiment, the domain name to be accessed is obtained from the preset domain name set, and the domain name to be accessed is a non-existing top-level domain name; the target recursive server is accessed according to the domain name to be accessed, and the domain name resolution result fed back by the target recursive server is received; the domain name is generated according to the domain name resolution result Parse the log, and write the domain name resolution log into the preset log file; determine the unavailable period of the target recursive server based on the preset log file. Since the non-existent top-level domain name is used to access the target recursive server, the current available status of the target recursive server can be determined according to the feedback domain name resolution result, and then the domain name resolution log generated according to the domain name resolution result is written into the preset log file, and the statistical prediction The unavailable period of the target recursive server can be determined by setting the domain name resolution results corresponding to each domain name resolution log in the log file.

Further, the log generation module 30 is further configured to read the previous resolution log from the preset log file; if the domain name resolution result is inconsistent with the domain name resolution result in the previous resolution log, the As a result, a domain name resolution log is generated, and the domain name resolution log is written into a preset log file.

Further, the time period determination module 40 is further configured to read the domain name resolution log whose corresponding domain name resolution result is the first type result in the preset log file, and obtain the first type log; in the preset log file Search forward from the first type of log to find the domain name resolution log whose corresponding domain name resolution result is the second type of result, and obtain the second type of log corresponding to the first type of log; according to the first type of log and all The second type of log determines the period of unavailability of the target recursive server.

Further, the service access module 20 is further configured to obtain a preset instruction template, and obtain the access address of the target recursive server; fill the preset instruction template according to the access address and the domain name to be accessed, and obtain Domain name access instruction; access the target recursive server through the domain name access instruction.

Further, the service access module 20 is further configured to perform existence verification on the domain names in the preset domain name set if the domain name resolution result is the third type result; The preset domain name set is removed, and the step of obtaining the domain name to be accessed from the preset domain name set, where the domain name to be accessed is a non-existent top-level domain name, is returned.

Further, the service access module 20 is further configured to traverse the preset domain name set, and use the traversed domain name as the domain name to be verified; access the root domain name server according to the domain name to be verified, and receive the root domain name server. The domain name verification result fed back by the domain name server; determine whether the domain name to be verified exists according to the domain name verification result; if the domain name to be verified exists, it is determined that the domain name to be verified has passed the existence verification; detecting Whether there are untraversed domain names in the preset domain name set, if there is no untraversed domain name, the traversal of the preset domain name set is ended.

Further, the domain name obtaining module 10 is further configured to obtain a preset detection period, and generate a domain name detection condition according to the preset detection period; monitor the system running time in real time, and when the system running time meets the domain name detection condition , and obtains a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a non-existent top-level domain name.

It should be understood that the above are only examples, and do not constitute any limitation to the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as required, which is not limited by the present invention.

It should be noted that the above-described workflow is only illustrative, and does not limit the protection scope of the present invention. In practical applications, those skilled in the art can select some or all of them to implement according to actual needs. The purpose of the solution in this embodiment is not limited here.

In addition, for technical details not described in detail in this embodiment, reference may be made to the recursive server monitoring method provided by any embodiment of the present invention, and details are not described herein again.

Furthermore, it should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or system comprising a series of elements includes not only those elements, but also other elements not expressly listed or inherent to such a process, method, article or system. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system that includes the element.

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on such understanding, the technical solutions of the present invention can be embodied in the form of software products in essence, or the parts that make contributions to the prior art. , ROM)/RAM, magnetic disk, optical disk), including several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied in other related technical fields , are similarly included in the scope of patent protection of the present invention.

Claims (10)

1. a recursive server monitoring method, is characterized in that, described recursive server monitoring method comprises the following steps: Obtain a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a non-existent top-level domain name; Access the target recursive server according to the domain name to be accessed, and receive the domain name resolution result fed back by the target recursive server; Generate a domain name resolution log according to the domain name resolution result, and write the domain name resolution log into a preset log file; The unavailable period of the target recursive server is determined based on the preset log file. 2. The recursive server monitoring method according to claim 1, wherein the step of generating a domain name resolution log according to a domain name resolution result, and writing the domain name resolution log into a preset log file, comprises: Read the previous parsing log from the preset log file; If the domain name resolution result is inconsistent with the domain name resolution result in the previous resolution log, a domain name resolution log is generated according to the domain name resolution result, and the domain name resolution log is written into a preset log file. 3. The recursive server monitoring method according to claim 2, wherein the step of determining the unavailable period of the target recursive server based on the preset log file comprises: Reading the domain name resolution log whose corresponding domain name resolution result is the first type result in the preset log file, to obtain the first type log; searching forward from the first type of log in the preset log file for a domain name resolution log whose corresponding domain name resolution result is the second type of result, to obtain a second type of log corresponding to the first type of log; The unavailable period of the target recursive server is determined according to the first type of log and the second type of log. 4. The recursive server monitoring method according to claim 1, wherein the step of accessing the target recursive server according to the domain name to be accessed comprises: Obtain the preset instruction template, and obtain the access address of the target recursive server; Filling the preset instruction template according to the access address and the domain name to be accessed to obtain a domain name access instruction; Access the target recursive server through the domain name access instruction. 5. The recursive server monitoring method as claimed in claim 1, characterized in that, after the step of accessing the target recursive server according to the domain name to be accessed, and receiving the domain name resolution result fed back by the target recursive server, further comprising: If the domain name resolution result is the third type result, perform existence check on the domain names in the preset domain name set; Remove the domain name that has passed the existence check from the preset domain name set, and return to the step of obtaining the domain name to be accessed from the preset domain name set, where the domain name to be accessed is a non-existent top-level domain name. 6. The recursive server monitoring method according to claim 5, wherein the step of performing existence verification on the domain names in the preset domain name set comprises: Traverse the preset domain name set, and use the traversed domain name as the domain name to be verified; Access the root domain name server according to the domain name to be verified, and receive the domain name verification result fed back by the root domain name server; Determine whether the domain name to be verified exists according to the domain name verification result; If the domain name to be verified exists, it is determined that the domain name to be verified has passed the existence check; Detecting whether there is an untraversed domain name in the preset domain name set, and if there is no untraversed domain name, ending the traversal of the preset domain name set. 7. The recursive server monitoring method according to any one of claims 1-6, wherein the step of obtaining a domain name to be accessed from a preset domain name set, the domain name to be accessed being a non-existent top-level domain name, comprising: : obtaining a preset detection period, and generating a domain name detection condition according to the preset detection period; The real-time monitoring system running time, when the system running time meets the domain name detection condition, obtains the domain name to be accessed from the preset domain name set, and the domain name to be accessed is a non-existing top-level domain name. 8. A recursive server monitoring device, wherein the recursive server monitoring device comprises the following modules: a domain name obtaining module, configured to obtain a domain name to be accessed from a preset domain name set, where the domain name to be accessed is a non-existent top-level domain name; a service access module, configured to access a target recursive server according to the domain name to be accessed, and receive a domain name resolution result fed back by the target recursive server; a log generation module, configured to generate a domain name resolution log according to the domain name resolution result, and write the domain name resolution log into a preset log file; A period determination module, configured to determine the unavailable period of the target recursive server based on the preset log file. 9. A recursive server monitoring device, characterized in that the recursive server monitoring device comprises: a processor, a memory, and a recursive server monitoring program stored on the memory and running on the processor, the recursive server monitoring program The server monitoring program implements the steps of the recursive server monitoring method according to any one of claims 1-7 when the server monitoring program is executed by the processor. 10. A computer-readable storage medium, characterized in that, a recursive server monitoring program is stored on the computer-readable storage medium, and when the recursive server monitoring program is executed, the execution of the recursive server monitoring program is implemented as described in any one of claims 1-7 The steps of the recursive server monitoring method.

Images