Domain name processing method and device, electronic equipment and computer storage medium

Abstract

The invention provides a domain name processing method and device, electronic equipment and a computer storage medium, and is applied to a server, and the method comprises the steps: monitoring a domain name request for accessing a business service; determining a first number of corresponding IPs which cannot be analyzed by the domain name request within a first preset time; if the first number meets a first threshold value, acquiring basic information of the domain name request which cannot be analyzed to the corresponding IP; and triggering a target disaster prevention strategy based on the basic information. In the embodiment of the invention, the anti-risk capability of a customer in an emergency or an unknown situation is improved by monitoring the domain name; when it is determined that the first number of the corresponding IPs cannot be analyzed by the domain name request within the first preset time meets a first threshold value, it is determined that the domain name has a risk, and at the moment, a target disaster prevention strategy needs to be triggered according to basic information of the domain name request of which the corresponding IP cannot be analyzed. Through the mode, the use experience of the user can be improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a domain name processing method, device, electronic equipment and computer storage medium. Background Art

[0002] Domain name services in the Internet are widely used in enterprise portals or app applications. Domain name services are distributed databases that map domain names and IP addresses to each other, so that users can directly access websites or applications with IP addresses corresponding to their domain names through domain names.

[0003] When the domain name service is hijacked by the network or blocked by the operator, the website or app application will be unable to log in or access the specified function; at this time, manual feedback is required so that the system operation and maintenance personnel can locate the problem and solve it by checking the server survival status and domain name related inbound and outbound traffic. The above methods will affect the user experience. Summary of the invention

[0004] In view of this, the embodiments of the present invention provide a domain name processing method, device, electronic device and computer storage medium to solve the problems existing in the prior art that may affect the user experience.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] A first aspect of an embodiment of the present invention shows a method for processing a domain name, which is applied to a server. The method includes:

[0007] Monitor domain name requests to access business services;

[0008] Determine a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time;

[0009] If the first number meets a first threshold, obtaining basic information of the domain name request that cannot be resolved to a corresponding IP address;

[0010] A target disaster prevention strategy is triggered based on the basic information.

[0011] Optionally, also include:

[0012] When the domain name request is resolved to a corresponding IP, a service access is performed based on the IP corresponding to the domain name request to obtain an access success result or an access failure result;

[0013] Counting the number of failed access results of the same domain name request within a second preset time;

[0014] A triggering target disaster prevention strategy is determined based on the number of times.

[0015] Optionally, the determining of triggering a target disaster prevention strategy based on the number of times includes:

[0016] Calculating a failure rate within a second preset time based on the number of times;

[0017] When it is determined that the failure rate reaches a preset percentage, triggering a target disaster prevention strategy;

[0018] Calculate the percentage of the number of access failure results for the same domain name request to the total number of the same domain name request to obtain the failure rate; determine whether the failure rate reaches a preset percentage. If so, trigger the target disaster prevention strategy; if not, no operation is required.

[0019] Optionally, determining a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time includes:

[0020] Parsing the domain name request;

[0021] If it is determined that the resolution result of the domain name request does not belong to the preset result, it is determined that the domain name request cannot be resolved to the corresponding IP, and the domain name of the domain name request is recorded;

[0022] Determining whether the domain name request is intercepted;

[0023] If it is determined that the domain name request is intercepted, it is determined that the domain name request cannot be resolved to a corresponding IP, and the domain name of the domain name request is recorded;

[0024] A first number of domain names for which the domain name request cannot resolve the corresponding IP within a first preset time is counted.

[0025] Optionally, triggering a target disaster prevention strategy based on the basic information includes:

[0026] Determining whether the areas where the operator information in the basic information is located are all the same;

[0027] If so, determining the area where the operator information is located as the target area;

[0028] triggering a target disaster prevention strategy for a domain name request within the target area;

[0029] If not, determining whether the number of different areas where the operator information is located is greater than or equal to a second threshold;

[0030] If it is greater than or equal to, trigger the target disaster prevention strategy for all the domain name requests.

[0031] Optionally, triggering a target disaster prevention strategy based on the basic information includes:

[0032] Determining whether the number of areas where the operator information in the basic information is located is greater than or equal to a third threshold;

[0033] If it is greater than or equal to, determining the area where the number of the same areas is greater than or equal to the third threshold as the target area;

[0034] A target disaster prevention strategy is triggered for a domain name request within the target area.

