Analytic record processing method and device, computer equipment and storage medium

Abstract

The embodiment of the invention relates to an analysis record processing method and device, computer equipment and a storage medium, and the method comprises the steps: receiving a target request which is sent by a target object and aims at an analysis record of a domain name, and a server comprises a plurality of analysis records corresponding to a plurality of different enterprise terminals; determining a request type of the target request and a requested target enterprise terminal; and when it is determined that the target object has the operation authority of the analysis record of the target enterprise terminal, updating the analysis record of the target enterprise terminal according to the request type. Therefore, a server platform can be set to store and manage the resolution records of different enterprise end domain names, only target requests sent by users with permissions can be processed, the resolution records do not need to be stored in enterprise ends or clients, leakage of the resolution records is avoided, and the security of the resolution record management of the domain names is improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of domain name resolution, and in particular to a resolution record processing method, device, computer equipment and storage medium. Background Art

[0002] In computer networks, the Hosts file is a static file that maps host names (domain names) to IP addresses. By editing the Hosts file, users can customize the resolution of specific domain names. However, in the prior art, the management and use of the Hosts file has the following problems:

[0003] With the expansion of network scale and the increase of business services, the complexity of the environment is increasing. Every time a new service is added or the IP address is changed, the operation and maintenance personnel need to manually modify the local Hosts file. This method is not only inefficient, but also increases the risk of configuration errors. In addition, due to the lack of a centralized management mechanism in existing technologies, the version control and change records of Hosts files are difficult to track, and the visibility and consistency of configuration management are poor. The manual update method is prone to inconsistent versions of the terminal Hosts file, which can cause service access errors. In addition, the Hosts file contains key information of the enterprise's internal network, such as service domain names and IP addresses. The traditional local file management method lacks a security protection mechanism and is at risk of being maliciously tampered with or leaked. Therefore, how to improve the security of domain name resolution management has become an urgent problem to be solved. Summary of the invention

[0004] In view of this, in order to solve the above technical problems or part of the technical problems, the embodiments of the present invention provide a method, apparatus, computer device and storage medium for parsing and processing records.

[0005] In a first aspect, an embodiment of the present invention provides a parsing record processing method, which is applied to a server, comprising:

[0006] receiving a target request for a resolution record of a domain name sent by a target object, wherein the server includes a plurality of resolution records corresponding to a plurality of different enterprise terminals;

[0007] Determine the request type of the target request and the target enterprise end of the request;

[0008] When it is determined that the target object has the operation authority for the resolution record of the target enterprise end, the resolution record of the target enterprise end is updated according to the request type.

[0009] In a possible implementation, updating the resolution record of the target enterprise end according to the request type includes:

[0010] When the request type is a deletion request or a modification request, determining a first resolution record that the target request needs to request;

[0011] The first resolution record is deleted or modified according to the target request, so as to update the resolution record of the target enterprise through the deletion or modification operation.

[0012] In a possible implementation manner, determining the first resolution record that the target request needs to request includes:

[0013] Determine a first database corresponding to the target enterprise end, wherein the server includes a plurality of databases, each of which corresponds to an enterprise end, and is used to store a plurality of parsing records corresponding to each of the enterprise ends;

[0014] Obtaining a parsing record identifier from the target request;

[0015] A first resolution record corresponding to the resolution record identifier is determined from the first database.

[0016] In a possible implementation, updating the resolution record of the target enterprise end according to the request type includes:

[0017] When the request type is a new request, obtaining a new parsing record from the target request;

[0018] When the new parsing record does not exist in the first database corresponding to the target enterprise end, a new addition operation is performed on the first database according to the new parsing record, so as to update the parsing record of the target enterprise end through the new addition operation.

[0019] In a possible implementation manner, after updating the resolution record of the target enterprise end according to the request type, the method further includes:

[0020] Updating the domain name server corresponding to the first database according to the updated first database;

[0021] When the domain name server is updated successfully, a success message is returned to the target object.

[0022] In a possible implementation, the request type further includes: a resolution request for a domain name, and the method further includes:

[0023] When receiving a resolution request for a target domain name sent by a target object, determining a second database to which the target domain name belongs;

[0024] Acquire a second resolution record corresponding to the target domain name from the second database;

[0025] Resolve the target domain name according to the domain name server or the second resolution record to obtain a resolution result;

[0026] Return the parsing result to the target object.

[0027] In a possible implementation, the method further includes:

