CN113301177A - Domain name anti-blocking method and device - Google Patents
Domain name anti-blocking method and device Download PDFInfo
- Publication number
- CN113301177A CN113301177A CN202110461468.0A CN202110461468A CN113301177A CN 113301177 A CN113301177 A CN 113301177A CN 202110461468 A CN202110461468 A CN 202110461468A CN 113301177 A CN113301177 A CN 113301177A
- Authority
- CN
- China
- Prior art keywords
- domain name
- access
- configuration file
- standby
- main
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000004048 modification Effects 0.000 claims description 7
- 238000012986 modification Methods 0.000 claims description 7
- 230000004044 response Effects 0.000 claims description 3
- 230000000903 blocking effect Effects 0.000 abstract description 6
- 238000007789 sealing Methods 0.000 abstract description 3
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a domain name anti-blocking method and device. According to the technical scheme provided by the embodiment of the application, the domain name blocking fault is repaired under the condition that a user does not sense the domain name blocking fault by issuing a new domain name configuration and a mode of combining multi-domain name self-rescue of the client. When the access of the main domain name in a certain area fails, the client side can try to access a plurality of standby domain names until the access is successful. And the client side can count the access failure times and success times of each domain name on the same day, and after the main domain name is determined to be forbidden, the client side actively modifies the local domain name configuration file and upgrades the available standby domain name into the main domain name so as to stop domain name switching and ensure the access fluency of the user until the server side issues a new non-forbidden domain name configuration file. Because the domain name switching speed is high, only the condition of slow short-time access exists during the domain name sealing period, and a fault period does not exist, so that the stability and maintainability of the client are improved, and the user experience is further improved.
Description
Technical Field
The embodiment of the application relates to the technical field of network communication, in particular to a method, a device, equipment and a storage medium for preventing and forbidding domain names.
Background
As a global Internet client product, the problem that the domain name is suddenly blocked in a certain area is inevitable in the long-term use process, so that the Internet client product cannot be used in the blocked area, the image of the Internet client product is seriously damaged, the user viscosity is reduced, and great negative effects are caused.
At present, a common method for solving this problem is to issue a domain name configuration to a client in a sealed area, where the domain name configuration may attempt to be issued in multiple ways, such as socket (socket), https (hyper Text Transfer Protocol over secure socket layer), GitHub (hosting platform for open source and private software projects), and the like, so as to ensure a success rate of issuing the configuration. After receiving the domain name configuration file, the client performs domain name replacement operation on the resource request in the client so as to achieve the purpose of preventing blocking.
However, in the current technology, the domain name is disabled, and a new domain name configuration is issued, and the middle time is a failure period, during which the user cannot successfully access the resource.
Disclosure of Invention
The embodiment of the application provides a domain name anti-blocking method, a domain name anti-blocking device, domain name anti-blocking equipment and a storage medium, so that a client can actively replace the use of a domain name according to the access condition of the client, and the generation of a fault period is avoided.
In a first aspect, an embodiment of the present application provides a domain name anti-blocking method, including:
receiving a domain name access request, and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a plurality of standby domain names;
when the main domain name fails to be accessed, allocating a standby domain name for resource access;
acquiring the access failure times of the main domain name and the access success times of each standby domain name within a preset time interval;
and determining whether to modify the currently and actually used domain name configuration file or not according to the access failure times of the main domain name access and the access success times of the standby domain name.
In a second aspect, an embodiment of the present application provides a domain name anti-blocking device, including:
an access request receiving module: the domain name access system is used for receiving a domain name access request and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a plurality of standby domain names;
the standby domain name access module: the method comprises the steps of allocating a standby domain name for resource access when the main domain name fails to be accessed;
visit success or failure statistics module: the method comprises the steps of obtaining access failure times of a main domain name and access success times of a standby domain name within a preset time interval;
a configuration file modification module: and the system is used for determining whether to modify the currently and actually used domain name configuration file according to the access failure times of the main domain name access and the access success times of the standby domain name.
In a third aspect, an embodiment of the present application provides a computer device, including: a memory and one or more processors;
the memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the domain name anti-blocking method of the first aspect.
In a fourth aspect, embodiments of the present application provide a storage medium containing computer-executable instructions for performing the domain name anti-blocking method according to the first aspect when executed by a computer processor.
According to the method and the device, domain name sealing faults are repaired under the condition that a user is unaware by issuing new domain name configuration and self-rescue of multiple domain names of the client before issuing the new domain name configuration, a local domain name configuration file of the client comprises a main domain name and a plurality of standby domain names, the client tries to access the plurality of standby domain names after the main domain name is failed to access, the client counts the access failure times of the main domain name and the access success times of the standby domain names within a period of time, and when the access failure times of the main domain name reach enough number and the access success times of the standby domain names also reach enough number, the client actively modifies the local domain name configuration file and upgrades the standby domain names into the main domain name to stop domain name switching and ensure the smoothness of user access. Due to the fact that the domain name switching time is short, only the condition that access is slow in a short time is achieved during the domain name blocking period, a fault period does not exist, stability and maintainability of the client are improved, and user experience is further improved.
Drawings
Fig. 1 is a flowchart of a domain name anti-blocking method provided in an embodiment of the present application;
fig. 2 is a flowchart of another domain name anti-blocking method provided in an embodiment of the present application;
fig. 3 is a flowchart of another domain name anti-blocking method provided in an embodiment of the present application;
fig. 4 is a flowchart of another domain name anti-blocking method provided in an embodiment of the present application;
fig. 5 is a flowchart of another domain name anti-blocking method provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of a domain name anti-blocking device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another domain name anti-blocking device provided in an embodiment of the present application;
fig. 8 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, specific embodiments of the present application will be described in detail with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some but not all of the relevant portions of the present application are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The embodiment of the application provides a domain name anti-blocking method, a domain name anti-blocking device, domain name anti-blocking equipment and a storage medium. According to the method and the device, the domain name seal failure is repaired under the condition that a user does not sense the domain name seal failure through the mode of issuing the new domain name configuration and the mode of combining multi-domain name self-rescue of the client before issuing the new domain name configuration. The local domain name configuration file content of the client comprises the following contents: a primary replacement domain name and a plurality of backup replacement domain names for each original domain name. When a primary replacement domain name in a certain region fails to be accessed, the client side can try to access a plurality of standby domain names until the access is successful. And the client side can count the access failure times of the main domain name and the access success times of each standby domain name on the same day, and when the access failure times of the main domain name reach a sufficient number and the access success times of a certain standby domain name also reach a sufficient number, the client side actively modifies the local domain name configuration file and upgrades the standby domain name into the main domain name so as to stop domain name switching and ensure the access smoothness of the user. When the server side issues a new non-blocked domain name configuration file, the client side uses the latest domain name configuration file. Due to the fact that the domain name switching time is short, only the condition that access is slow in a short time is achieved during the domain name blocking period, a fault period does not exist, stability and maintainability of the client are improved, and user experience is further improved.
The following are detailed below.
Fig. 1 is a flowchart of a domain name anti-blocking method provided in an embodiment of the present application, where the domain name anti-blocking method provided in the embodiment of the present application may be executed by a domain name anti-blocking device, and the domain name anti-blocking device may be implemented in a hardware and/or software manner and integrated in a computer device.
The following description will be given taking as an example a domain name anti-blocking apparatus executing a domain name anti-blocking method. Referring to fig. 1, the method for preventing a domain name from being blocked includes:
101: receiving a domain name access request, and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request.
The embodiment of the application is applied to the client. The client is also called a user side, and is a program corresponding to the server and providing local services for the client. Some applications which only run locally do not need to cooperate with other service terminals, but the application embodiments need to perform resource access, so the applications are installed on a common client and need to cooperate with the service terminals to run. In the embodiment of the present application, the commonly used client includes a web browser, an email box for receiving and sending an email, and instant messaging software. The client is usually borne on a terminal, and the terminal comprises intelligent devices such as a desktop computer, a notebook computer, an intelligent printer, an intelligent mobile phone, an intelligent bracelet and an intelligent watch.
And receiving a domain name access request input by a user on the client, and accessing the corresponding resource through the domain name access request after the access is successful. In the embodiment of the application, in order to avoid a failure period when domain name access fails and save a time of a user waiting for allocating another domain name, a plurality of domain names are configured in advance on a domain name configuration file of a client, and for facilitating future application, one domain name is selected from the plurality of domain names to be used as a main domain name, and the other domain names are used as standby domain names. The mode of selecting the main domain name can be random selection, but in order to better meet the public requirements and provide more stable domain name access service, the domain name which is more commonly used and has higher access success rate is usually selected as the main domain name. Specifically, in the embodiment of the present application, the domain name profile stored in the client includes a main domain name and a plurality of standby domain names.
When a user puts forward a domain name access request through a client, a main domain name in a currently and actually used domain name configuration file is allocated to access resources according to the domain name access request of the user. That is, in the client, there may be more than one domain name profile stored, and there may be different multiple domain name profiles stored. Similarly, each domain name configuration file comprises a plurality of domain names, which are divided into a main domain name and at least one standby domain name. The currently actually used domain name profile is also the domain name profile currently in use. In a plurality of domain name configuration files stored by a client, specific domain names contained in each domain name configuration file may be completely the same or different, or may be partially the same and partially different.
102: and when the main domain name fails to be accessed, allocating a plurality of standby domain names for resource access.
When receiving a domain name access request, allocating a domain name for the currently used domain name configuration file for resource access. Firstly, a main domain name of a domain name configuration file is selected for resource access, and when the access fails, a standby domain name is immediately allocated for resource access. In the embodiment of the present application, a plurality of domain names in each domain name configuration file are sorted in advance, and one domain name is allocated as a main domain name, which is usually sorted in the first order. The spare domain names may be sorted according to the access frequency of each spare domain name, or may be assigned to each spare domain name a sorter, where the sorter is a character or a plurality of characters, which may be numbers or letters, and is used to sequentially sort the spare domain names. For example, the standby domain names are respectively a, b, c, d and … … in their sequence, and are sorted according to the sequence of the letters, when the access of the main domain name fails, the standby domain name a is selected for access first, the access of the standby domain name a fails, and then the standby domain name b is used for access, and so on. In another implementation manner, in the embodiment of the present application, each standby domain name of the domain name configuration file may not be ordered, and when the access of the main domain name fails, one of the standby domain names is randomly selected for resource access. Or when the standby domain name is only one, the standby domain name is automatically used for resource access when the access of the main domain name fails.
By self-rescue of the client to domain name access failure, the transition time for switching from the domain name with access failure to another backup domain name is short, so that the existence of a failure period is avoided, and the domain name is repaired under the condition that a user does not sense the failure
103: and acquiring the access failure times of the main domain name and the access success times of each standby domain name in a preset time interval.
In the embodiment of the application, the times of time domain name access success or failure of each time of domain name access are recorded, and the times of domain name access success or failure are counted at intervals of a fixed time length. In the embodiment of the application, when the self-rescue of the client is expected to be realized, the domain name configuration file is modified when the failure times of the main domain name in the domain name configuration file are excessive and the access success times of the standby domain name in the domain name configuration file reach a set value. Therefore, the access failure times of the main domain name and the access success times of the standby domain name within the preset time interval are obtained from the counted access success or failure times of the domain names. The preset time interval is, for example, one day, half day, three days, half week, one hour, etc. The specific duration of the preset time interval is not clear, and different numerical settings can be provided according to different use scenes and combined with actual needs.
As shown in fig. 2, as a preferred implementation manner, the domain name profile of this embodiment includes a main domain name and a plurality of standby domain names, where each standby domain name and a secondary domain name of the main domain name are different from each other. And the standby domain names in the domain name configuration file are arranged according to a preset sequence.
Step 203, when the access of the main domain name fails, allocating a standby domain name for resource access, including: when the main domain name access fails, allocating a first standby domain name for resource access, and when the first standby domain name access fails, sequentially allocating other standby domain names according to a preset sequence for resource access until any one standby domain name is successfully accessed.
The method specifically comprises the following steps: 2031: when the main domain name fails to be accessed, allocating a first standby domain name for resource access; 2032: detecting whether the first standby domain name is successfully accessed, if so, executing 204, otherwise, executing 2033: sequentially distributing and sequencing the next standby domain name according to a preset sequence to access resources; 2034: and detecting whether the next standby domain name ordered in the sequence is successfully accessed, if so, executing 204, otherwise, circulating 2033 until the access is successful.
104: and determining whether to modify the currently and actually used domain name configuration file or not according to the access failure times of the main domain name access and the access success times of the standby domain name.
In the embodiment of the application, the access failure times of the main domain name and the access success times of the standby domain name are obtained in the statistics of the access success or failure times of the domain name at regular intervals.
Specifically, determining whether to modify the currently and actually used domain name configuration file according to the access failure times of the main domain name access and the access success times of the standby domain name includes: and when the access failure times of the main domain name reach a first threshold value and the access success times of one standby domain name reach a second threshold value, modifying the currently and actually used domain name configuration file.
In this embodiment of the application, both the first threshold and the second threshold are positive integers, and the first threshold may be equal to the second threshold, for example, both the first threshold and the second threshold are 3, and on the other hand, the first threshold and the second threshold may also be unequal, for example, the first threshold is 3 and the second threshold is 4.
As a further preferred embodiment, when the domain name configuration file actually used at present is determined to be modified according to the access failure times of the main domain name access and the access success times of the standby domain names, the domain name configuration file actually used at present is modified, specifically, the main domain name in the domain name configuration file actually used at present is replaced with the standby domain name whose access success times reach the second threshold.
Fig. 3 shows another domain name anti-blocking method provided in the embodiment of the present application, which includes the following steps:
301: receiving a domain name access request, and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a standby domain name. The standby domain names are multiple, and are preferably arranged in a preset order.
302: and when the main domain name fails to be accessed, allocating the standby domain name for resource access. In one aspect, the standby domain names are multiple, when the main domain name fails to be accessed, the first standby domain name is allocated for resource access, and when the first standby domain name fails to be accessed, other standby domain names are sequentially allocated according to a preset sequence for resource access until any one standby domain name is successfully accessed.
303: and acquiring the access failure times of the main domain name and the access success times of the standby domain name within a preset time interval.
304: and determining whether to modify the currently and actually used domain name configuration file or not according to the access failure times of the main domain name access and the access success times of the standby domain name. Preferably, when the number of times of access failure of the main domain name reaches a first threshold value and the number of times of access success of one of the standby domain names reaches a second threshold value, the domain name configuration file which is actually used at present is modified. One of the possible embodiments for modifying the domain name configuration file is as follows: and replacing the main domain name in the currently and actually used domain name configuration file with the standby domain name with the access success frequency reaching a second threshold value.
305: receiving a domain name configuration file currently sent by a server, and defining the domain name configuration file currently sent by the server as a current domain name configuration file.
In the embodiment of the application, the domain name configuration files stored by the client can be distributed by the server. Preferably, a plurality of domain name configuration files are locally stored in the client, and the plurality of domain name configuration files can be classified into three types, wherein one type is a currently actually used domain name configuration file, the other type is a domain name configuration file last issued by the server, and the other type is a domain name configuration file currently issued by the server and a current domain name configuration file of accumulated water. In this step, the domain name configuration file currently sent by the server is received, and the domain name configuration file is a class of domain name configuration files currently issued by the server.
306: and comparing whether the domain name configuration file sent last time by the server is consistent with the current domain name configuration file, if so, continuing to use the currently and actually used domain name configuration file, and otherwise, replacing the currently and actually used domain name configuration file with the current domain name configuration file.
As shown in fig. 4, fig. 4 shows another domain name anti-blocking method provided in the embodiment of the present application, including:
401: receiving a domain name access request, and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name profile includes a primary domain name and a plurality of backup domain names.
402: and when the main domain name fails to be accessed, allocating the standby domain name for resource access. In one aspect, the standby domain names are multiple, when the main domain name fails to be accessed, the first standby domain name is allocated for resource access, and when the first standby domain name fails to be accessed, other standby domain names are sequentially allocated according to a preset sequence for resource access until any one standby domain name is successfully accessed.
403: and acquiring the access failure times of the main domain name and the access success times of the standby domain name within a preset time interval.
404: and determining whether to modify the currently and actually used domain name configuration file or not according to the access failure times of the main domain name access and the access success times of the standby domain name. Preferably, when the number of times of access failure of the main domain name reaches a first threshold value and the number of times of access success of one of the standby domain names reaches a second threshold value, the domain name configuration file which is actually used at present is modified. One of the possible embodiments for modifying the domain name configuration file is as follows: and replacing the main domain name in the currently and actually used domain name configuration file with the standby domain name with the access success frequency reaching a second threshold value.
405: receiving a domain name configuration file currently sent by a server, and defining the domain name configuration file currently sent by the server as a current domain name configuration file.
Specifically, for the domain name configuration file currently sent by the receiving server in step 405, the method includes: 4051: sending a domain name configuration file request to a server side every other preset time length; 4052: and receiving the domain name configuration file fed back by the server end in response to the domain name configuration file request. That is, the client actively sends a domain name configuration file request to the server, so that the server issues the domain name configuration file.
In the embodiment, the client locally has three domain name replacement configuration files, which are a domain name configuration file currently sent by the server, an actually used domain name configuration file, and a domain name configuration file last sent by the server. And at the client, comparing the domain name configuration file newly issued by the server, namely whether the current domain name configuration file is consistent with the domain name configuration file issued last time, if so, keeping the currently and actually used domain name configuration file unchanged, otherwise, replacing the currently and actually used domain name configuration file with the domain name configuration file newly issued by the server.
406: and comparing whether the domain name configuration file sent last time by the server is consistent with the current domain name configuration file, if so, continuing to use the currently and actually used domain name configuration file, and otherwise, replacing the currently and actually used domain name configuration file with the current domain name configuration file.
According to the method, the domain name sealing fault is repaired under the condition that a user is unaware by issuing a new domain name configuration stage and before issuing the new domain name configuration stage, a local domain name configuration file of the client comprises a main domain name and a plurality of standby domain names, when the access failure of the main domain name is failed, the client tries to access each standby domain name, the client counts the access failure times of the main domain name and the access success times of each standby domain name within a period of time, and when the access failure times of the main domain name reach enough number and the access success times of the standby domain names also reach enough number, the client actively modifies the local domain name configuration file and upgrades the standby domain names into the main domain name to stop domain name switching and ensure the smoothness of the user access. When the server side issues a new non-blocked domain name configuration file, the client side uses the latest domain name configuration file. Due to the fact that the domain name switching time is short, only the condition that access is slow in a short time is achieved during the domain name blocking period, a fault period does not exist, stability and maintainability of the client are improved, and user experience is further improved.
As shown in fig. 5, fig. 5 illustrates another domain name anti-blocking method provided in an embodiment of the present application, including:
501: receiving a domain name access request, and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name profile includes a primary domain name and a plurality of backup domain names.
502: and when the main domain name fails to be accessed, allocating the standby domain name for resource access. In one aspect, the standby domain names are multiple, when the main domain name fails to be accessed, the first standby domain name is allocated for resource access, and when the first standby domain name fails to be accessed, other standby domain names are sequentially allocated according to a preset sequence for resource access until any one standby domain name is successfully accessed.
503: and acquiring the access failure times of the main domain name and the access success times of the standby domain name within a preset time interval.
504: and determining whether to modify the currently and actually used domain name configuration file or not according to the access failure times of the main domain name access and the access success times of the standby domain name. Preferably, when the number of times of access failure of the main domain name reaches a first threshold value and the number of times of access success of one of the standby domain names reaches a second threshold value, the domain name configuration file which is actually used at present is modified. One of the possible embodiments for modifying the domain name configuration file is as follows: and replacing the main domain name in the currently and actually used domain name configuration file with the standby domain name with the access success frequency reaching a second threshold value.
505: receiving a domain name configuration file currently sent by a server, and defining the domain name configuration file currently sent by the server as a current domain name configuration file.
The domain name configuration file currently sent by the server side in step 505 is formed in the following manner:
5051: the server side monitors whether a main domain name or a standby domain name in a currently and actually used domain name configuration file is forbidden; 5052: when the fact that the main domain name and/or the standby domain name in the currently and actually used domain name configuration file are/is blocked is monitored, the plurality of non-blocked domain names are reconfigured to form the domain name configuration file.
506: and comparing whether the domain name configuration file sent last time by the server is consistent with the current domain name configuration file, if so, continuing to use the currently and actually used domain name configuration file, and otherwise, replacing the currently and actually used domain name configuration file with the current domain name configuration file.
Fig. 6 shows a domain name anti-blocking device provided in an embodiment of the present application, which includes an access request receiving module 601, an alternate domain name accessing module 602, an access success/failure statistics module 603, and a profile modification module 604. The access request receiving module 601 is configured to receive a domain name access request, and allocate a main domain name in a currently and actually used domain name configuration file to perform resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a standby domain name. The standby domain name access module 602 is configured to allocate a standby domain name for resource access when the primary domain name access fails. The access success/failure statistics module 603 is configured to obtain access failure times of the main domain name and access success times of the standby domain name in a preset time interval. The configuration file modification module 604 is configured to determine whether to modify the currently and actually used domain name configuration file according to the access failure times of the main domain name access and the access success times of the standby domain name.
As a preferred embodiment, the domain name configuration file includes a main domain name and a plurality of standby domain names, each standby domain name and a first-level domain name of the main domain name are different, and the standby domain names are arranged according to a preset order; in the standby domain name access module 602, when the primary domain name access fails, allocating a standby domain name for resource access includes: when the main domain name access fails, allocating a first standby domain name for resource access, and when the first standby domain name access fails, sequentially allocating other standby domain names according to a preset sequence for resource access until any one standby domain name is successfully accessed.
In the configuration file modification module 604, determining whether to modify the currently and actually used domain name configuration file according to the access failure times of the main domain name access and the access success times of the standby domain name, includes: and when the access failure times of the main domain name reach a first threshold value and the access success times of one standby domain name reach a second threshold value, modifying the currently and actually used domain name configuration file.
Wherein, modifying the domain name configuration file actually used at present comprises: and replacing the main domain name in the currently and actually used domain name configuration file with the standby domain name with the access success frequency reaching a second threshold value.
Fig. 7 shows another domain name anti-blocking device provided in this embodiment of the present application, which includes an access request receiving module 701, a standby domain name accessing module 702, an access success/failure statistics module 703, a profile modification module 704, a profile receiving module 705, and a profile comparison module 706. The access request receiving module 701 is configured to receive a domain name access request, and allocate a main domain name in a currently and actually used domain name configuration file to perform resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a standby domain name. The standby domain name access module 702 is configured to allocate a standby domain name for resource access when the primary domain name access fails. The access success/failure statistics module 703 is configured to obtain the access failure times of the main domain name and the access success times of the standby domain name in a preset time interval. The configuration file modification module 704 is configured to determine whether to modify the currently and actually used domain name configuration file according to the access failure times of the main domain name access and the access success times of the standby domain name. The configuration file receiving module 705 is configured to receive a domain name configuration file currently sent by a server, and define the domain name configuration file currently sent by the server as a current domain name configuration file. The configuration file comparison module 706 is configured to compare whether the domain name configuration file last sent by the server is consistent with the current domain name configuration file, if so, continue to use the currently and actually used domain name configuration file, otherwise, replace the currently and actually used domain name configuration file with the current domain name configuration file.
In the configuration file receiving module 705, receiving a domain name configuration file currently sent by a server, including: sending a domain name configuration file request to a server side every other preset time length; and receiving the domain name configuration file fed back by the server end in response to the domain name configuration file request.
In another embodiment, the forming method of the domain name configuration file currently sent by the server includes: the server side monitors whether a main domain name or a standby domain name in a currently and actually used domain name configuration file is forbidden; when the fact that the main domain name and/or the standby domain name in the currently and actually used domain name configuration file are/is blocked is monitored, the plurality of non-blocked domain names are reconfigured to form the domain name configuration file.
As shown in fig. 8, an embodiment of the present application further provides a computer device, including: a memory 801 and one or more processors 802; the memory 801 for storing one or more programs; when executed by the one or more processors 802, cause the one or more processors to implement a domain name anti-block method as described herein.
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are used to perform the domain name anti-blocking method provided in the above embodiments.
Of course, the storage medium provided in the embodiments of the present application contains computer-executable instructions, and the computer-executable instructions are not limited to the domain name anti-blocking method described above, and may also perform related operations in the domain name anti-blocking method provided in any embodiment of the present application.
The foregoing is considered as illustrative of the preferred embodiments of the invention and the technical principles employed. The present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the claims.
Claims (10)
1. A domain name anti-blocking method is characterized by comprising the following steps:
receiving a domain name access request, and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a plurality of standby domain names;
when the main domain name fails to be accessed, allocating a standby domain name for resource access;
acquiring the access failure times of the main domain name and the access success times of each standby domain name within a preset time interval;
and determining whether to modify the currently and actually used domain name configuration file or not according to the access failure times of the main domain name access and the access success times of the standby domain name.
2. The domain name anti-block method according to claim 1, wherein each of the standby domain names and the secondary domain name of the main domain name are different, and a plurality of the standby domain names are arranged in a preset order;
when the main domain name fails to be accessed, allocating a standby domain name for resource access, comprising the following steps:
when the main domain name access fails, allocating a first standby domain name for resource access, and when the first standby domain name access fails, sequentially allocating other standby domain names according to a preset sequence for resource access until any one standby domain name is successfully accessed.
3. The method for preventing and forbidding domain names according to claim 2, wherein determining whether to modify the domain name configuration file actually used currently according to the access failure times of the main domain name access and the access success times of each standby domain name comprises:
and when the access failure times of the main domain name reach a first threshold value and the access success times of one standby domain name reach a second threshold value, modifying the currently and actually used domain name configuration file.
4. The domain name anti-block method of claim 3, wherein modifying the domain name profile currently in actual use comprises:
and replacing the main domain name in the currently and actually used domain name configuration file with the standby domain name with the access success frequency reaching a second threshold value.
5. The domain name anti-blocking method according to claim 1 or 3, characterized in that the domain name anti-blocking method further comprises:
receiving a domain name configuration file currently sent by a server, and defining the domain name configuration file currently sent by the server as a current domain name configuration file;
and comparing whether the domain name configuration file sent last time by the server is consistent with the current domain name configuration file, if so, continuing to use the currently and actually used domain name configuration file, and otherwise, replacing the currently and actually used domain name configuration file with the current domain name configuration file.
6. The method of claim 5, wherein receiving the domain name configuration file currently sent by the server comprises:
sending a domain name configuration file request to a server side every other preset time length;
and receiving the domain name configuration file fed back by the server end in response to the domain name configuration file request.
7. The domain name anti-blocking method according to claim 5, wherein the domain name configuration file currently sent by the server is formed by:
the server side monitors whether a main domain name or a standby domain name in a currently and actually used domain name configuration file is forbidden;
when the fact that the main domain name and/or the standby domain name in the currently and actually used domain name configuration file are/is blocked is monitored, the plurality of non-blocked domain names are reconfigured to form the domain name configuration file.
8. A domain name anti-block device, comprising:
an access request receiving module: the domain name access system is used for receiving a domain name access request and allocating a main domain name in a currently and actually used domain name configuration file for resource access based on the domain name access request; the domain name configuration file comprises a main domain name and a plurality of standby domain names;
the standby domain name access module: the method comprises the steps of allocating a standby domain name for resource access when the main domain name fails to be accessed;
visit success or failure statistics module: the method comprises the steps of obtaining access failure times of a main domain name and access success times of each standby domain name within a preset time interval;
a configuration file modification module: and the system is used for determining whether to modify the currently and actually used domain name configuration file according to the access failure times of the main domain name access and the access success times of the standby domain name.
9. A computer device, comprising: a memory and one or more processors;
the memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the domain name anti-blocking method of any of claims 1-7.
10. A storage medium containing computer-executable instructions for performing the domain name anti-blocking method of any one of claims 1-7 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110461468.0A CN113301177A (en) | 2021-04-27 | 2021-04-27 | Domain name anti-blocking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110461468.0A CN113301177A (en) | 2021-04-27 | 2021-04-27 | Domain name anti-blocking method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113301177A true CN113301177A (en) | 2021-08-24 |
Family
ID=77320375
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110461468.0A Pending CN113301177A (en) | 2021-04-27 | 2021-04-27 | Domain name anti-blocking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113301177A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114205220A (en) * | 2021-12-10 | 2022-03-18 | 北京荣达天下信息科技有限公司 | Client exception counting-based multi-machine room fault transfer method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104092787A (en) * | 2014-06-24 | 2014-10-08 | 腾讯科技（深圳）有限公司 | Network access method and system based on DNS |
| CN109769040A (en) * | 2018-12-14 | 2019-05-17 | 平安普惠企业管理有限公司 | Content delivery network service switching method, device, equipment and storage medium |
| CN110519409A (en) * | 2019-08-28 | 2019-11-29 | 北京思维造物信息科技股份有限公司 | Domain name Dynamic Configuration, device, equipment and storage medium |
| CN112134968A (en) * | 2020-09-29 | 2020-12-25 | 平安普惠企业管理有限公司 | Domain name access method and device, electronic equipment and storage medium |
-
2021
- 2021-04-27 CN CN202110461468.0A patent/CN113301177A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104092787A (en) * | 2014-06-24 | 2014-10-08 | 腾讯科技（深圳）有限公司 | Network access method and system based on DNS |
| CN109769040A (en) * | 2018-12-14 | 2019-05-17 | 平安普惠企业管理有限公司 | Content delivery network service switching method, device, equipment and storage medium |
| CN110519409A (en) * | 2019-08-28 | 2019-11-29 | 北京思维造物信息科技股份有限公司 | Domain name Dynamic Configuration, device, equipment and storage medium |
| CN112134968A (en) * | 2020-09-29 | 2020-12-25 | 平安普惠企业管理有限公司 | Domain name access method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114205220A (en) * | 2021-12-10 | 2022-03-18 | 北京荣达天下信息科技有限公司 | Client exception counting-based multi-machine room fault transfer method and system |
| CN114205220B (en) * | 2021-12-10 | 2024-04-05 | 北京百融睿博科技有限公司 | Multi-machine room fault transfer method and system based on abnormal counting of clients |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11586673B2 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| US10013662B2 (en) | Virtual resource cost tracking with dedicated implementation resources | |
| CN106487486B (en) | Service processing method and data center system | |
| US8447757B1 (en) | Latency reduction techniques for partitioned processing | |
| US20180027061A1 (en) | Method and apparatus for elastically scaling virtual machine cluster | |
| US10652080B2 (en) | Systems and methods for providing a notification system architecture | |
| CN109783151B (en) | Method and device for rule change | |
| CN111209110B (en) | Task scheduling management method, system and storage medium for realizing load balancing | |
| CN104158707A (en) | Method and device of detecting and processing brain split in cluster | |
| US20180074887A1 (en) | Using Predictive Analytics of Natural Disaster to Cost and Proactively Invoke High-Availability Preparedness Functions in a Computing Environment | |
| CN109324942B (en) | Double-activity processing method, device, system, equipment and storage medium for microservice | |
| CN111865632A (en) | Switching method of distributed data storage cluster and switching instruction sending method and device | |
| CN104793982A (en) | Method and device for establishing virtual machine | |
| CN102903043A (en) | Payment server and payment channel acquisition method | |
| EP3457668B1 (en) | Clustering in unified communication and collaboration services | |
| CN107508700B (en) | Disaster recovery method, device, equipment and storage medium | |
| US10447622B2 (en) | Identifying trending issues in organizational messaging | |
| US8156374B1 (en) | Problem management for outsized queues | |
| CN113301177A (en) | Domain name anti-blocking method and device | |
| CN108111630B (en) | Zookeeper cluster system and connection method and system thereof | |
| CN112631756A (en) | Distributed regulation and control method and device applied to space flight measurement and control software | |
| CN111866210A (en) | Virtual IP balance distribution method, system, terminal and storage medium | |
| CN116954863A (en) | Database scheduling method, device, equipment and storage medium | |
| US20220405311A1 (en) | Systems and methods for using data applications and data filters to improve customer communications | |
| CN105338058A (en) | Application updating method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210824 |
|
| RJ01 | Rejection of invention patent application after publication |