[0035] A second aspect of an embodiment of the present invention shows a domain name processing device, which is applied to a server, and the device includes:

[0036] A monitoring unit, used to monitor domain name requests for accessing business services;

[0037] A processing unit, configured to determine a first number of domain name requests that cannot be resolved to a corresponding IP within a first preset time; if the first number meets a first threshold, obtain basic information of the domain name requests that cannot be resolved to a corresponding IP;

[0038] A triggering unit is used to trigger a target disaster prevention strategy based on the basic information.

[0039] Optionally, the processing unit is further used for:

[0040] When the domain name request is resolved to a corresponding IP, a service access is performed based on the IP corresponding to the domain name request to obtain an access success result or an access failure result; and the number of failed access results of the same domain name request within a second preset time is counted;

[0041] Correspondingly, the trigger unit is further used to determine the trigger target disaster prevention strategy based on the number of times.

[0042] A third aspect of an embodiment of the present invention shows an electronic device, which is used to run a program, wherein when the program is run, the domain name processing method shown in the first aspect of the embodiment of the present invention is executed.

[0043] A fourth aspect of an embodiment of the present invention shows a computer storage medium, which includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the domain name processing method as shown in the first aspect of the embodiment of the present invention.

[0044] A domain name processing method, device, electronic device and computer storage medium provided based on the above-mentioned embodiment of the present invention are applied to a server, and the method includes: monitoring domain name requests for accessing business services; determining a first number of domain name requests that cannot be resolved to a corresponding IP within a first preset time; if the first number meets a first threshold, obtaining basic information of the domain name requests that cannot be resolved to a corresponding IP; triggering a target disaster prevention strategy based on the basic information. In an embodiment of the present invention, the risk resistance of customers in emergency or unknown situations is improved by monitoring domain names; when it is determined that the first number of domain name requests that cannot be resolved to a corresponding IP within a first preset time meets a first threshold, it is determined that the domain name is at risk, and at this time, it is necessary to trigger a target disaster prevention strategy based on the basic information of the domain name requests that cannot be resolved to a corresponding IP. The above method can improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0046] Figure 1 A schematic diagram of the architecture of a server and a terminal according to an embodiment of the present invention;

[0047] Figure 2 A flowchart of a method for processing a domain name according to an embodiment of the present invention is shown;

[0048] Figure 3 A schematic diagram of a process of triggering a target disaster prevention strategy according to an embodiment of the present invention;

[0049] Figure 4 A flowchart of another method for processing a domain name according to an embodiment of the present invention is shown;

[0050] Figure 5 A flowchart of another method for processing a domain name according to an embodiment of the present invention is shown;

[0051] Figure 6 The present invention is a schematic diagram of the structure of a domain name processing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only 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.

[0053] 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 described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof 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.

[0054] It should be noted that the descriptions of "first", "second", etc. in the present invention are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0055] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0056] See also Figure 1 , is a schematic diagram of the architecture of a server and a terminal shown in an embodiment of the present invention.

[0057] The server 10 is connected to a plurality of terminals 20 .

[0058] The domain name disaster recovery component software package file format jar package, namely the software development kit SDK, is introduced into the server providing domain name services to realize the SDK's external open interface, that is, to provide disaster prevention services to the outside world. In other words, all servers that introduce the SDK can use the service, and the service provided by the SDK has strong stability and security.

[0059] The process of implementing the domain name processing method based on the above architecture includes:

[0060] The user inputs a domain name through the APP or WEB page of the terminal 20 to generate a domain name request corresponding to the domain name and send it to the server 10.

[0061] Server 10 monitors domain name requests for accessing business services; determines a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time; if the first number meets a first threshold, obtains basic information of the domain name requests that cannot be resolved to corresponding IP addresses; and triggers a target disaster prevention strategy based on the basic information.

[0062] In an embodiment of the present invention, the risk resistance of customers in emergency or unknown situations is improved by monitoring domain names; when it is determined that the first number of domain name requests that cannot resolve to the corresponding IP within the first preset time meets the first threshold, it is determined that the domain name is at risk, and at this time, it is necessary to trigger the target disaster prevention strategy based on the basic information of the domain name request that cannot resolve to the corresponding IP, so as to provide system alarms and automatic IP cold standby and / or automatic domain name downgrade, etc., so as to provide users with business services corresponding to the domain name without perception and quickly. The present invention can improve the user experience in the above manner.