[0028] Monitor the operation status of the server, the operation status including: health status, and / or, domain name query performance, and / or, domain name service log, and / or, domain name query traffic, and / or, request timeout status, and / or;

[0029] When the operating condition is abnormal, an alarm event is triggered.

[0030] In a second aspect, an embodiment of the present invention provides a parsing record processing device, including:

[0031] A receiving module, used for receiving a target request for a resolution record of a domain name sent by a target object, wherein the server contains multiple resolution records corresponding to multiple different enterprise terminals;

[0032] A determination module, used to determine the request type of the target request and the target enterprise end of the request;

[0033] The updating module is used to update the resolution record of the target enterprise end according to the request type when it is determined that the target object has the operation authority of the resolution record of the target enterprise end.

[0034] In a third aspect, an embodiment of the present invention provides a computer device, comprising: a processor and a memory, wherein the processor is used to execute a parsing record processing program stored in the memory to implement the parsing record processing method described in any one of the first aspects above.

[0035] In a fourth aspect, an embodiment of the present invention provides a storage medium, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the parsing record processing method described in any one of the first aspects above.

[0036] The resolution record processing scheme provided by the embodiment of the present invention receives a target request for a resolution record of a domain name sent by a target object, wherein the server contains multiple resolution records corresponding to multiple different enterprise ends; determines the request type of the target request and the target enterprise end of the request; and when it is determined that the target object has the operation authority for the resolution record of the target enterprise end, updates the resolution record of the target enterprise end according to the request type. Thus, a server platform can be set up to store and manage the resolution records of domain names of different enterprise ends, and only target requests sent by authorized users can be processed. Resolution records do not need to be stored on the enterprise end or client end, thereby avoiding the leakage of resolution records and improving the security of resolution record management of domain names. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A flowchart of a method for parsing records provided by an embodiment of the present invention;

[0038] Figure 2 A flowchart of another method for parsing records provided by an embodiment of the present invention;

[0039] Figure 3 A schematic diagram of the structure of a parsing record processing device provided by an embodiment of the present invention;

[0040] Figure 4 A schematic diagram of the structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0042] To facilitate understanding of the embodiments of the present invention, specific embodiments will be further explained below in conjunction with the accompanying drawings. The embodiments do not constitute a limitation on the embodiments of the present invention.

[0043] Figure 1 A flowchart of a method for parsing records provided by an embodiment of the present invention is shown in FIG. Figure 1 As shown, the method specifically includes:

[0044] S11. Receive a target request for a resolution record of a domain name sent by a target object, wherein the server contains multiple resolution records corresponding to multiple different enterprise terminals.

[0045] The resolution record processing method provided in the embodiment of the present invention is applied to a computer device, which may include: a server, a desktop computer, and a domain name server (DNS server). This embodiment is described by taking the server as an example. Specifically, a server platform is set up to store and manage the resolution records of domain names on different enterprise sides. Only target requests sent by authorized users can be processed. The resolution records do not need to be stored on the enterprise side or the client side, thereby avoiding the leakage of the resolution records.

[0046] In this embodiment, multiple databases are pre-built in the server platform (for example, the database can be: MySQL or MongoDB), and each database stores all the resolution records corresponding to an enterprise end. At the same time, a user interface is built on the front end of the platform (for example, the user interface is built using React or Vue.js.) A dynamic form is provided through the user interface for users to input operations such as adding resolution records, modifying resolution records, and deleting resolution records as user requests for resolution records of domain names (for example, users can view, add, modify or delete DNS resolution records on the Web interface). The back end of the platform builds an API service (for example, using Node.js or Python Flask / Django to build an API service), provides an interface to receive target requests, and can manage resolution records through target requests. When the user enters a target request, the back end can receive the target request.

[0047] S12: Determine the request type of the target request and the target enterprise end of the request.

[0048] In this embodiment, the request type characterizes the purpose of the target request or the operation on the resolution record. The request type may include but is not limited to: a deletion request, a new addition request, a modification request for the resolution record, a resolution request for the domain name, etc. At the same time, the target request also includes: the identifier of the enterprise end where the resolution record targeted by the target request is located, which is used to quickly locate the target enterprise end corresponding to the current target request. When the platform backend receives the target request, it identifies the request type of the target request and extracts the identifier corresponding to the target enterprise end from the target request.

[0049] S13: When it is determined that the target object has the operation authority for the resolution record of the target enterprise, the resolution record of the target enterprise is updated according to the request type.

