CN115695275B - Root zone record monitoring method, system, equipment and readable storage medium - Google Patents
Root zone record monitoring method, system, equipment and readable storage medium Download PDFInfo
- Publication number
- CN115695275B CN115695275B CN202211714618.5A CN202211714618A CN115695275B CN 115695275 B CN115695275 B CN 115695275B CN 202211714618 A CN202211714618 A CN 202211714618A CN 115695275 B CN115695275 B CN 115695275B
- Authority
- CN
- China
- Prior art keywords
- root
- root zone
- monitoring
- record
- server
- 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
Abstract
The application discloses a root zone record monitoring method, a root zone record monitoring system, root zone record monitoring equipment and a readable storage medium, wherein the root zone record monitoring method is applied to a root zone record monitoring device and comprises a root server and a plurality of network cluster nodes which are mutually in communication connection, and each network cluster node comprises a plurality of cloud servers; the root zone record monitoring method comprises the following steps: controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset duration; generating a data set to be monitored according to the root zone file; controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server; and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored. The method and the device record the monitoring accuracy rate for the root zone.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method, a system, a device, and a readable storage medium for monitoring root zone records.
Background
The traditional detection method for recording the correctness of the root zone of the root server is to detect the root by using a known root zone file through a single server and compare and analyze the correctness of the record. Firstly, the method is that the single-node client performs request detection to the target root server, which is easily limited by the machine load condition of the single server and the network condition of the server, and may cause an abnormality in the monitoring result of the root server. Secondly, this approach focuses on the probe analysis of the root's top-level domain name resource record correctness case, and lacks probe analysis of other records. Again, this approach is a single probe analysis, and it is difficult to monitor the root zone record in real time when changes occur in the root zone record update record. Finally, the mode supports the mode of comparing and detecting the root zone records, and does not support the configuration input mode, namely the detection mode of generating the root zone record configuration, namely, the metadata set of the root zone records is input in multiple modes. Therefore, the conventional detection method for detecting the recording correctness of the root zone has low accuracy for recording the root zone.
Disclosure of Invention
The present application mainly aims to provide a method, a system, a device and a readable storage medium for monitoring root zone records, and aims to solve the problem of low accuracy of monitoring root zone records.
In order to achieve the above object, the present application provides a root zone record monitoring method, which is applied to a root zone record monitoring apparatus, and includes a root server and a plurality of network cluster nodes, which are in communication connection with each other, where the network cluster nodes include a plurality of cloud servers; the root zone record monitoring method comprises the following steps:
controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset time;
generating a data set to be monitored according to the root zone file;
controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server;
and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
Optionally, the step of controlling the cloud server to respectively acquire the root zone files in the root server at intervals of a preset duration includes:
controlling a cloud server to respectively acquire the release conditions of the root zone files of the root server at intervals of preset duration;
pulling a target file according to the release condition, wherein the target file comprises a root zone file or a root zone record configuration file;
and if the target file is a root zone recording configuration file, generating a root zone file according to the root zone recording configuration file.
Optionally, the step of generating a data set to be monitored according to the root zone file includes:
extracting resource record names and resource record types from the root zone file;
and generating a data set to be monitored according to the resource record name and the resource record type.
Optionally, the step of controlling, according to the data set to be monitored, the cloud servers to respectively send the detection requests to the root server, and recording the monitoring results fed back by the root server includes:
controlling the cloud server to respectively traverse the resource record name and the resource record type in the data set to be monitored, and sequentially sending a detection request to the root server;
and recording a monitoring result fed back by the root server according to the resource record name and the resource record type, wherein the monitoring result comprises record content and a response state.
Optionally, the step of recording an abnormal result in the monitoring result according to the monitoring result and the data set to be monitored includes:
if the response states in the monitoring results are normal, comparing the recorded content with the data set to be monitored to obtain a comparison result;
and recording abnormal results in the monitoring results according to the comparison results.
Optionally, the step of recording an abnormal result in the monitoring result according to the comparison result includes:
and if the comparison result shows that the recorded content is not consistent with the resource record name and the resource record type in the data set to be monitored, judging that the recorded content is abnormal, and storing the recorded content.
Optionally, after the step of comparing the recorded content with the data set to be monitored to obtain a comparison result, if the response status in the monitoring result is normal, the method further includes:
and if the response state of one cloud server in the monitoring results is abnormal and the response states of the other cloud servers are normal, determining that the network of the cloud server with the abnormal response state is abnormal.
Further, to achieve the above object, the present invention provides a root zone record monitoring system, comprising:
the file acquisition module is used for controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset time;
the data set generating module is used for generating a data set to be monitored according to the root zone file;
the detection monitoring module is used for controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored and recording monitoring results fed back by the root server;
and the monitoring result recording module is used for recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
In addition, to achieve the above object, the present invention further provides a root zone record monitoring apparatus, including: the system comprises a memory, a processor and a root zone record monitoring program which is stored on the memory and can run on the processor, wherein the root zone record monitoring program realizes the steps of the root zone record monitoring method when being executed by the processor.
Furthermore, to achieve the above object, the present invention further provides a computer readable storage medium having a root zone record monitoring program stored thereon, the root zone record monitoring program, when executed by a processor, implementing the steps of the root zone record monitoring method as described above.
The invention provides a root zone record monitoring method, a system, equipment and a readable storage medium, wherein the root zone record monitoring method is applied to a root zone record monitoring device and comprises a root server and a plurality of network cluster nodes which are mutually communicated and connected, and each network cluster node comprises a plurality of cloud servers; the root zone record monitoring method comprises the following steps: controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset time; generating a data set to be monitored according to the root zone file; controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server; and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored. By the method, the record after the root zone file is issued can be monitored for correctness, the verification of the one-time partial record of the root zone by a traditional single machine is improved, the uninterrupted monitoring of all the root zone records is improved in a cluster mode, and the target of real-time monitoring is achieved by setting the preset time length and starting the monitored root zone file orderly and intermittently and uninterruptedly. Through the server environment of multiple clusters, the problem that the monitoring result is inaccurate due to serious load of a single server and abnormal limitation of a network is solved, the root zone records of the root can be monitored in a real-network detection mode, the problem of service possibly provided by cluster nodes of different networks can be found in real time through malicious interaction between a cloud server and a root server, the problem that only part of the root zone file records are analyzed by the single server in an off-line mode, and the comprehensive real-time monitoring of all the root zone records is not carried out is solved, and the accuracy of monitoring the root zone records is improved.
Drawings
FIG. 1 is a schematic structural diagram of a hardware operating environment according to an embodiment of a root-zone record monitoring method of the present invention;
FIG. 2 is a flowchart illustrating an embodiment of a root zone record monitoring method according to the present invention;
FIG. 3 is a schematic diagram of a frame structure of the root zone recording and monitoring device according to the present invention;
FIG. 4 is a flowchart illustrating a detailed process of step S10 according to an embodiment of the root-zone record monitoring method of the present invention;
the implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As shown in fig. 1, fig. 1 is a schematic terminal structure diagram of a hardware operating environment according to an embodiment of the present invention.
The terminal of the embodiment of the invention is root zone recording monitoring equipment.
As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a dvi interface 1004, a usb interface 1005, and a memory 1006. Wherein a communication bus 1002 is used to enable connective 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, a wireless interface. The DVI interface 1004 may optionally include a standard wired interface for connecting to other external devices via DVI wires. The USB interface 1005 may optionally include a standard wired interface for connecting with other external devices via a USB cable. The memory 1006 may be a high-speed RAM memory or a non-volatile memory (e.g., a disk memory). The memory 1006 may alternatively be a storage device separate from the processor 1001.
Optionally, the terminal may further include an audio circuit and the like, which are not described in detail herein.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, the memory 1006, which is a type of computer storage medium, may include therein an operating system, a DVI interface module, a USB interface module, a user interface module, and a root-log monitor program.
In the terminal shown in fig. 1, the DVI interface 1004 is mainly used for connecting, and communicating data with, external devices; the USB interface 1005 is mainly used for connecting an external device and performing data communication with the external device; the user interface 1003 is mainly used for connecting a client and performing data communication with the client; and the processor 1001 may be configured to call the root zone record monitor stored in the memory 1006 and perform the following operations:
controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset time;
generating a data set to be monitored according to the root zone file;
controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server;
and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
Further, the processor 1001 may call the root zone record monitoring program stored in the memory 1006, and further perform the following operations:
controlling a cloud server to respectively acquire the release conditions of the root zone files of the root server at intervals of preset duration;
pulling a target file according to the release condition, wherein the target file comprises a root zone file or a root zone record configuration file;
and if the target file is a root zone recording configuration file, generating a root zone file according to the root zone recording configuration file.
Further, the processor 1001 may call the root zone record monitoring program stored in the memory 1006, and further perform the following operations:
extracting a resource record name and a resource record type from the root zone file;
and generating a data set to be monitored according to the resource record name and the resource record type.
Further, the processor 1001 may call the root zone record monitoring program stored in the memory 1006, and further perform the following operations:
controlling the cloud server to respectively traverse the resource record names and the resource record types in the data set to be monitored, and sequentially sending detection requests to the root server;
and recording a monitoring result fed back by the root server according to the resource record name and the resource record type, wherein the monitoring result comprises record content and a response state.
Further, the processor 1001 may call the root zone record monitoring program stored in the memory 1006, and further perform the following operations:
if the response states in the monitoring results are normal, comparing the recorded content with the data set to be monitored to obtain a comparison result;
and recording abnormal results in the monitoring results according to the comparison results.
Further, the processor 1001 may call the root zone record monitoring program stored in the memory 1006, and further perform the following operations:
and if the comparison result shows that the recorded content is not consistent with the resource record name and the resource record type in the data set to be monitored, judging that the recorded content is abnormal, and storing the recorded content.
Further, the processor 1001 may call the root zone record monitoring program stored in the memory 1006, and further perform the following operations:
and if the response state of one cloud server in the monitoring results is abnormal and the response states of the other cloud servers are normal, judging that the network of the cloud server with the abnormal response state is abnormal.
The specific embodiment of the root zone record monitoring device of the present invention is basically the same as the following embodiments of the root zone record monitoring program, and will not be described herein again.
Referring to fig. 2, fig. 2 is a schematic flowchart of a root zone record monitoring method according to a first embodiment of the present invention, and the root zone record monitoring method provided in this embodiment includes the following steps:
step S10, controlling a cloud server to respectively acquire root zone files in a root server at intervals of preset duration;
please refer to fig. 3, fig. 3 is a schematic diagram of a frame structure of a root zone record monitoring apparatus according to the present invention, which is applied to the root zone record monitoring apparatus, the root zone record monitoring apparatus includes a root Server and a plurality of network cluster nodes, the network cluster nodes include a plurality of cloud servers, where the root Server is a Domain Name Server (DNS) mainly used for mapping from a Domain Name to an Internet Protocol address (Internet Protocol, IP) and resolving other Internet resources, the network cluster nodes include networks of three operators, such as unicom, telecom, and mobile, and each network cluster node includes cloud servers in different regions, and in addition, each cluster node is provided with a dig tool, which is a commonly used Domain Name query tool, and can query information from a designated DNS Server, and in this embodiment, the present invention is mainly used for sending a detection request and receiving a monitoring result of the root Server. Each cloud server is a detection point, and a detection request can be sent to the root server through the dig tool.
In an embodiment, the step S10 further includes:
s11, controlling a cloud server to respectively acquire the release conditions of the root zone files of the root server at intervals of preset time length;
in this embodiment, the preset duration is preferably 5 minutes, that is, every 5 minutes, all the cloud servers acquire a root zone file publishing condition of the root server, where the publishing condition includes that a new root zone file is not published and a new root zone file is published, and the root zone file mainly includes top-level domain name resource records and other records. In addition, when the issue condition of the root zone file is judged, the root zone file or the root zone record configuration file can be pulled, the last detected root zone file or the last detected root zone record configuration file is compared, if the record changes, the root issues a new root zone file, and otherwise, the root does not update.
Step S12, pulling a target file according to the release condition, wherein the target file comprises a root zone file or a root zone record configuration file;
if the release condition is that a new root zone file is released, pulling the latest root zone file or root zone record configuration file, and replacing the historical root zone file or root zone record configuration file; and if the release condition is that no new root zone file is released, directly using the last acquired historical root zone file or root zone record configuration file.
And S13, if the target file is a root zone recording configuration file, generating a root zone file according to the root zone recording configuration file.
In this embodiment, if the root zone record configuration file is the root zone record configuration file, the root zone file is generated, otherwise, the root zone file is directly used.
Step S20, generating a data set to be monitored according to the root zone file;
in an embodiment, the step S20 further includes:
step A21, extracting resource record names and resource record types from the root zone file;
step A22, generating a data set to be monitored according to the resource record name and the resource record type.
In this implementation, all resource record names and resource record types are extracted from the root zone file, then the deduplication operation is aggregated according to the resource record names and the resource record types, the duplicate resource record names and the resource record types are removed, and finally, the reserved data set is the data set to be monitored, which is needed by the detection request.
Step S30, controlling the cloud servers to respectively send detection requests to the root servers according to the data sets to be monitored, and recording monitoring results fed back by the root servers;
in this embodiment, each cloud server sequentially traverses the resource record name and the resource record type in the data set to be monitored, and sends a probe request to the root server according to the resource record name and the resource record type, so that the root server responds according to the probe request feedback.
Specifically, in an embodiment, the step S30 further includes:
step A31, controlling the cloud server to respectively traverse the resource record name and the resource record type in the data set to be monitored, and sequentially sending a detection request to the root server;
step A32, recording a monitoring result fed back by the root server according to the resource record name and the resource record type, wherein the monitoring result comprises record content and a response state.
In this embodiment, the cloud servers are respectively located in different operator networks, and therefore send the probe request to the root server through the different operator networks, specifically, since the cloud servers are deployed with the dig tool, the probe request can be sequentially sent to the root server according to the resource record name and the resource record type through the dig tool, after receiving the probe request, the root server responds according to the probe request, generates record content corresponding to the response, generates an original monitoring result, and then obtains the original monitoring result of the root server through the dig tool. In addition, after the original monitoring result is obtained, the original monitoring result needs to be normalized, and the response state in the original monitoring result and all recorded contents corresponding to the response state after the response are extracted and taken as the monitoring result.
And S40, recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
In an embodiment, the step S40 further includes:
step A41, if the response states in the monitoring result are all normal, comparing the recorded content with the data set to be monitored to obtain a comparison result;
in this embodiment, since there are multiple cloud servers, and each cloud server obtains a monitoring result, when the response state fed back by the root server according to the resource record name and the resource record type in the probe request sent by all cloud servers is normal, all the record contents after the response are extracted, and the record contents are compared with the resource record name and the resource record type in the data set to be monitored, which are collected by the cloud servers, to obtain a comparison result, where the comparison result includes that the record contents are consistent with the resource record name and the resource record type, and the record contents are inconsistent with the resource record name and the resource record type.
And A42, recording abnormal results in the monitoring results according to the comparison results.
In one embodiment, the step a42 further includes:
step A421, if the comparison result is that the recorded content is inconsistent with the resource record name and the resource record type in the data set to be monitored, determining that the recorded content is abnormal, and storing the recorded content.
In this embodiment, if the record content is inconsistent with the resource record name and the resource record type in the data set to be monitored, it indicates that the record content is abnormal, the root zone file in the root server has an error, and the record content in which the abnormality occurs is stored for use in detecting, monitoring, alarming, displaying, and the like. In addition, if the record content is consistent with the resource record name and the resource record type in the data set to be monitored, the record content is normal, and the root zone file is correct, the next round of monitoring is performed or the next resource record name and the resource record type are detected in the data set to be monitored until all detection of the data set to be monitored is completed. In addition, in this embodiment, if the data set to be monitored lacks or adds content records, it is also determined that the root zone file record is incorrect.
In an embodiment, after the step a41, the method further includes:
step a43, if the response state of one cloud server in the monitoring result is abnormal, and the response states of the other cloud servers are normal, determining that the network of the cloud server whose response state is abnormal.
In this embodiment, when the response state of the root server is abnormal, the content record is not generated, and it is directly determined that the root area file record is incorrect. If the response state obtained by one of the cloud servers is abnormal and the response states of the other cloud servers are normal, determining that the network of the cloud server with the abnormal response state is abnormal, wherein the network is a cluster node accessed by the cloud server and comprises communication, movement or telecommunication.
The invention provides a root zone record monitoring method, which is applied to a root zone record monitoring device and comprises a root server and a plurality of network cluster nodes, wherein the root server and the plurality of network cluster nodes are mutually communicated and connected; the root zone record monitoring method comprises the following steps: controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset duration; generating a data set to be monitored according to the root zone file; controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server; and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored. By the method, the record after the root zone file is issued can be monitored for correctness, the verification of the one-time partial record of the root zone by a traditional single machine is improved, the uninterrupted monitoring of all the root zone records is improved in a cluster mode, and the target of real-time monitoring is achieved by setting the preset time length and starting the monitored root zone file orderly and intermittently and uninterruptedly. Through the server environment of multiple clusters, the problem that the monitoring result is inaccurate due to serious load of a single server and abnormal limitation of a network is solved, the root zone records of the root can be monitored in a real-network detection mode, the problem of service possibly provided by cluster nodes of different networks can be found in real time through malicious interaction between a cloud server and a root server, the problem that only part of the root zone file records are analyzed by the single server in an off-line mode, and the comprehensive real-time monitoring of all the root zone records is not carried out is solved, and the accuracy of monitoring the root zone records is improved.
Furthermore, an embodiment of the present invention further provides a computer-readable storage medium, where a root zone record monitoring program is stored on the computer-readable storage medium, and when executed by a processor, the root zone record monitoring program implements the following operations:
controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset duration;
generating a data set to be monitored according to the root zone file;
controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server;
and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
Further, the position detection program when executed by the processor further performs the following operations:
controlling a cloud server to respectively acquire the release conditions of the root zone files of the root server at intervals of preset duration;
pulling a target file according to the release condition, wherein the target file comprises a root zone file or a root zone record configuration file;
and if the target file is a root zone recording configuration file, generating a root zone file according to the root zone recording configuration file.
Further, the position detection program when executed by the processor further performs the following operations:
extracting resource record names and resource record types from the root zone file;
and generating a data set to be monitored according to the resource record name and the resource record type.
Further, the position detection program when executed by the processor further performs the following operations:
controlling the cloud server to respectively traverse the resource record name and the resource record type in the data set to be monitored, and sequentially sending a detection request to the root server;
and recording a monitoring result fed back by the root server according to the resource record name and the resource record type, wherein the monitoring result comprises record content and a response state.
Further, the position detection program when executed by the processor further performs the following operations:
if the response states in the monitoring results are normal, comparing the recorded content with the data set to be monitored to obtain a comparison result;
and recording abnormal results in the monitoring results according to the comparison results.
Further, the position detection program when executed by the processor further performs the following operations:
and if the comparison result shows that the recorded content is not consistent with the resource record name and the resource record type in the data set to be monitored, judging that the recorded content is abnormal, and storing the recorded content.
Further, the position detection program when executed by the processor further performs the following operations:
and if the response state of one cloud server in the monitoring results is abnormal and the response states of the other cloud servers are normal, judging that the network of the cloud server with the abnormal response state is abnormal.
The invention also proposes a computer-readable storage medium on which a computer program is stored. The computer readable storage medium may be the Memory 02 of the mass spectrometer of fig. 1, or may be at least one of a ROM (Read-Only Memory)/RAM (Random Access Memory), a magnetic disk, and an optical disk, and includes information for enabling the mass spectrometer to perform the method according to the embodiments of the present invention.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or system comprising the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better implementation.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A root zone record monitoring method is characterized in that the root zone record monitoring method is applied to a root zone record monitoring device and comprises a root server and a plurality of network cluster nodes which are mutually communicated and connected, wherein each network cluster node comprises a plurality of cloud servers; the root zone record monitoring method comprises the following steps:
controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset time;
generating a data set to be monitored according to the root zone file;
controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored, and recording monitoring results fed back by the root server;
and recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
2. The method for monitoring root zone records according to claim 1, wherein the step of controlling the cloud server to respectively acquire the root zone files in the root server at intervals of a preset duration comprises:
controlling a cloud server to respectively acquire the release conditions of the root zone files of the root server at intervals of preset duration;
pulling a target file according to the release condition, wherein the target file comprises a root zone file or a root zone record configuration file;
and if the target file is a root zone recording configuration file, generating a root zone file according to the root zone recording configuration file.
3. The root zone record monitoring method according to claim 2, wherein the step of generating a data set to be monitored according to the root zone file comprises:
extracting resource record names and resource record types from the root zone file;
and generating a data set to be monitored according to the resource record name and the resource record type.
4. The root zone record monitoring method according to claim 3, wherein the step of controlling the cloud server to respectively send a detection request to the root server according to the data set to be monitored and recording the monitoring result fed back by the root server comprises:
controlling the cloud server to respectively traverse the resource record name and the resource record type in the data set to be monitored, and sequentially sending a detection request to the root server;
and recording a monitoring result fed back by the root server according to the resource record name and the resource record type, wherein the monitoring result comprises record content and a response state.
5. The root zone record monitoring method according to claim 4, wherein the step of recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored comprises:
if the response states in the monitoring results are all normal, comparing the recorded content with the data set to be monitored to obtain a comparison result;
and recording abnormal results in the monitoring results according to the comparison results.
6. The method for monitoring root zone record according to claim 5, wherein the step of recording abnormal results in the monitoring results according to the comparison results comprises:
and if the comparison result shows that the record content is inconsistent with the resource record name and the resource record type in the data set to be monitored, judging that the record content is abnormal, and storing the record content.
7. The method for monitoring root zone records according to claim 5, wherein, after the step of comparing the record content with the data set to be monitored to obtain a comparison result, if the response status in the monitoring result is normal, the method further comprises:
and if the response state of one cloud server in the monitoring results is abnormal and the response states of the other cloud servers are normal, determining that the network of the cloud server with the abnormal response state is abnormal.
8. A root zone record monitoring system, comprising:
the file acquisition module is used for controlling the cloud server to respectively acquire root zone files in the root server at intervals of preset time;
the data set generating module is used for generating a data set to be monitored according to the root zone file;
the detection monitoring module is used for controlling the cloud server to respectively send detection requests to the root server according to the data set to be monitored and recording monitoring results fed back by the root server;
and the monitoring result recording module is used for recording abnormal results in the monitoring results according to the monitoring results and the data set to be monitored.
9. A root zone record monitoring device, comprising: a memory, a processor and a root zone record monitoring program stored on the memory and executable on the processor, the root zone record monitoring program when executed by the processor implementing the steps of the root zone record monitoring method as claimed in any one of claims 1 to 7.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a root zone record monitoring program, which when executed by a processor implements the steps of the root zone record monitoring method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211714618.5A CN115695275B (en) | 2022-12-30 | 2022-12-30 | Root zone record monitoring method, system, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211714618.5A CN115695275B (en) | 2022-12-30 | 2022-12-30 | Root zone record monitoring method, system, equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115695275A CN115695275A (en) | 2023-02-03 |
| CN115695275B true CN115695275B (en) | 2023-03-07 |
Family
ID=85057326
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211714618.5A Active CN115695275B (en) | 2022-12-30 | 2022-12-30 | Root zone record monitoring method, system, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115695275B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103685599A (en) * | 2013-12-09 | 2014-03-26 | 中国科学院计算机网络信息中心 | Domain name recursion service pre-judgment and intervention method |
| CN107819895A (en) * | 2017-11-16 | 2018-03-20 | 哈尔滨工业大学（威海） | The analysis method of TLD configuration and safety based on domain resource record |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9954840B2 (en) * | 2015-05-08 | 2018-04-24 | Cloudflare, Inc. | Generating a negative answer to a domain name system query that indicates resource records as existing for the domain name regardless of whether those resource records actually exist for the domain name |
| CN105245631B (en) * | 2015-09-25 | 2018-10-26 | 中国互联网络信息中心 | A kind of method and system of optimization DNS root service access |
-
2022
- 2022-12-30 CN CN202211714618.5A patent/CN115695275B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103685599A (en) * | 2013-12-09 | 2014-03-26 | 中国科学院计算机网络信息中心 | Domain name recursion service pre-judgment and intervention method |
| CN107819895A (en) * | 2017-11-16 | 2018-03-20 | 哈尔滨工业大学（威海） | The analysis method of TLD configuration and safety based on domain resource record |
Non-Patent Citations (1)
| Title |
|---|
| 张宇，夏重达等.一个自主开放的互联网根域名解析体系.2017,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115695275A (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111045952B (en) | Software testing method, flow playback device, terminal equipment and readable storage medium | |
| US20070005738A1 (en) | Automated remote scanning of a network for managed and unmanaged devices | |
| US20190372878A1 (en) | Web site reachability management for content browsing | |
| CN111159514B (en) | Method, device and equipment for detecting task effectiveness of web crawler and storage medium | |
| CN110460476B (en) | Network operation and maintenance management method | |
| CN109684155B (en) | Monitoring configuration method, device, equipment and readable storage medium | |
| CN111045879B (en) | Method, device and storage medium for generating pressure test report | |
| CN107360036B (en) | Network fault positioning method, terminal and server | |
| CN110765090B (en) | Log data management method and device, storage medium and electronic equipment | |
| CN115695275B (en) | Root zone record monitoring method, system, equipment and readable storage medium | |
| CN108076165B (en) | Method, equipment and system for domain name resolution information management | |
| US10572458B2 (en) | Method and apparatus of collecting and reporting database application incompatibilities | |
| CN110275785B (en) | Data processing method and device, client and server | |
| CN114465927B (en) | DNS server pressure testing method, electronic equipment and readable storage medium | |
| CN111177722A (en) | Webshell file detection method and device, server and storage medium | |
| CN111198853B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN111131370B (en) | Method, device and system for detecting whether service call is correct | |
| CN114116448A (en) | Pressure testing method and device of application program, storage medium and computer equipment | |
| CN114598622A (en) | Data monitoring method and device, storage medium and computer equipment | |
| CN115729727A (en) | Fault repairing method, device, equipment and medium | |
| CN109756393B (en) | Information processing method, system, medium, and computing device | |
| CN113660359A (en) | Management method and device for domain name resolution record, storage medium and electronic equipment | |
| CN112671615A (en) | Method, system and storage medium for collecting operation behavior data of front-end user | |
| US20130141128A1 (en) | Test device and test method for testing electronic devices | |
| CN117176613B (en) | Data acquisition method and device |
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 |