[0063] See also Figure 2 , is a flow chart of a method for processing a domain name according to an embodiment of the present invention, which is applied to the above-mentioned server, and the method includes:

[0064] Step S201: monitor domain name requests for accessing business services.

[0065] Optionally, the user can enter the domain name through the terminal APP or web page.

[0066] In the specific implementation of step S201, the server calls the domain name monitoring interface to monitor the domain name request for accessing the business service in the APP or web page in real time.

[0067] Optionally, while monitoring the domain name, the monitoring data can be configured in advance. Specifically, the terminal obtains relevant usage permissions by registering for the domain name disaster prevention background web service. That is, after registering for the service, the server will assign a system code sysCode and an authority code authorityCode to the terminal, so that subsequent calls to the SDK related interfaces can use the system code and authority code for identity authentication. Technical personnel can log in to the SDK background configuration page to perform basic monitoring domain name configuration: configure the domain name to be monitored and the service IP under the domain name. The configuration information includes but is not limited to: domain name, backup domain name, IP, VIP, that is, virtual IP, operator, creation time, and update time, etc.

[0068] Optionally, the server can also directly monitor the backend code of the business service.

[0069] Optionally, when a domain name request is monitored, the unique identification code of the called terminal is recorded, and a long connection is established between the terminal and the server.

[0070] It should be noted that the terminal unique identification code is called through user authorization.

[0071] The calling of the terminal unique identification code involved in this plan complies with the relevant laws and regulations, is used for legal purposes, and does not violate public order and good morals.

[0072] Step S202: Determine a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time.

[0073] It should be noted that the specific process of implementing step S202 includes the following steps:

[0074] Step S11: parsing the domain name request.

[0075] It should be noted that the domain name service is a distributed database that maps domain names and IP addresses to each other.

[0076] Step S12: Determine whether the resolution result of the domain name request belongs to a preset result. If not, execute step S13. If yes, do not consider the domain name request.

[0077] In the process of specifically implementing step S11 and step S12, the domain name request is parsed to determine whether it is parsed to the IP configured under the specified domain name. If the IP configured under the specified domain name cannot be parsed, it is determined that the parsing result of the domain name request does not belong to the preset result, that is, the IP address corresponding to the domain name in the domain name request cannot be found from the domain name service; if the IP configured under the specified domain name is parsed, the IP address corresponding to the domain name of the domain name request stored in the domain name service is used as the parsing result, and the domain name request is not considered.

[0078] The preset result is used to indicate whether the IP configured under the specified domain name cannot be resolved.

[0079] Optionally, the specific implementation process of step S11 and step S12 can also be to parse the domain name request to determine whether the resolution result obtained is an ip or vip that is not configured by the system. If so, it is determined that the resolution result of the domain name request does not belong to the preset result, that is, the IP address corresponding to the domain name in the domain name request cannot be found from the domain name service; if not, the IP address corresponding to the domain name of the domain name request stored in the domain name service is used as the resolution result, and the domain name request is not considered.

[0080] Step S13: Determine that the domain name request cannot be resolved to a corresponding IP, and record the domain name of the domain name request.

[0081] It should be noted that the domain name requested is recorded regardless of whether the domain name is the same as the domain name requested.

[0082] Step S14: Determine whether the domain name request is intercepted. If so, execute step S15; if not, ignore the domain name request.

[0083] In the process of implementing step S14, it is determined whether a notification from the operator system that the SDK component system domain name is affected or a notification from the anti-fraud center that the SDK domain name is hijacked is received. If received, it means that the domain name request is intercepted, and step S15 is executed. If not, it means that the domain name request is not intercepted, and the domain name request is not considered.

[0084] Step S15: Determine that the domain name request cannot be resolved to a corresponding IP, and record the domain name of the domain name request.

[0085] In the process of implementing step S15, if there is any blocked domain name, that is, the domain name request cannot be resolved to the domain name of the corresponding IP.

[0086] Step S16: Counting a first number of domain names whose domain name requests cannot be resolved to corresponding IP addresses within a first preset time.

[0087] In the specific implementation of step S16, the number of the domain names recorded within the first preset time is counted and taken as the first number.

[0088] It should be noted that the first preset time is set in advance by the technicians based on actual conditions or multiple tests.