[0050] In this embodiment, it is verified whether the target object (eg, client) sending the target request has the operation authority to manage or view the resolution records of the target enterprise end, so as to ensure the security and compliance of the operation.

[0051] The content of the permission verification may include: the system verifies whether the identity of the target object is legal through a preset permission management module. Check whether the target object is granted the permission to update the parsed record.

[0052] After the target object's permissions are confirmed, the resolution record is updated according to the type of request initiated: Add request: Add a new domain name and IP mapping to the resolution record database of the target enterprise. Modify request: Update an existing resolution record, such as modifying an IP address or domain name. Delete request: Remove the specified resolution record to ensure that redundant or expired data is no longer retained. After the update is completed, the system is synchronized to the relevant DNS server in real time to ensure the timeliness of the resolution record. At the same time, the details of each operation are recorded in the log, including the operator, time, request type and update content, to facilitate subsequent auditing and tracing.

[0053] In a possible implementation, updating the resolution record of the target enterprise end according to the request type includes:

[0054] When the request type is a deletion request or a modification request, determine the first resolution record that the target request needs to request; perform a deletion operation or a modification operation on the first resolution record according to the target request, so as to update the resolution record of the target enterprise end through the deletion operation or the modification operation.

[0055] The determining of the first parsing record required for the target request includes:

[0056] Determine a first database corresponding to the target enterprise end, where the server includes multiple databases, each database corresponds to an enterprise end, and is used to store multiple resolution records corresponding to each enterprise end; obtain a resolution record identifier from the target request; and determine a first resolution record corresponding to the resolution record identifier from the first database.

[0057] Specifically, the system pre-configures an independent database for each enterprise end, and each database stores all resolution records of the enterprise end. After receiving the target request, the corresponding first database is determined by the enterprise end identifier (such as enterprise ID or unique authentication information) contained in the request. The resolution record identifier (such as domain name, IP address or unique record ID) is extracted from the target request. The resolution record identifier is a key parameter for locating a specific resolution record. In the first database, a query is performed based on the resolution record identifier. Determine the target resolution record corresponding to the resolution record identifier, that is, the first resolution record. Check whether the target object has the authority to perform deletion or modification operations on the first resolution record to prevent unauthorized operations from affecting the system.

[0058] When the request type is a delete request, the system removes the first resolution record from the database according to the request content. When the request type is a modify request, the system modifies the first resolution record according to the new resolution content specified in the request (such as the updated IP address or TTL value), so as to update the resolution record in the first database.

[0059] In a possible implementation, updating the resolution record of the target enterprise end according to the request type further includes:

[0060] When the request type is a new request, a new resolution record is obtained from the target request; when the new resolution record does not exist in the first database corresponding to the target enterprise end, a new operation is performed on the first database according to the new resolution record to update the resolution record of the target enterprise end through the new operation.

[0061] Specifically, when processing a new request type, the system parses and extracts a new resolution record from the target request. The new resolution record contains necessary field information, such as domain name, IP address, TTL (time to live), etc. According to the enterprise-side identifier (such as enterprise ID) in the target request, locate the first database corresponding to the target enterprise side. The first database specifically stores all resolution records on the target enterprise side to ensure data isolation and management efficiency. The system queries the first database for the unique identifier of the new resolution record (such as domain name or record ID). If the record already exists: terminate the new addition operation and return a prompt message to the requester (if the record already exists, it cannot be added repeatedly). If the record does not exist: continue to perform the new addition operation. Write the new resolution record into the first database. Ensure that the format and field integrity of the newly added record meet the preset specifications of the database.

[0062] In a possible implementation manner, after updating the resolution record of the target enterprise end according to the request type, the method further includes:

[0063] The domain name server corresponding to the first database is updated according to the updated first database; when the domain name server is updated successfully, success information is returned to the target object.

[0064] Specifically, when the resolution record in the first database changes due to addition, modification or deletion operations, the system generates an update task. The update task contains the latest status of the resolution record (new additions, modified content, or deleted records). The system synchronizes the updated resolution record to the DNS server corresponding to the first database (for example, Bind9, CoreDNS) through an API or a dedicated interface. Ensure that the resolution data of the domain name server is consistent with the first database, and ensure the continuity and stability of the business. The DNS server can be the same server as the server where the platform is located or a different server.

