Domain name management method, domain name management device, equipment and computer storage medium
Through the domain name management method, the verification of the domain name information is stored in the preset list, solving the problem of the corporate domain name and non -matching IP address association in the process of business iteration, realizing the timely monitoring and alarm of abnormal domain names, increasing the domain name management Efficiency.
Patent Information
- Application Number
- CN202411252142.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-06
- Publication Date
- 2025-01-24
Smart Images
Figure CN119363366A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network technology, and in particular to a domain name management method, a domain name management apparatus, a domain name management device, and a computer storage medium. Background Art
[0002] Domain name is a key part of the Internet infrastructure, which can provide a readable and easy-to-understand address for any IP (Internet Protocol) address on the Internet.
[0003] Enterprises often have many domain name assets, and each domain name asset has an IP address that matches it. As the business changes, the server (IP address that matches the domain name) may be released, but due to poor management of the domain name, it may be missed. At this time, if the IP address is used by another enterprise or individual again, the domain name that originally belonged to you will point to someone else's IP address, resulting in abnormal traffic. In serious cases, it may also introduce security issues. Summary of the invention
[0004] In order to solve the above technical problems, the present application proposes a domain name management method, a domain name management apparatus, a domain name management device and a computer storage medium.
[0005] In order to solve the above technical problems, the present application proposes a domain name management method, which includes:
[0006] In response to the detection trigger instruction, obtaining the target domain name;
[0007] obtaining at least one preset list;
[0008] Verifying whether the domain name information of the target domain name is stored in the preset list;
[0009] If yes, confirm that the risk assessment result of the target domain name is risk-free;
[0010] If not, confirm that the risk assessment result of the target domain name is that there is a risk.
[0011] In order to solve the above technical problems, the present application also proposes a domain name management device, which includes: a detection trigger module, a domain name risk assessment module, and a feedback and alarm module; wherein:
[0012] The detection trigger module is used to obtain the target domain name in response to the detection trigger instruction;
[0013] The domain name risk assessment module is used to obtain at least one preset list; verify whether the domain name information of the target domain name is stored in the preset list;
[0014] The feedback and alarm module is used to confirm that the risk assessment result of the target domain name is risk-free when it is confirmed that the domain name information of the target domain name is stored in the preset list; and to confirm that the risk assessment result of the target domain name is risky when it is confirmed that the domain name information of the target domain name is not stored in the preset list.
[0015] In order to solve the above technical problems, the present application also proposes a domain name management device, which includes a memory and a processor coupled to the memory; wherein the memory is used to store program data, and the processor is used to execute the program data to implement the domain name management method as described above.
[0016] In order to solve the above technical problems, the present application also proposes a computer storage medium, which is used to store program data. When the program data is executed by a computer, it is used to implement the above domain name management method.
[0017] Compared with the prior art, the beneficial effects of the present application are: the domain name management device obtains the target domain name in response to the detection trigger instruction; obtains at least one preset list; verifies whether the domain name information of the target domain name is stored in the preset list; if so, confirms that the risk assessment result of the target domain name is risk-free; if not, confirms that the risk assessment result of the target domain name is risky. Through the above domain name management method, abnormal domain names can be monitored and alarmed in a timely manner, without waiting for the abnormal business traffic to be discovered before delaying processing, thereby ensuring the efficiency of domain name management. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0019] in:
[0020] Figure 1 It is a flowchart of an embodiment of a domain name management method provided by the present application;
[0021] Figure 2 It is a schematic diagram of the framework of the domain name management system provided by this application;
[0022] Figure 3 It is a flowchart of the risk assessment scheme provided in this application;
[0023] Figure 4 It is a structural diagram of an embodiment of a domain name management device provided by the present application;
[0024] Figure 5 It is a structural diagram of an embodiment of a domain name management device provided by the present application;
[0025] Figure 6 It is a structural diagram of an embodiment of a computer storage medium provided by the present application. DETAILED DESCRIPTION
[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0027] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0028] As cloud networks become more complex, users lack comprehensive target monitoring capabilities, especially in hybrid cloud network architectures, where users are unable to promptly detect abnormalities in target services monitored by domain names. This application provides a domain name management solution that provides multiple verification methods to meet the needs of verifying different types of target services in a hybrid cloud network architecture, thereby improving the reliability of domain names and the security of services.
[0029] Please refer to Figure 1 and Figure 2 , Figure 1 is a flowchart of an embodiment of a domain name management method provided by the present application. Figure 2 It is a schematic diagram of the framework of the domain name management system provided by this application.
[0030] The domain name management method of the present application is applied to a domain name management device, wherein the domain name management device of the present application can be a server, a terminal device, or a system in which a server and a terminal device cooperate with each other. Accordingly, the various parts included in the domain name management device, such as various units, sub-units, modules, and sub-modules, can all be set in the server, can all be set in the terminal device, or can be set in the server and the terminal device respectively.
[0031] Furthermore, the above-mentioned server can be hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or it can be implemented as a single server. When the server is software, it can be implemented as multiple software or software modules, such as software or software modules used to provide distributed servers, or it can be implemented as a single software or software module, which is not specifically limited here.
[0032] like Figure 1 As shown, the specific steps are as follows:
[0033] Step S11: In response to the detection trigger instruction, obtain the target domain name.
[0034] In the embodiments of the present application, Figure 2 The domain name management system shown, or the framework of the domain name management device shown above, can be divided into a detection trigger module, a domain name risk assessment module, and a feedback and alarm module according to the functions.
[0035] The function of the detection trigger module is to obtain the target domain name in response to the detection trigger instruction.
[0036] Specifically, the detection trigger instruction serves as a start instruction for starting the domain name management method of the present application. The present application may provide a variety of triggering methods, and any triggering method may generate the detection trigger instruction.
[0037] For example, the detection trigger instruction can be initiated by the user actively. Specifically, the user triggers the detection function by touching a button of the domain name management device, thereby generating the detection trigger instruction.
[0038] For another example, the detection trigger instruction can be used by the system to trigger the detection task regularly. Specifically, the domain name management device presets the periodic time of triggering the detection task in advance through the detection trigger module, such as once a day, once a week, once a month, etc., and can also preset specific periodic time.
[0039] For another example, the detection trigger instruction can be compatible with both the user actively initiating the detection task and the system timing triggering the detection task. That is, in addition to the function of presetting the triggering detection task in advance, the domain name management device also provides the function of user intervention and active triggering.
[0040] When the domain name management device detects the generation of the detection trigger instruction, it obtains the target domain name for the specified detection according to the detection trigger instruction.
[0041] Step S12: Obtain at least one preset list.
[0042] In the embodiments of the present application, Figure 2 As shown, the domain name management device performs risk assessment on the target domain name obtained in step S11 through the domain name risk assessment module and the preset list. The principle of risk assessment is to detect whether the target domain name and its domain name information are in the preset list that is continuously maintained. Only when it fully complies with the records in the preset list can the target domain name be determined to be risk-free.
[0043] Specifically, the domain name management device extracts a list of data required for risk assessment, such as Figure 2 As shown, the preset data lists include but are not limited to: a domain name list, a mapping list, and a service address list. The domain name management device can select one or more data lists for risk assessment according to the risk assessment scheme specified by the user.
[0044] Furthermore, the above data list can be maintained on one side of the domain name management device, or on the other side of the cloud vendor. Specifically, the domain name management device can manually maintain the list content of the preset list through staff. For example, when the domain name or its domain name information changes, the staff can manually update the list data; the domain name management device can also synchronize the latest information about the target domain name or its domain name information on the cloud vendor side to the preset order by calling the cloud vendor interface. In addition, the domain name management device can also call the cloud vendor interface to directly import the latest preset list for risk assessment.
[0045] The domain name management device ensures that the data content of the preset list is the latest situation of the domain name through the above method, thereby improving the accuracy of domain name management and risk assessment.
[0046] Step S13: Verify whether the domain name information of the target domain name is stored in the preset list.
[0047] In the embodiment of the present application, the domain name management device verifies whether the domain name information of the target domain name is stored in a preset list through the domain name risk assessment module, thereby obtaining the risk assessment result of the target domain name.
[0048] Specifically, the present application provides a variety of risk assessment schemes, and the domain name management device can arbitrarily select one or more combinations to assess the risk of the target domain name.
[0049] Please combine Figure 2 Continue reading Figure 3 , Figure 3It is a flow chart of the risk assessment scheme provided in this application. It should be noted that: Figure 3 It is a combination of multiple risk assessment schemes. In other embodiments, other numbers or other types of risk assessment schemes or combinations may be used, which are not listed here one by one.
[0050] The domain name risk assessment module accesses the corresponding required data list according to the risk assessment plan formulated by the user. The domain name information of the target domain name includes but is not limited to: the target service address, identity information, mapping relationship, etc. corresponding to the target domain name. Correspondingly, the preset lists maintained by the domain name management device include but are not limited to: domain name list, service address list, mapping list, and identity list, etc.
[0051] Combine the following Figure 3 The risk assessment solution embodiment shown specifically introduces the workflow of the domain name risk assessment module:
[0052] S1: The domain name risk assessment module resolves the target service address A1 mapped to the target domain name D1, and then performs risk assessment on the target domain name D1 and / or the target service address A1.
[0053] It should be noted that the type of the target service address involved in this application can be any one or more of the following address types: IP address, mail server address, domain name server address, canonical domain name address, etc. If multiple address types are used, the domain name risk assessment module needs to perform risk assessment on the target service address of each address type.
[0054] Specifically, the domain name risk assessment module obtains the domain name list, and then verifies whether the target domain name is stored in the domain name list. If yes, it proceeds to step S14; if not, it proceeds to step S15.
[0055] S2: The domain name risk assessment module performs risk assessment on the domain name information by determining whether the target service address is in a preset list.
[0056] Specifically, the domain name risk assessment module obtains the domain name list and the target service list, and then verifies whether the target domain name is stored in the domain name list, and verifies whether the target service address is stored in the target service list. Only when the above two verification results are both yes, proceed to step S14; if the above two verification results are both no, or only one verification result is yes, proceed to step S15.
[0057] S3: The domain name risk assessment module performs risk assessment on the domain name information by determining whether the mapping relationship between the domain name and the target server address is in a preset list.
[0058] Specifically, the domain name risk assessment module obtains the domain name list and the mapping list, and then verifies whether the target domain name is stored in the domain name list, and verifies whether the mapping relationship between the target domain name and the target service address is stored in the mapping list. Only when the above two verification results are both yes, proceed to step S14; if the above two verification results are both no, or only one verification result is yes, proceed to step S15.
[0059] S4: For important services, the domain name risk assessment module can be embedded in a preset instruction response module, and then the domain name information can be assessed for risk by sending preset instructions to the domain name and verifying the identity information of the target server.
[0060] Specifically, the domain risk assessment module obtains the identity list. The domain risk assessment module sends a preset instruction to the target domain name through the preset instruction response module, so that the target domain name returns a static file. The domain risk assessment module extracts the identity information of the target server by parsing the static file. Then, it verifies whether the identity information is stored in the identity list. If so, it proceeds to step S14; if not, it proceeds to step S15.
[0061] Sn: Based on the above risk assessment situations, the final risk assessment result is obtained.
[0062] Specifically, the domain name risk assessment module comprehensively considers the above risk assessment situations, and when all verification results are yes, it proceeds to step S14; otherwise, it proceeds to step S15.
[0063] In the above steps, the preset domain name list, service address list, domain name and service address mapping list can be obtained through automatic import and manual maintenance operations, such as: by calling the cloud vendor interface, manually exporting cloud vendor data, manual maintenance, etc.
[0064] It should be noted that the steps of the risk assessment scheme referred to in this application may include one or more combinations of the above-mentioned S2, S3, and S4, which are not listed one by one here.
[0065] Step S14: confirm that the risk assessment result of the target domain name is risk-free.
[0066] In the embodiment of the present application, the domain name management device confirms that the risk assessment result of the target domain name is risk-free, and can continue to monitor the target domain name and use the target domain name normally.
[0067] Step S15: confirm that the risk assessment result of the target domain name is that there is a risk.
[0068] In the embodiment of the present application, when the domain name management device confirms that the risk assessment result of the target domain name is risky, the feedback and alarm module will report the data of the abnormal risk assessment result to the system and feedback to the stakeholders. The feedback method includes but is not limited to: system station letter, email, SMS, phone call, instant messaging tool reminder, etc.
[0069] In the present application, the domain name management device responds to the detection trigger instruction, obtains the target domain name; obtains at least one preset list; verifies whether the domain name information of the target domain name is stored in the preset list; if so, confirms that the risk assessment result of the target domain name is risk-free; if not, confirms that the risk assessment result of the target domain name is risky. Through the above domain name management method, abnormal domain names can be monitored and alarmed in a timely manner, without waiting for the abnormal business traffic to be discovered before delaying processing, thereby ensuring the efficiency of domain name management.
[0070] The domain name management method of the present application can timely monitor abnormal domain name mapping relationships and issue an alarm, without having to wait for business traffic anomalies to be discovered before delaying processing.
[0071] The domain name management method of the present application provides different levels of verification methods by targeting different types of servers for domain name mapping, adapting to different scenarios and different business levels.
[0072] The domain name management method of the present application verifies the identity of the target server by sending preset instructions, making the domain name mapping relationship safer and more reliable, and further ensuring business security.
[0073] The domain name management method of the present application avoids traffic anomalies caused by IP reuse by a third party by detecting the service address information of the domain name resolution, thereby improving business security.
[0074] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.
[0075] In order to implement the above domain name management method, this application also proposes a domain name management device, please refer to Figure 4 , Figure 4 It is a structural diagram of an embodiment of a domain name management device provided by the present application.
[0076] The domain name management device 300 of this embodiment includes a detection trigger module 31 , a domain name risk assessment module 32 , and a feedback and alarm module 33 .
[0077] The detection trigger module 31 is used to obtain the target domain name in response to the detection trigger instruction.
[0078] The domain name risk assessment module 32 is used to obtain at least one preset list; and verify whether the domain name information of the target domain name is stored in the preset list.
[0079] The feedback and alarm module 33 is used to confirm that the risk assessment result of the target domain name is risk-free when it is confirmed that the domain name information of the target domain name is stored in the preset list; and to confirm that the risk assessment result of the target domain name is risky when it is confirmed that the domain name information of the target domain name is not stored in the preset list.
[0080] In order to implement the above domain name management method, this application also proposes a domain name management device, please refer to Figure 5 , Figure 5 It is a structural diagram of an embodiment of a domain name management device provided by the present application.
[0081] The domain name management device 400 of this embodiment includes a processor 41 , a memory 42 , an input / output device 43 , and a bus 44 .
[0082] The processor 41, the memory 42, and the input / output device 43 are respectively connected to the bus 44. The memory 42 stores program data, and the processor 41 is used to execute the program data to implement the domain name management method described in the above embodiment.
[0083] In the embodiment of the present application, the processor 41 may also be referred to as a CPU (Central Processing Unit). The processor 41 may be an integrated circuit chip having the ability to process signals. The processor 41 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or the processor 41 may also be any conventional processor, etc.
[0084] This application also provides a computer storage medium, please continue to refer to Figure 6 , Figure 6 It is a structural diagram of an embodiment of a computer storage medium provided in the present application. The computer storage medium 600 stores a computer program 61. When the computer program 61 is executed by a processor, it is used to implement the domain name management method of the above embodiment.
[0085] When the embodiments of the present application are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk.
[0086] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A domain name management method, characterized in that: The domain name management method comprises: In response to the detection trigger instruction, obtaining the target domain name; obtaining at least one preset list; Verifying whether the domain name information of the target domain name is stored in the preset list; If yes, confirm that the risk assessment result of the target domain name is risk-free; If not, confirm that the risk assessment result of the target domain name is that there is a risk.
2. The domain name management method according to claim 1, characterized in that: The obtaining of at least one preset list includes: The data interface of the cloud vendor is called to import the preset list maintained by the cloud vendor.
3. The domain name management method according to claim 1 or 2, characterized in that: The at least one preset list includes a domain name list; The verifying whether the domain name information of the target domain name is stored in the preset list includes: Verify whether the target domain name is stored in the domain name list.
4. The domain name management method according to claim 3, characterized in that: The at least one preset list also includes a service address list; The verifying whether the domain name information of the target domain name is stored in the preset list includes: Resolve the target domain name and obtain the target service address mapped by the target domain name; Verify whether the following risk assessment conditions are met simultaneously: the target domain name is stored in the domain name list, and the target service address is stored in the service address list.
5. The domain name management method according to claim 4, characterized in that: The type of the target service address is any one of the following address types: IP address, mail server address, domain name server address, and standard domain name address.
6. The domain name management method according to claim 3, characterized in that: The at least one preset list further includes a mapping list; The verifying whether the domain name information of the target domain name is stored in the preset list includes: Resolve the target domain name and obtain the target service address mapped by the target domain name; Obtaining a mapping relationship between the target domain name and the target service address; Verify whether the following risk assessment conditions are met simultaneously: the target domain name is stored in the domain name list, and the mapping relationship is stored in the mapping list.
7. The domain name management method according to claim 1, characterized in that: The at least one preset list further includes an identity list; The verifying whether the domain name information of the target domain name is stored in the preset list includes: Sending a preset instruction to the target domain name to obtain a static file returned by the target domain name; Parsing the static file to obtain the identity information of the target server; Verify whether the identity information is stored in the identity list.
8. A domain name management device, characterized in that: The domain name management device includes: a detection trigger module, a domain name risk assessment module and a feedback and alarm module; wherein, The detection trigger module is used to obtain the target domain name in response to the detection trigger instruction; The domain name risk assessment module is used to obtain at least one preset list; verify whether the domain name information of the target domain name is stored in the preset list; The feedback and alarm module is used to confirm that the risk assessment result of the target domain name is risk-free when it is confirmed that the domain name information of the target domain name is stored in the preset list; and to confirm that the risk assessment result of the target domain name is risky when it is confirmed that the domain name information of the target domain name is not stored in the preset list.
9. A domain name management device, characterized in that: The domain name management device includes a memory and a processor coupled to the memory; The memory is used to store program data, and the processor is used to execute the program data to implement the domain name management method according to any one of claims 1 to 7.
10. A computer storage medium, characterized in that: The computer storage medium is used to store program data, and when the program data is executed by a computer, it is used to implement the domain name management method according to any one of claims 1 to 7.