[0089] Step S203: Determine whether the first number meets a first threshold value. If so, execute step S204; if not, return to execute step S201.

[0090] In the process of implementing step S203, it is determined whether the disaster prevention strategy can be triggered at this time, and whether the first number exceeds the preset first threshold. If it exceeds, it means that the disaster prevention strategy can be triggered, and step S204 is executed; if it does not exceed, it means that the disaster prevention strategy cannot be triggered at this time, and the domain name of the recorded domain name request can be directly output to the technical staff for the technical staff to view and process, and return to execute step S201.

[0091] Step S204: Obtain basic information of the domain name request that cannot be resolved to a corresponding IP.

[0092] It should be noted that the basic information includes the regional operator used by the terminal that submits the domain name request, that is, operator information, such as operator 1 in area A and operator 2 in area B.

[0093] Step S205: triggering a target disaster prevention strategy based on the basic information.

[0094] It should be noted that the specific implementation process of step S205 is as follows: Figure 3 As shown, the following steps are included:

[0095] Step S301: determine whether the areas where the operator information in the basic information is located are all the same. If so, determine that the target disaster prevention strategy can be triggered, and execute steps S302 and S303; if not, execute step S304.

[0096] In the specific implementation of step S301, the scope of executing the target disaster prevention strategy is determined by whether the areas where the operator information is located are the same area. If so, step S302 and step S303 are executed; if not, step S304 is executed.

[0097] Step S302: Determine the area where the operator information is located as the target area.

[0098] Step S303: triggering a target disaster prevention strategy for a domain name request within the target area.

[0099] In the specific implementation of step S304, a target disaster prevention strategy is triggered by requesting a domain name in the target area through a long link.

[0100] It should be noted that the target disaster prevention strategy includes any one or more combinations of the first disaster prevention strategy, the second disaster prevention strategy and the third disaster prevention strategy.

[0101] The first disaster prevention strategy is used to instruct to switch the domain name, specifically switching the domain name in the domain name request to the backup domain name.

[0102] The second disaster prevention strategy is used to refer to domain name cold backup or IP cold backup, specifically, domain name cold backup is performed on domain names within a first preset time; or IP cold backup is performed on domain names corresponding to a second preset time.

[0103] The third disaster prevention strategy is used to instruct the alarm to be issued according to the pre-selected alarm method, such as SMS and intelligent AI voice, alarm frequency, such as once within 15 minutes, contact information and other information, so that technical personnel can handle it in time.

[0104] Optionally, the target disaster prevention strategy may further include synchronizing disaster information that the domain name request cannot connect to the corresponding IP in time or cannot successfully handshake with the server through the IP in time to the terminal app or web.

[0105] It should be noted that the target disaster prevention strategy not only includes the disaster prevention strategies shown above, but also may include other disaster prevention strategies, which can be set in advance in the configuration page by the technicians based on experiments or experience.

[0106] Step S304: determine whether the number of different areas where the operator information is located is greater than or equal to a second threshold, if so, execute step S305; if less than, execute step S306.

[0107] In the specific implementation of step S304, by determining the area where the operator information is located, the scope of the domain name affected by the disaster is determined, that is, whether the scope of executing the target disaster prevention strategy is comprehensive. The number of each area where the operator information is located is counted; it is determined whether the number is greater than or equal to the second threshold, if it is greater than or equal to, step S305 is executed; if it is less than, step S306 is executed.

[0108] It should be noted that the second threshold is set by technicians based on experience or multiple experiments, and the embodiment of the present invention does not limit this.

[0109] Step S305: triggering a target disaster prevention strategy for all the domain name requests.

[0110] In the specific implementation of step 305, the target disaster prevention strategy is triggered for all current domain name requests, that is, a comprehensive downgrade is performed.

[0111] Step S306: taking each area where the operator information is located as a target area.

[0112] Step S307: triggering a target disaster prevention strategy for a domain name request in the target area.

[0113] It should be noted that the specific implementation process of step S306 to step S307 is the same as the specific implementation process of step S302 to step S303 above, and they can refer to each other.

[0114] In an embodiment of the present invention, the risk resistance of customers in emergency or unknown situations is improved by monitoring domain names; when it is determined that the first number of domain name requests that cannot resolve to the corresponding IP within the first preset time meets the first threshold, it is determined that the domain name is at risk, and at this time, it is necessary to trigger the target disaster prevention strategy based on the basic information of the domain name request that cannot resolve to the corresponding IP, so as to provide system alarms and automatic IP cold standby and / or automatic domain name downgrade, etc., so as to provide users with business services corresponding to the domain name without perception and quickly. The present invention can improve the user experience in the above manner.