[0065] The system monitors the update operation of the domain name server to ensure that the update task is successfully executed: if the update is successful, the system checks whether the configuration file loading status and resolution response of the domain name server are in line with expectations. If the update fails, the system captures the failure reason (such as network anomaly, insufficient permissions, configuration error) and records it in the error log.

[0066] When the update is successful, the target object is returned with operation success information, including the updated record content and effective time. This ensures that the target object knows that the update has been completed and the parsed record has taken effect.

[0067] When an update fails, an operation failure message is returned with a detailed error description to facilitate troubleshooting for the target object.

[0068] At the same time, the system can record key information during the update process, including: updated database name, type and content of resolution record, domain name server name, operation time, update result, etc. It supports locating problems through log auditing, and provides automatic retry mechanism or manual intervention for failed tasks.

[0069] In a possible implementation, the request type further includes: a resolution request for a domain name, and the method further includes:

[0070] When a resolution request for a target domain name sent by a target object is received, the second database to which the target domain name belongs is determined; a second resolution record corresponding to the target domain name is obtained from the second database; the target domain name is resolved according to the domain name server or the second resolution record to obtain a resolution result; and the resolution result is returned to the target object.

[0071] Specifically, a resolution request for a target domain name sent by a target object is received. The resolution request includes the target domain name and other necessary information (such as request type, enterprise-side identifier, client-side identifier, etc.). The second database corresponding to the enterprise-side identifier is determined. The second database is used to store the resolution record of the target domain name, and the second resolution record corresponding to the target domain name is queried in the determined second database. The second resolution record may include: the IP address of the domain name (A record), CNAME (alias record), MX (mail exchange record), or other types of resolution information. If the second resolution record of the target domain name exists in the second database, the record is used directly to complete the resolution. If the second database does not hit the record, the resolution request is forwarded to the corresponding domain name server, and the domain name server completes the resolution. The resolution result (such as the IP address or resolution error information) is returned to the target object.

[0072] In one possible implementation, the operation status of the server is monitored, and the operation status includes: health status, and / or, domain name query performance, and / or, domain name service log, and / or, domain name query traffic, and / or, request timeout, and / or; when the operation status is abnormal, an alarm event is triggered.

[0073] Specifically, the system conducts a comprehensive monitoring of the operation of the server, which may include but is not limited to: Health status: monitor the server's CPU, memory, disk usage and other resource indicators, and check the survival status of the service process. Domain name query performance: monitor the response time of domain name resolution, evaluate whether performance indicators are met, and measure QPS (queries per second) to understand the service load. Domain name service log: analyze the logs generated by the domain name server and identify abnormal events (such as misses, resolution errors). Domain name query traffic: monitor the query traffic entering the domain name server, including the source and frequency of requests, and check abnormal traffic (such as DDoS attacks). Request timeout: count the number and frequency of timed requests and evaluate service stability.

[0074] At the same time, anomaly detection is also required. The system identifies anomalies through preset thresholds, rules, and machine learning algorithms: health status is lower than normal (such as CPU usage higher than 90%, memory exhaustion). Query performance is degraded (such as response time exceeds the threshold). Traffic surges or the proportion of requests from unknown sources is too high. A large number of parsing errors or timeouts appear in the log. When the system detects an anomaly, it automatically triggers an alarm event and notifies the relevant person in charge. It supports multiple alarm channels, including SMS, email, and instant messaging tools (such as DingTalk, Slack). Alarm content: server information involved in the anomaly, abnormal indicators, occurrence time, and recommended handling measures. Grading alarm: Set different alarm levels according to the severity of the anomaly (such as insufficient resources and system downtime). At the same time, the system records all operating indicators and abnormal event logs, and supports historical backtracking and problem location. Provide a visual monitoring panel to help administrators view the operating status of the server in real time.

[0075] As an example, Figure 2 A flowchart of another method for parsing records provided by an embodiment of the present invention is shown in FIG. Figure 2 As shown, the method specifically includes:

[0076] The user logs in to the management platform through the web interface. The system performs identity authentication to ensure user permissions. When managing DNS resolution records, users can view, add, modify or delete DNS resolution records on the web interface. The system records the user's operations in the database and updates the DNS server in real time. A success message is returned to the user.

[0077] When processing a DNS resolution request, an internal service or user initiates a DNS resolution request. After receiving the request, the DNS server obtains the corresponding resolution record from the database and returns the resolution result to the requesting party. Using dynamic DNS resolution to manage and access cloud hosts solves the problem of dynamic changes in IP addresses and enables access through a fixed domain name.

[0078] At the same time, the system monitors the status of the DNS service in real time to ensure its normal operation. Once an abnormality is found, an alarm is sent to the administrator in a timely manner. The system regularly generates audit reports to record user operations and DNS resolution changes to ensure compliance.

[0079] The resolution record processing scheme provided by the embodiment of the present invention receives a target request for a resolution record of a domain name sent by a target object, wherein the server contains multiple resolution records corresponding to multiple different enterprise ends; determines the request type of the target request and the target enterprise end of the request; and when it is determined that the target object has the operation authority for the resolution record of the target enterprise end, updates the resolution record of the target enterprise end according to the request type. Thus, a server platform can be set up to store and manage the resolution records of domain names of different enterprise ends, and only target requests sent by authorized users can be processed. The resolution records do not need to be stored on the enterprise end or the client end, thereby avoiding the leakage of the resolution records. At the same time, it can effectively solve the security risks caused by adding resolution to the local hosts file in the B-end environment of cloud computing. By centrally managing DNS resolution records, security and management efficiency are enhanced, ensuring efficient and secure access to internal and external network resources.

[0080] Figure 3 A schematic diagram of a structure of a parsing record processing device provided by an embodiment of the present invention, such as Figure 3 As shown, the device specifically includes:

[0081] A receiving module 31 is used to receive a target request for a resolution record of a domain name sent by a target object, wherein the server contains multiple resolution records corresponding to multiple different enterprise terminals;

[0082] A determination module 32, used to determine the request type of the target request and the target enterprise end of the request;

[0083] The updating module 33 is used to update the resolution record of the target enterprise end according to the request type when it is determined that the target object has the operation authority of the resolution record of the target enterprise end.

[0084] In a possible implementation manner, the determination module is specifically configured to determine the first resolution record that the target request needs to request when the request type is a deletion request or a modification request;

[0085] The update module is specifically used to perform a deletion operation or a modification operation on the first resolution record according to the target request, so as to update the resolution record of the target enterprise end through the deletion operation or the modification operation.

[0086] In a possible implementation manner, the determination module is specifically used to determine a first database corresponding to the target enterprise end, the server includes multiple databases, each of the databases corresponds to an enterprise end, and is used to store multiple resolution records corresponding to each of the enterprise ends;

[0087] Obtaining a parsing record identifier from the target request;

[0088] A first resolution record corresponding to the resolution record identifier is determined from the first database.

[0089] In a possible implementation, the updating module is specifically configured to obtain a new parsing record from the target request when the request type is a new request;

[0090] When the new parsing record does not exist in the first database corresponding to the target enterprise end, a new addition operation is performed on the first database according to the new parsing record, so as to update the parsing record of the target enterprise end through the new addition operation.

[0091] In a possible implementation manner, the updating module is further configured to update the domain name server corresponding to the first database according to the updated first database;

[0092] When the domain name server is updated successfully, a success message is returned to the target object.

[0093] In a possible implementation manner, the determination module is further configured to determine the second database to which the target domain name belongs when receiving a resolution request for the target domain name sent by the target object;

[0094] Acquire a second resolution record corresponding to the target domain name from the second database;

[0095] A resolution module 34, configured to resolve the target domain name according to the domain name server or the second resolution record to obtain a resolution result;

[0096] Return the parsing result to the target object.

[0097] In a possible implementation, the monitoring module 35 is used to monitor the operation status of the server, and the operation status includes: health status, and / or, domain name query performance, and / or, domain name service log, and / or, domain name query traffic, and / or, request timeout status, and / or;

[0098] When the operating condition is abnormal, an alarm event is triggered.

[0099] The parsing record processing device provided in this embodiment may be as follows Figure 3 The device shown in FIG. 1 may perform the following steps: Figure 1-2 Parse all the steps of the record processing method in order to achieve Figure 1-2 For details, please refer to the technical effect of the analytical record processing method shown in Figure 1-2 For the sake of brevity, the relevant description is not repeated here.

[0100] Figure 4 A schematic diagram of the structure of a computer device provided by an embodiment of the present invention, Figure 4 The computer device 400 shown includes: at least one processor 401, a memory 402, at least one network interface 404 and other user interfaces 403. The various components in the computer device 400 are coupled together via a bus system 405. It is understood that the bus system 405 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 405 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 405 is not shown in FIG. Figure 4 Various buses are labeled as bus system 405 .