[0115] Based on the domain name processing method shown in the above embodiment of the present invention, the embodiment of the present invention also shows a flow chart of another domain name processing method, such as Figure 4 As shown, the method includes:

[0116] Step S401: monitor domain name requests for accessing business services.

[0117] Step S402: Determine a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time.

[0118] Step S403: Determine whether the first number meets a first threshold value. If so, execute step S404; if not, return to execute step S401.

[0119] Step S404: Obtain basic information of the domain name request that cannot be resolved to a corresponding IP.

[0120] It should be noted that the specific implementation process of step S401 to step S404 is the same as the specific implementation process of step S201 to step S204 described above, and they can refer to each other.

[0121] Step S405: determine whether the number of areas where the operator information in the basic information is located is greater than or equal to a third threshold, if so, execute steps S406 and S407; if not, determine that the domain name in the area is not affected by the disaster.

[0122] In the process of implementing step 405, for each area where the operator information is located, the number of operator information in the same area is counted; it is determined whether the number of operator information in the same area is greater than or equal to a third threshold value, if it is greater than or equal to, steps S406 and S407 are executed for the area; if not, it is determined that the domain name of the area is not affected by the disaster.

[0123] It should be noted that the third threshold is set by technicians based on experience or multiple experiments, and the embodiment of the present invention does not limit this.

[0124] Step S406: Determine the area whose number of identical areas is greater than or equal to the third threshold as the target area.

[0125] Step S407: triggering a target disaster prevention strategy for a domain name request in the target area.

[0126] It should be noted that the specific implementation process of step S307 is the same as the specific implementation process of the above-mentioned step S207, and they can refer to each other.

[0127] In an embodiment of the present invention, the risk resistance of customers in emergency or unknown situations is improved by monitoring domain names; when it is determined that the first number of domain name requests that cannot resolve the corresponding IP within the first preset time meets the first threshold, it is determined that the domain name is at risk, and for each area where the operator information is located, the number of operator information in the same area is counted; it is determined whether the number of operator information in the same area is greater than or equal to the third threshold, and if it is greater than or equal to, the target disaster prevention strategy is executed for the area, so as to provide system alarms and automatic IP cold standby and / or automatic domain name downgrade, etc., so as to provide users with business services corresponding to the domain name without perception and quickly. The present invention can improve the user experience in the above manner.

[0128] Based on the domain name processing method shown in the above embodiment of the present invention, the embodiment of the present invention also shows a flow chart of another domain name processing method, such as Figure 5 As shown, the method includes:

[0129] Step S501: monitor domain name requests for accessing business services.

[0130] It should be noted that the specific implementation process of step S501 is the same as the specific implementation process of the above-mentioned steps S201 to S202, and they can refer to each other.

[0131] Step S502: when the domain name request is resolved to a corresponding IP, a business service access is performed based on the IP corresponding to the domain name request to obtain an access success result or an access failure result.

[0132] In the process of implementing step S502, the domain name in the monitored domain name request is resolved into an IP; and the business service is accessed based on the IP. If it is determined that the server and the terminal corresponding to the domain name request can shake hands within a certain period of time, it means that the access is successful and an access success result is generated; if it is determined that the server and the terminal corresponding to the domain name request cannot shake hands within a certain period of time, it means that the access has timed out and an access failure result is generated. At this time, the domain name is written into the service es or db in the background of the software development tool kit sdk.

[0133] Step S503: Count the number of failed access results of the same domain name request within a second preset time period.

[0134] In the specific implementation of step S503, the number of failed access results when different terminals initiate the same domain name request within the second preset time is monitored, that is, the number of times the same domain name is stored in the service es or database db of the software development tool kit sdk background is obtained.

[0135] Step S504: triggering a target disaster prevention strategy based on the number of times.

[0136] The specific process of implementing step S504 includes the following steps:

[0137] Step S21: Calculate the failure rate within a second preset time based on the number of times.

[0138] Step S22: Determine whether the failure rate reaches a preset percentage. If so, execute step S23. If not, no operation is required.

[0139] Step S23: triggering the target disaster prevention strategy.

[0140] In the specific implementation process of step S21 to step S23, the percentage of the number of access failure results for the same domain name request to the total number of the same domain name request is calculated to obtain the failure rate; it is determined whether the failure rate reaches a preset percentage, and if so, the target disaster prevention strategy is triggered; if not, no operation is required.

[0141] In an embodiment of the present invention, the risk resistance of customers in emergency or unknown situations is improved by monitoring domain names; when the domain name request is resolved to the corresponding IP, the business service is accessed based on the IP corresponding to the domain name request to obtain a successful access result or a failed access result; the number of failed access results within a second preset time is counted; based on the number, a target disaster prevention strategy is triggered to provide system alarms and automatic IP cold standby and / or automatic domain name downgrade, etc., so as to provide users with business services corresponding to the domain name without perception and quickly. The present invention can improve the user experience through the above method.

[0142] Based on the domain name processing method shown in the above embodiment of the present invention, the embodiment of the present invention also discloses a domain name processing device, such as Figure 6 As shown, the device comprises:

[0143] A monitoring unit 601 is used to monitor domain name requests for accessing business services;

[0144] Processing unit 602 is used to determine a first number of domain name requests that cannot be resolved to a corresponding IP within a first preset time; if the first number meets a first threshold, obtain basic information of the domain name requests that cannot be resolved to a corresponding IP;

[0145] The triggering unit 603 is used to trigger a target disaster prevention strategy based on the basic information.

[0146] It should be noted that the specific principles and execution processes of each unit in the domain name processing device disclosed in the above-mentioned embodiment of the present application are the same as the domain name processing method shown in the above-mentioned embodiment of the present application. Please refer to the corresponding parts of the domain name processing method disclosed in the above-mentioned embodiment of the present application, and no further details will be given here.

[0147] In an embodiment of the present invention, the risk resistance of customers in emergency or unknown situations is improved by monitoring domain names; when it is determined that the first number of domain name requests that cannot resolve to the corresponding IP within the first preset time meets the first threshold, it is determined that the domain name is at risk, and at this time, it is necessary to trigger the target disaster prevention strategy based on the basic information of the domain name request that cannot resolve to the corresponding IP, so as to provide system alarms and automatic IP cold standby and / or automatic domain name downgrade, etc., so as to provide users with business services corresponding to the domain name without perception and quickly. The present invention can improve the user experience in the above manner.

[0148] Optionally, based on the domain name processing device shown in the above embodiment of the present invention, the processing unit 602 is further used to: when the domain name request is resolved to a corresponding IP, perform service access based on the IP corresponding to the domain name request to obtain an access success result or an access failure result; count the number of failed access results of the same domain name request within a second preset time;

[0149] Correspondingly, the triggering unit 603 is further used to determine the triggering target disaster prevention strategy based on the number of times.

[0150] Optionally, based on the domain name processing device shown in the above embodiment of the present invention, the processing unit 602 for determining the first number of IP addresses to which the domain name request cannot be resolved within the first preset time is specifically configured to:

[0151] Parsing the domain name request;

[0152] If it is determined that the resolution result of the domain name request does not belong to the preset result, it is determined that the domain name request cannot be resolved to the corresponding IP, and the domain name of the domain name request is recorded;

[0153] Determining whether the domain name request is intercepted;

[0154] If it is determined that the domain name request is intercepted, it is determined that the domain name request cannot be resolved to a corresponding IP, and the domain name of the domain name request is recorded;

[0155] A first number of domain names for which the domain name request cannot resolve the corresponding IP within a first preset time is counted.

[0156] Optionally, based on the domain name processing device shown in the above embodiment of the present invention, the triggering unit 603 for triggering the target disaster prevention strategy based on the basic information is specifically used to:

[0157] Determining whether the areas where the operator information in the basic information is located are all the same;

[0158] If so, determining the area where the operator information is located as the target area;

[0159] triggering a target disaster prevention strategy for a domain name request within the target area;

[0160] If not, determining whether the number of different areas where the operator information is located is greater than or equal to a second threshold;

[0161] If it is greater than or equal to, the target disaster prevention strategy is triggered for all the domain name requests.

[0162] Optionally, based on the domain name processing device shown in the above embodiment of the present invention, the triggering unit 603 for triggering the target disaster prevention strategy based on the basic information is specifically used to:

[0163] Determining whether the number of areas where the operator information in the basic information is located is greater than or equal to a third threshold;