[0101] The user interface 403 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).

[0102] It can be understood that the memory 402 in the embodiment of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 402 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0103] In some implementations, the memory 402 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 4021 and application programs 4022 .

[0104] The operating system 4021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 4022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present invention can be included in the application 4022.

[0105] In the embodiment of the present invention, by calling the program or instruction stored in the memory 402, specifically, the program or instruction stored in the application 4022, the processor 401 is used to execute the method steps provided by each method embodiment, for example, including:

[0106] receiving a target request for a resolution record of a domain name sent by a target object, wherein the server includes a plurality of resolution records corresponding to a plurality of different enterprise terminals;

[0107] Determine the request type of the target request and the target enterprise end of the request;

[0108] When it is determined that the target object has the operation authority for the resolution record of the target enterprise end, the resolution record of the target enterprise end is updated according to the request type.

[0109] In a possible implementation, when the request type is a deletion request or a modification request, determining a first resolution record that the target request needs to request;

[0110] The first resolution record is deleted or modified according to the target request, so as to update the resolution record of the target enterprise through the deletion or modification operation.

[0111] In a possible implementation, a first database corresponding to the target enterprise end is determined, and the server includes a plurality of databases, each of which corresponds to an enterprise end and is used to store a plurality of parsing records corresponding to each of the enterprise ends;

[0112] Obtaining a parsing record identifier from the target request;

[0113] A first resolution record corresponding to the resolution record identifier is determined from the first database.

[0114] In a possible implementation, when the request type is a new request, a new resolution record is obtained from the target request;

[0115] When the new parsing record does not exist in the first database corresponding to the target enterprise end, a new addition operation is performed on the first database according to the new parsing record, so as to update the parsing record of the target enterprise end through the new addition operation.

[0116] In a possible implementation manner, the domain name server corresponding to the first database is updated according to the updated first database;

[0117] When the domain name server is updated successfully, a success message is returned to the target object.

[0118] In a possible implementation, when a resolution request for a target domain name sent by a target object is received, determining a second database to which the target domain name belongs;

[0119] Acquire a second resolution record corresponding to the target domain name from the second database;

[0120] Resolve the target domain name according to the domain name server or the second resolution record to obtain a resolution result;

[0121] Return the parsing result to the target object.

[0122] In a possible implementation, the operation status of the server is monitored, and the operation status includes: health status, and / or, domain name query performance, and / or, domain name service log, and / or, domain name query traffic, and / or, request timeout status, and / or;

[0123] When the operating condition is abnormal, an alarm event is triggered.

[0124] The method disclosed in the above embodiment of the present invention can be applied to the processor 401, or implemented by the processor 401. The processor 401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 401 or the instruction in the form of software. The above processor 401 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as a hardware decoding processor to execute, or the hardware and software units in the decoding processor can be executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 402, and the processor 401 reads the information in the memory 402 and completes the steps of the above method in combination with its hardware.

[0125] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0126] For software implementation, the technology described herein can be implemented by a unit that performs the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0127] The computer device provided in this embodiment may be Figure 4 The device shown in , can be executed as Figure 1-2 Parse all the steps of the record processing method in order to achieve Figure 1-2 For details, please refer to the technical effect of the analytical record processing method shown in Figure 1-2 For the sake of brevity, the relevant description is not repeated here.

[0128] The embodiment of the present invention also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above-mentioned types of memory.

[0129] When one or more programs in the storage medium can be executed by one or more processors, the above-mentioned parsing record processing method executed on the device side can be implemented.

[0130] The processor is used to execute the parsing record processing program stored in the memory to implement the following steps of the parsing record processing method executed on the device side:

[0131] receiving a target request for a resolution record of a domain name sent by a target object, wherein the server includes a plurality of resolution records corresponding to a plurality of different enterprise terminals;

[0132] Determine the request type of the target request and the target enterprise end of the request;

[0133] When it is determined that the target object has the operation authority for the resolution record of the target enterprise end, the resolution record of the target enterprise end is updated according to the request type.

[0134] In a possible implementation, when the request type is a deletion request or a modification request, determining a first resolution record that the target request needs to request;

[0135] The first resolution record is deleted or modified according to the target request, so as to update the resolution record of the target enterprise through the deletion or modification operation.