[0164] If it is greater than or equal to, determining the area where the number of the same areas is greater than or equal to the third threshold as the target area;

[0165] A target disaster prevention strategy is triggered for a domain name request within the target area.

[0166] The embodiment of the present invention also discloses an electronic device, which is used to run a database storage process, wherein the above-mentioned Figures 2 to 5 How to handle public domain names.

[0167] The embodiment of the present invention also discloses a computer storage medium, wherein the storage medium includes a storage database storage process, wherein when the database storage process is running, the device where the storage medium is located is controlled to execute the above Figures 2 to 5 How to handle public domain names.

[0168] In the context of the present disclosure, a computer storage medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0169] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0170] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in 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 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 may 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.

[0171] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing a domain name. It is characterized in that Applied to a server, the method comprises: Monitor domain name requests to access business services; Determine a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time; If the first number meets a first threshold, obtaining basic information of the domain name request that cannot be resolved to the corresponding IP; A target disaster prevention strategy is triggered based on the basic information.

2. The method according to claim 1, It is characterized in that Also includes: When the domain name request is resolved to a corresponding IP, a service access is performed based on the IP corresponding to the domain name request to obtain an access success result or an access failure result; Counting the number of failed access results of the same domain name request within a second preset time; A triggering target disaster prevention strategy is determined based on the number of times.

3. The method according to claim 2, It is characterized in that The determining of triggering a target disaster prevention strategy based on the number of times includes: Calculating a failure rate within a second preset time based on the number of times; When it is determined that the failure rate reaches a preset percentage, triggering a target disaster prevention strategy; Calculate the percentage of the number of access failure results for the same domain name request to the total number of the same domain name request to obtain the failure rate; determine whether the failure rate reaches a preset percentage. If so, trigger the target disaster prevention strategy; if not, no operation is required.

4. The method according to claim 1, It is characterized in that Determining a first number of domain name requests that cannot be resolved to corresponding IP addresses within a first preset time includes: Parsing the domain name request; If it is determined that the resolution result of the domain name request does not belong to the preset result, it is determined that the domain name request cannot be resolved to the corresponding IP, and the domain name of the domain name request is recorded; Determining whether the domain name request is intercepted; If it is determined that the domain name request is intercepted, it is determined that the domain name request cannot be resolved to a corresponding IP, and the domain name of the domain name request is recorded; A first number of domain names for which the domain name request cannot resolve the corresponding IP within a first preset time is counted.

5. The method according to claim 1, It is characterized in that The target disaster prevention strategy is triggered based on the basic information, including: Determining whether the areas where the operator information in the basic information is located are all the same; If so, determining the area where the operator information is located as the target area; triggering a target disaster prevention strategy for a domain name request within the target area; If not, determining whether the number of different areas where the operator information is located is greater than or equal to a second threshold; If it is greater than or equal to, trigger the target disaster prevention strategy for all the domain name requests.

6. The method according to claim 1, It is characterized in that The target disaster prevention strategy is triggered based on the basic information, including: Determining whether the number of areas where the operator information in the basic information is located is greater than or equal to a third threshold; If it is greater than or equal to, determining the area where the number of the same areas is greater than or equal to the third threshold as the target area; A target disaster prevention strategy is triggered for a domain name request within the target area.

7. A domain name processing device, It is characterized in that Applied to a server, the device comprises: A monitoring unit, used to monitor domain name requests for accessing business services; A processing unit, configured to determine a first number of domain name requests that cannot be resolved to a corresponding IP within a first preset time; if the first number meets a first threshold, obtain basic information of domain name requests that cannot be resolved to a corresponding IP; A triggering unit is used to trigger a target disaster prevention strategy based on the basic information.

8. The device according to claim 7, It is characterized in that The processing unit is further used for: When the domain name request is resolved to a corresponding IP, a service access is performed based on the IP corresponding to the domain name request to obtain an access success result or an access failure result; Counting the number of failed access results of the same domain name request within a second preset time; Correspondingly, the trigger unit is further used to determine the trigger target disaster prevention strategy based on the number of times.

9. An electronic device, It is characterized in that The electronic device is used to run a program, wherein the program, when running, executes the domain name processing method as described in any one of claims 1-6.

10. A computer storage medium, It is characterized in that The storage medium includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the domain name processing method according to any one of claims 1 to 6.

Images