[0136] In a possible implementation, a first database corresponding to the target enterprise end is determined, and the server includes a plurality of databases, each of which corresponds to an enterprise end and is used to store a plurality of parsing records corresponding to each of the enterprise ends;

[0137] Obtaining a parsing record identifier from the target request;

[0138] A first resolution record corresponding to the resolution record identifier is determined from the first database.

[0139] In a possible implementation, when the request type is a new request, a new resolution record is obtained from the target request;

[0140] When the new parsing record does not exist in the first database corresponding to the target enterprise end, a new addition operation is performed on the first database according to the new parsing record, so as to update the parsing record of the target enterprise end through the new addition operation.

[0141] In a possible implementation manner, the domain name server corresponding to the first database is updated according to the updated first database;

[0142] When the domain name server is updated successfully, a success message is returned to the target object.

[0143] In a possible implementation, when a resolution request for a target domain name sent by a target object is received, determining a second database to which the target domain name belongs;

[0144] Acquire a second resolution record corresponding to the target domain name from the second database;

[0145] Resolve the target domain name according to the domain name server or the second resolution record to obtain a resolution result;

[0146] Return the parsing result to the target object.

[0147] In a possible implementation, the operation status of the server is monitored, and the operation status includes: health status, and / or, domain name query performance, and / or, domain name service log, and / or, domain name query traffic, and / or, request timeout status, and / or;

[0148] When the operating condition is abnormal, an alarm event is triggered.

[0149] The professionals should further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0150] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0151] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for processing parsed records, characterized in that: Applicable to servers, including: receiving a target request for a resolution record of a domain name sent by a target object, wherein the server includes a plurality of resolution records corresponding to a plurality of different enterprise terminals; Determine the request type of the target request and the target enterprise end of the request; When it is determined that the target object has the operation authority for the resolution record of the target enterprise end, the resolution record of the target enterprise end is updated according to the request type.

2. The method according to claim 1, characterized in that: The updating of the resolution record of the target enterprise end according to the request type includes: When the request type is a deletion request or a modification request, determining a first resolution record that the target request needs to request; The first resolution record is deleted or modified according to the target request, so as to update the resolution record of the target enterprise through the deletion or modification operation.

3. The method according to claim 2, characterized in that The determining the first parsing record required for the target request includes: Determine a first database corresponding to the target enterprise end, wherein the server includes a plurality of databases, each of which corresponds to an enterprise end, and is used to store a plurality of parsing records corresponding to each of the enterprise ends; Obtaining a parsing record identifier from the target request; A first resolution record corresponding to the resolution record identifier is determined from the first database.

4. The method according to claim 3, characterized in that The updating of the resolution record of the target enterprise end according to the request type includes: When the request type is a new request, obtaining a new parsing record from the target request; When the new parsing record does not exist in the first database corresponding to the target enterprise end, a new addition operation is performed on the first database according to the new parsing record, so as to update the parsing record of the target enterprise end through the new addition operation.

5. The method according to claim 4, characterized in that After updating the resolution record of the target enterprise end according to the request type, the method further includes: Updating the domain name server corresponding to the first database according to the updated first database; When the domain name server is updated successfully, a success message is returned to the target object.

6. The method according to claim 5, characterized in that The request type also includes: a resolution request for a domain name, and the method also includes: When receiving a resolution request for a target domain name sent by a target object, determining a second database to which the target domain name belongs; Acquire a second resolution record corresponding to the target domain name from the second database; Resolve the target domain name according to the domain name server or the second resolution record to obtain a resolution result; Return the parsing result to the target object.

7. The method according to claim 5, characterized in that The method further comprises: Monitor the operation status of the server, the operation status including: health status, and / or, domain name query performance, and / or, domain name service log, and / or, domain name query traffic, and / or, request timeout status, and / or; When the operating condition is abnormal, an alarm event is triggered.

8. A parsing record processing device, characterized in that: include: A receiving module, used for receiving a target request for a resolution record of a domain name sent by a target object, wherein the server contains multiple resolution records corresponding to multiple different enterprise terminals; A determination module, used to determine the request type of the target request and the target enterprise end of the request; The updating module is used to update the resolution record of the target enterprise end according to the request type when it is determined that the target object has the operation authority of the resolution record of the target enterprise end.

9. A computer device, characterized in that: include: A processor and a memory, wherein the processor is used to execute a parsing record processing program stored in the memory to implement the parsing record processing method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the parsing record processing method according to any one of claims 1 to 7.

Images