CN112543238A - Domain name over-white list optimization method, device, equipment and medium - Google Patents
Domain name over-white list optimization method, device, equipment and medium Download PDFInfo
- Publication number
- CN112543238A CN112543238A CN202011444378.2A CN202011444378A CN112543238A CN 112543238 A CN112543238 A CN 112543238A CN 202011444378 A CN202011444378 A CN 202011444378A CN 112543238 A CN112543238 A CN 112543238A
- Authority
- CN
- China
- Prior art keywords
- domain name
- name data
- matching
- execution result
- legal
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000005457 optimization Methods 0.000 title claims abstract description 22
- 230000015654 memory Effects 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012544 monitoring process Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 238000012552 review Methods 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000003068 static effect Effects 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/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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
- H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL
Abstract
The invention discloses a domain name over-white list optimization method, a domain name over-white list optimization device, electronic equipment and a computer storage medium, relates to the technical field of network security, and aims to solve the problem that a legal white list user is deleted by mistake. The method comprises the following steps: according to a first preset period, periodically requesting to record domain name data for domain name matching so as to obtain legal domain name data; if the legal domain name data is obtained, recording an execution result of successful matching, and taking the legal domain name data as the latest domain name data which is over-white, otherwise, recording an execution result of failed matching; according to a second preset period, regularly inquiring the recorded execution result; and if the execution result of the matching failure is inquired, re-requesting the recorded domain name data for domain name matching until the legal domain name data is obtained, and taking the legal domain name data as the latest whitewashed domain name data.
Description
Technical Field
The invention relates to the technical field of network security, in particular to a domain name over white list optimization method, a device, equipment and a medium.
Background
The existing domain name over-white (over-white list) system comprises a checking module and an over-white module. The whitewashing module comprises a newly added domain name data unit and a whitewashed domain name data unit, the checking module is used for requesting all domain name data in the whitewashing module to be matched with the domain name filing system, synchronizing the domain name data meeting the requirement (namely screening out the domain name data which is already filed in the domain name filing system) to the whitewashing module, updating the whitewashed domain name data unit in the whitewashing module, and emptying the newly added domain name data unit.
Based on the domain name whitewashing system, the currently adopted business operation logic is as follows: after the checking module finishes matching with the official domain name filing system every time, the whitewashing module deletes the domain name data which is not filed, and only updates the domain name data which meets the requirement. The main reasons for updating the domain name data meeting the requirements regularly include two aspects, on one hand, the domain name data which is already whited possibly does not meet the whiter requirements due to the expiration of the filing period, and further recheck is needed; on the other hand, newly-added domain name data is imported in each period. Therefore, the checking module needs to check all domain name data in the whitepassing module periodically according to a set period, and is generally set to check with the official domain name registration system once every day.
However, the verification request initiated by the verification module may be unsuccessful, which is mainly caused by the following reasons: (1) network connection errors result in request failures; (2) when the system fails and cannot normally send or receive domain update data, the request initiated by the checking module easily causes data errors; (3) when the checking module requests to match the domain name with the official filing system, if the domain name filing system is being updated, accurate filing data cannot be acquired.
Therefore, the existing domain name over-whitening method has the following problems: when the checking module initiates a checking request but cannot normally acquire the recorded data, after the checking module requests judgment, all domain name data in the over-blank module cannot meet the requirements due to the absence of the recorded domain name data, so that all domain names in the over-blank domain name data unit are deleted. The over-white module is mainly used for linking up 'white list' users in a service system so as to facilitate operations such as over-home, transaction, website analysis and the like, and when all 'white list' users are deleted, normal service development can be seriously influenced.
Aiming at the problem that legal white list users are deleted by mistake, an effective solution is not provided at present.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a medium for optimizing a domain name over white list, which are used for at least solving the problem that a legal white list user is deleted by mistake.
In a first aspect, an embodiment of the present invention provides a method for optimizing a domain name over-white list, including the following steps:
according to a first preset period, periodically requesting to record domain name data for domain name matching so as to obtain legal domain name data;
if the legal domain name data is obtained, recording an execution result of successful matching, and taking the legal domain name data as the latest domain name data which is over-white, otherwise, recording an execution result of failed matching;
according to a second preset period, regularly inquiring the recorded execution result;
and if the execution result of the matching failure is inquired, re-requesting the recorded domain name data for domain name matching, and taking the legal domain name data as the latest whiteout domain name data after the legal domain name data is obtained.
In some embodiments, the requesting record domain name data for domain name matching includes:
requesting domain name filing domain name data from a domain name filing system;
and performing domain name matching on the recorded domain name data, the historical already-blank domain name data and the newly-added domain name data, and acquiring the domain name data passing the matching as legal domain name data.
In some embodiments, when the legal domain name data is the latest whitewashed domain name data, the method further includes:
and deleting the newly added domain name data.
In some embodiments, the re-requesting the docket domain name data for domain name matching includes:
if the legal domain name data is not acquired, recording the execution result of the matching failure again;
and according to the second preset period, when the recorded execution result is inquired regularly, if the execution result of matching failure is inquired again, the filed domain name data is requested again to carry out domain name matching until the legal domain name data is obtained.
In some embodiments, the re-requesting the recorded domain name data for domain name matching, and after obtaining the legal domain name data, further includes:
and updating the execution result of the matching failure through the execution result of the matching success.
In some embodiments, if an execution result that the matching is successful is found, the recorded execution result is periodically monitored according to the second preset period, and the request for the recorded domain name data is not performed.
In some embodiments, the first predetermined period is greater than the second predetermined period.
In a second aspect, an embodiment of the present invention provides a domain name over white list optimization apparatus, including:
the system comprises a whiteout module, a white filter module and a white filter module, wherein the whiteout module is used for updating and storing latest domain name whiteout data and comprises a newly increased domain name data unit and a whiteout domain name data unit, the newly increased domain name data unit stores newly increased domain name data, and the whiteout domain name data unit stores whiteout domain name data;
the checking module is used for regularly requesting the recorded domain name data to be matched with all the domain name data in the blank module according to a first preset period, if the recorded domain name data is matched with all the domain name data in the blank module to obtain legal domain name data, feeding back an execution result of successful matching to the message module, and synchronizing the legal domain name data to the blank module to update the blank domain name data unit; otherwise, feeding back the execution result of the matching failure to the message module;
the message module is used for receiving and recording the execution result;
the rechecking module is used for periodically accessing the message module according to a second preset period, re-requesting the recorded domain name data to perform domain name matching if an execution result of matching failure is inquired, synchronizing the legal domain name data to the blank module after the legal domain name data is obtained so as to update the blank domain name data unit, and meanwhile updating the execution result of successful matching to the message module; and if the execution result of successful matching is inquired, periodically monitoring the message module according to the second preset period.
In a third aspect, an embodiment of the present invention provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor, when executing the computer program, implements the domain name whitelist optimization method according to the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the domain name over-white list optimization method according to the first aspect.
Compared with the prior art, embodiments of the present invention provide a method, an apparatus, a device, and a medium for optimizing a domain name over white list, where by regularly querying a domain name matching condition, and for an execution result that legal domain name data is not obtained, a request is made again to execute domain name matching with recorded domain name data until the legal domain name data is obtained, and it can effectively avoid that the over white domain name data is completely deleted due to abnormal recorded matching, so that a problem that a legal white list user is mistakenly deleted is solved, and normal development of subsequent services can be ensured.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below to provide a more thorough understanding of the invention.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow chart of a domain name over white list optimization method of the present invention;
fig. 2 is a block diagram of a domain name over white list optimizing apparatus according to an embodiment of the present invention;
fig. 3 is a block diagram of the electronic device according to the embodiment of the present invention.
Detailed Description
In order to make the purpose and technical solution of the present invention more apparent, the present invention will be described and illustrated with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments provided by the present invention, belong to the protection scope of the present application.
It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.
The domain name over white list means: by matching the domain name data with the data in the official domain name filing system, the filed domain name data in the domain name data is screened out, and legal domain name data (the filed domain name data) is obtained, so that the safety of white list users (legal domain names) is improved, and the safety of a service system is further improved.
Example 1
Based on the above principle, this embodiment provides a method for optimizing a domain name over white list, fig. 1 is a flowchart of the method for optimizing a domain name over white list according to the present invention, and as shown in fig. 1, the method for optimizing a domain name over white list includes the following steps:
s101, according to a first preset period, periodically requesting to record domain name data for domain name matching so as to obtain legal domain name data.
And the domain name matching between the definition request filing domain name data and the domain name data to be screened is realized by taking a preset first preset period as a time interval for requesting the official domain name filing system, so that the legal domain name data is obtained. The official domain name filing system can be a website filing system of the Ministry of industry and communications, an ICP filing system and the like. The first preset period is once a day, that is, the domain name data is requested to be recorded once a day for domain name matching. After finishing one time of domain name data filing request, the work is suspended, and the process of filing the domain name data is started again until the next period comes.
S102, if the legal domain name data are obtained, recording an execution result of successful matching, and taking the legal domain name data as the latest passing-white domain name data, otherwise, recording an execution result of failed matching.
If the legal domain name data is acquired, the successful request to the recorded domain name data is indicated, the legal domain name data is acquired by performing domain name matching on the domain name data to be screened and the recorded domain name data, the execution result (message) of successful matching is recorded, the legal domain name data is used as the latest domain name data which is over white, and the domain name data which is not matched is deleted.
If the legal domain name data is not obtained, the request for filing the domain name data fails, and the execution result of the matching failure is recorded.
And S103, periodically inquiring the recorded execution result according to a second preset period.
A second preset period is preset as a time interval for periodically inquiring the record, and the second preset period may be 5 to 60 minutes/time, specifically 30 minutes/time in this embodiment. Therefore, the recorded execution results are queried every 30 minutes.
And S104, if the execution result of the matching failure is inquired, re-requesting the recorded domain name data for domain name matching, and taking the legal domain name data as the latest whiteout domain name data after the legal domain name data is obtained.
If the execution result of the matching failure is inquired, the process of requesting the filed domain name data is restarted, and the filed domain name data requested is matched with the domain name data to be screened so as to obtain legal domain name data, and the legal domain name data is used for updating the white domain name data (as the latest white domain name data), so that the white domain name data is always legal domain name data, the legality and the safety of the white list user corresponding to the white domain name data are ensured, and the white list user can safely and quickly perform business operations such as user passing, transaction, station analysis and the like.
By means of the domain name over-white list optimization method, the execution result of domain name matching is inquired regularly, and the domain name data can be requested again to be matched according to the condition that the domain name matching fails, so that the legal domain name data can be obtained, the problem that the legal domain name users are deleted by mistake due to the fact that all the domain name data to be screened do not meet requirements (all the domain name data are judged to be unreported data) and the problem that the white list users corresponding to the domain name data to be screened are deleted completely are avoided, and the normal development of subsequent services is guaranteed.
Preferably, the above request to record domain name data for domain name matching includes:
requesting domain name filing domain name data from a domain name filing system;
and performing domain name matching on the recorded domain name data, the historical whited domain name data and the newly added domain name data, and acquiring the domain name data passing the matching as legal domain name data.
The domain name filing system is an official domain name filing system, and by requesting filed domain name data from the official domain name filing system, the filed domain name data is subjected to domain name matching with historical already-blank domain name data and newly-added domain name data to obtain the newly-added domain name data and the filed domain name data in the historical already-blank domain name data, and the matched domain name data is obtained and serves as legal domain name data.
The newly added domain name data is the domain name data which is imported each time, and the legality and the safety of the newly added domain name data need to be determined by filing and querying. The historical domain name data which has passed the white domain name and has been recorded and inquired before is recorded and inquired again to check that the valid period of the recorded domain name is not due, so that the latest domain name data which has passed the white domain name is always recorded and legal domain name data can be successfully subjected to subsequent business operation.
Preferably, when the legal domain name data is the latest domain name data that has already been whited, the method further includes:
and deleting the newly added domain name data.
After the newly added domain name data is subjected to record inquiry, the domain name matched with the recorded domain name data is used as legal domain name data and added into the latest whiteout domain name data, and the newly added domain name which is not matched and passes is illegal domain name data.
Preferably, if the successfully matched execution result is found, the recorded execution result is monitored regularly according to a second preset period, and the request for the filed domain name data is not made.
After the successfully matched execution result is inquired, the recorded execution result still needs to be inquired periodically according to a second preset period in the follow-up process so as to play a role of monitoring the execution result, but the request for the filed domain name data and the matching judgment of the domain name do not need to be executed again.
Preferably, the first preset period is greater than the second preset period. If the first preset period is once a day, and the second preset period is 30 minutes/time, the evaluation rate of requesting the recorded domain name data according to the first preset period is ensured to be less than the frequency of the execution result of the query record, so that when the request of recording the domain name data according to the first preset period fails, the request and the matching of the recorded domain name data can be repeatedly executed for many times through the execution result of the query record for many times until the legal domain name data is obtained, and the legal white list user is ensured not to be mistakenly deleted due to one-time request abnormity or abnormal matching.
Preferably, the method further comprises, after requesting the recorded domain name data for domain name matching again and obtaining the legal domain name data, the steps of:
and updating the execution result of the matching failure through the execution result of the matching success.
It should be noted that, in the execution process, the latest execution result is always recorded, so when the filed domain name data is requested again for domain name matching, if the legal domain name data is successfully acquired, the execution result that the matching is successful needs to be recorded, and the last execution result (the execution result that the matching fails) is updated according to the execution result that the matching is successful, so that when the latest execution result that the matching is successful is queried according to the second preset period, the request and the matching of the filed domain name data are not executed again.
Example 2
The difference between this embodiment and the above embodiment is that, when the execution result of the matching failure is found according to the second preset period, and the domain name matching is performed by re-requesting the filed domain name data, the method further includes:
if the legal domain name data are not obtained yet, recording the execution result of the matching failure again;
and according to the second preset period, when the recorded execution result is inquired regularly, if the execution result of matching failure is inquired again, the filed domain name data is requested again to carry out domain name matching until the legal domain name data is obtained.
If the legal domain name data is not successfully acquired when the filed domain name data is requested again for domain name matching, the execution result of matching failure needs to be recorded continuously, when the next query period comes, the recorded execution result is queried continuously, the request of the filed domain name data and the domain name matching are requested again according to the query result of matching failure, the query operation is executed repeatedly according to a second preset period, the request and the matching of the filed domain name data are executed again for many times until the legal domain name data are acquired, and therefore the white list user with the legal domain name is guaranteed not to be deleted mistakenly due to the abnormal request of the filed domain name data.
Preferably, the method of requesting the recorded domain name data again for domain name matching until obtaining the legal domain name data further includes:
updating the execution result of the matching failure through the execution result of the matching success;
taking legal domain name data as latest domain name data which is already white;
and deleting the newly added domain name data.
The white-list user corresponding to the latest white-list data is guaranteed to have validity and safety by updating the white-list data through the legal domain data, so that the white-list user can safely and quickly perform service operation.
Example 3
The present embodiment provides a domain name over white list optimization apparatus, which is used to implement the foregoing embodiments and preferred embodiment modes, and has been described without further description, and the following terms "module", "unit", "subunit", and the like may be a combination of software and/or hardware that can implement a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware or a combination of software and hardware is also possible and contemplated.
Fig. 2 is a block diagram of a domain name over white list optimizing apparatus according to an embodiment of the present invention, and as shown in fig. 2, the apparatus includes:
the whiteout module 21 is configured to update and store the latest domain name whiteout data, which includes a newly added domain name data unit and a whiteout domain name data unit, where the newly added domain name data unit stores newly added domain name data, and the whiteout domain name data unit stores whiteout domain name data;
the checking module 22 is configured to periodically request the recorded domain name data to be matched with all domain name data in the whiteout module according to a first preset period, and if legal domain name data are obtained through matching, the checking module feeds back an execution result of successful matching to the message module and synchronizes the legal domain name data to the whiteout module so as to update a whiteout domain name data unit; otherwise, feeding back the execution result of the matching failure to the message module;
a message module 23, configured to receive and record an execution result;
the review module 24 is configured to periodically access the message module according to a second preset period, and if an execution result of failed matching is found, request the recorded domain name data to perform domain name matching again, synchronize the legal domain name data to the whitepassing module after the legal domain name data is obtained, so as to update the whitepassing domain name data unit, and update the execution result of successful matching to the message module; and if the execution result of successful matching is inquired, periodically monitoring the message module according to a second preset period.
It should be noted that the review module 24 only starts the same process as the review module 22, namely, the request for filing domain name data and the matching process, when the result of executing the matching failure recorded in the access message module 23 is failed, and the operating frequency of the review module 24 is higher than the operating frequency of the review module 23, namely, the second preset period is less than the first preset period, for example, the first preset period is once a day, and the second preset period is 30 minutes/time. Therefore, before the next checking period comes, the message module can be accessed for many times through the rechecking module 24, and the multiple filing data requests and matching processes are executed until the legal domain name data is successfully acquired, so that the legal white list user is prevented from being deleted by mistake due to the failure of domain name matching of the checking module 22, the problem that the white list user is completely deleted due to the failure of the filing domain name data request is solved, and the normal development of subsequent services is ensured.
The above modules may be functional modules or program modules, and may be implemented by software or hardware. For a module implemented by hardware, the modules may be located in the same processor; or the modules can be respectively positioned in different processors in any combination.
Example 4
Fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 3, an electronic device is provided, where the electronic device may be a server, and its internal structural diagram may be as shown in fig. 3. The electronic device comprises a processor, a memory, an input device and an output device; wherein the number of processors in the electronic device may be one or more, and one processor is taken as an example in fig. 3; the processor, memory, input devices and output devices in the electronic apparatus may be connected by a bus or other means, and fig. 3 illustrates the connection by a bus as an example.
The memory, which is a computer-readable storage medium, may include a high-speed random access memory, a non-volatile memory, and the like, and may be used to store an operating system, a software program, a computer-executable program, and a database, such as program instructions/modules corresponding to the domain name over white list optimization method in embodiment 1 of the present invention, and may further include a memory, which may be used to provide an operating environment for the operating system and the computer program. In some examples, the memory may further include memory located remotely from the processor, and these remote memories may be connected to the electronic device through a network.
The processor, which is used to provide computing and control capabilities, may include a Central Processing Unit (CPU), or A Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of embodiments of the present Application. The processor executes various functional applications and data processing of the electronic device by running computer-executable programs, software programs, instructions, and modules stored in the memory, that is, implements the domain name whitelist optimization method of embodiment 1.
The output device of the electronic equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
The electronic device may further include a network interface/communication interface, the network interface of the electronic device being for communicating with an external terminal through a network connection. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Those skilled in the art will appreciate that the architecture shown in fig. 3 is a block diagram of only a portion of the architecture associated with the subject application, and does not constitute a limitation on the electronic devices to which the subject application is applied, as a particular electronic device may include more or less components than those shown, or combine certain components, or have a different arrangement of components.
It will be understood by those skilled in the art that all or part of the processes in the domain name over white list optimization method according to embodiment 1 may be implemented by a computer program, which may be stored in a non-volatile computer-readable storage medium, and may include the processes of the embodiments of the methods described above when the computer program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
Example 5
An embodiment of the present invention provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to implement a domain name whitelist optimization method, the method including:
according to a first preset period, periodically requesting to record domain name data for domain name matching so as to obtain legal domain name data;
if the legal domain name data is obtained, recording an execution result of successful matching, and taking the legal domain name data as the latest domain name data which is over-white, otherwise, recording an execution result of failed matching;
according to a second preset period, regularly inquiring the recorded execution result;
and if the execution result of the matching failure is inquired, re-requesting the recorded domain name data for domain name matching, and taking the legal domain name data as the latest whiteout domain name data after the legal domain name data is obtained.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the operations of the domain name over white list optimization method in the above-mentioned embodiments, and may also perform related operations in the domain name over white list optimization method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk, or an optical disk of a computer, and includes several instructions to enable an electronic device (which may be a mobile phone, a personal computer, a server, or a network device) to execute the domain name over white list optimization method according to the embodiments of the present invention.
It should be noted that, in the embodiment of the domain name over white list optimization method, each included unit and module are only divided according to functional logic, but are not limited to the above division, as long as corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.
Various other modifications and changes may be made by those skilled in the art based on the above-described technical solutions and concepts, and all such modifications and changes should fall within the scope of the claims of the present invention.
Claims (10)
1. A domain name over white list optimization method is characterized by comprising the following steps:
according to a first preset period, periodically requesting to record domain name data for domain name matching so as to obtain legal domain name data;
if the legal domain name data is obtained, recording an execution result of successful matching, and taking the legal domain name data as the latest domain name data which is over-white, otherwise, recording an execution result of failed matching;
according to a second preset period, regularly inquiring the recorded execution result;
and if the execution result of the matching failure is inquired, re-requesting the recorded domain name data for domain name matching, and taking the legal domain name data as the latest whiteout domain name data after the legal domain name data is obtained.
2. The method of claim 1, wherein requesting domain name registration data for domain name matching comprises:
requesting domain name filing domain name data from a domain name filing system;
and performing domain name matching on the recorded domain name data, the historical already-blank domain name data and the newly-added domain name data, and acquiring the domain name data passing the matching as legal domain name data.
3. The method of optimizing a domain name whitelist of claim 2, wherein the step of using the valid domain name data as the latest whitelisted domain name data further comprises:
and deleting the newly added domain name data.
4. The method of claim 1, wherein the re-requesting filed domain name data for domain name matching comprises:
if the legal domain name data is not acquired, recording the execution result of the matching failure again;
and according to the second preset period, when the recorded execution result is inquired regularly, if the execution result of matching failure is inquired again, the filed domain name data is requested again to carry out domain name matching until the legal domain name data is obtained.
5. The method for optimizing a domain name over white list according to claim 1 or 4, wherein the re-requesting filed domain name data for domain name matching, and after obtaining the legal domain name data, further comprising:
and updating the execution result of the matching failure through the execution result of the matching success.
6. The method according to claim 1, wherein if the result of successful matching is found, the recorded result is monitored periodically according to the second predetermined period without requesting the recorded domain name data.
7. The method of optimizing domain name over white list of claim 1, wherein the first predetermined period is greater than the second predetermined period.
8. An apparatus for optimizing a domain name over white list, comprising:
the system comprises a whiteout module, a white filter module and a white filter module, wherein the whiteout module is used for updating and storing latest domain name whiteout data and comprises a newly increased domain name data unit and a whiteout domain name data unit, the newly increased domain name data unit stores newly increased domain name data, and the whiteout domain name data unit stores whiteout domain name data;
the checking module is used for regularly requesting the recorded domain name data to be matched with all the domain name data in the blank module according to a first preset period, if the recorded domain name data is matched with all the domain name data in the blank module to obtain legal domain name data, feeding back an execution result of successful matching to the message module, and synchronizing the legal domain name data to the blank module to update the blank domain name data unit; otherwise, feeding back the execution result of the matching failure to the message module;
the message module is used for receiving and recording the execution result;
the rechecking module is used for periodically accessing the message module according to a second preset period, re-requesting the recorded domain name data to perform domain name matching if an execution result of matching failure is inquired, synchronizing the legal domain name data to the blank module after the legal domain name data is obtained so as to update the blank domain name data unit, and meanwhile updating the execution result of successful matching to the message module; and if the execution result of successful matching is inquired, periodically monitoring the message module according to the second preset period.
9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the computer program, implements the domain name whitelist optimization method of any one of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method for domain name over-white list optimization according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011444378.2A CN112543238B (en) | 2020-12-08 | 2020-12-08 | Domain name over-white list optimization method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011444378.2A CN112543238B (en) | 2020-12-08 | 2020-12-08 | Domain name over-white list optimization method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112543238A true CN112543238A (en) | 2021-03-23 |
| CN112543238B CN112543238B (en) | 2022-06-14 |
Family
ID=75018324
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011444378.2A Expired - Fee Related CN112543238B (en) | 2020-12-08 | 2020-12-08 | Domain name over-white list optimization method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112543238B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116886449A (en) * | 2023-09-07 | 2023-10-13 | 杭州优云科技有限公司 | Method for intelligently identifying and intercepting domain name |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571855A (en) * | 2010-12-17 | 2012-07-11 | 北大方正集团有限公司 | System and method for investigating illegal network information |
| CN104125209A (en) * | 2014-01-03 | 2014-10-29 | 腾讯科技（深圳）有限公司 | Malicious website prompt method and router |
| US20170195286A1 (en) * | 2015-12-30 | 2017-07-06 | Donuts Inc. | Whitelist domain name registry |
| CN107645503A (en) * | 2017-09-20 | 2018-01-30 | 杭州安恒信息技术有限公司 | A kind of detection method of the affiliated DGA families of rule-based malice domain name |
| CN109922030A (en) * | 2017-12-13 | 2019-06-21 | 南京领创信息科技有限公司 | Global network access control system and method based on Android device |
| CN109951469A (en) * | 2019-03-12 | 2019-06-28 | 中国平安人寿保险股份有限公司 | A kind of method, apparatus, storage medium and server creating domain name black and white lists |
-
2020
- 2020-12-08 CN CN202011444378.2A patent/CN112543238B/en not_active Expired - Fee Related
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571855A (en) * | 2010-12-17 | 2012-07-11 | 北大方正集团有限公司 | System and method for investigating illegal network information |
| CN104125209A (en) * | 2014-01-03 | 2014-10-29 | 腾讯科技（深圳）有限公司 | Malicious website prompt method and router |
| US20170195286A1 (en) * | 2015-12-30 | 2017-07-06 | Donuts Inc. | Whitelist domain name registry |
| CN107645503A (en) * | 2017-09-20 | 2018-01-30 | 杭州安恒信息技术有限公司 | A kind of detection method of the affiliated DGA families of rule-based malice domain name |
| CN109922030A (en) * | 2017-12-13 | 2019-06-21 | 南京领创信息科技有限公司 | Global network access control system and method based on Android device |
| CN109951469A (en) * | 2019-03-12 | 2019-06-28 | 中国平安人寿保险股份有限公司 | A kind of method, apparatus, storage medium and server creating domain name black and white lists |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116886449A (en) * | 2023-09-07 | 2023-10-13 | 杭州优云科技有限公司 | Method for intelligently identifying and intercepting domain name |
| CN116886449B (en) * | 2023-09-07 | 2023-12-05 | 杭州优云科技有限公司 | Method for intelligently identifying and intercepting domain name |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112543238B (en) | 2022-06-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2019246872B2 (en) | Tiered connection pooling methods, systems and computer readable storage media | |
| CN109862043B (en) | Terminal authentication method and device | |
| WO2020050943A4 (en) | Methods for requesting and authenticating photographic image data | |
| CN109766349B (en) | Task duplicate prevention method, device, computer equipment and storage medium | |
| CN105516055B (en) | Data access method, access device, target device and management server | |
| CN106961332B (en) | Authority authentication method and device | |
| CN111400777B (en) | Network storage system, user authentication method, device and equipment | |
| CN111209349B (en) | Method and device for updating session time | |
| CN113886743B (en) | Method, device and system for refreshing cache resources | |
| CN112543238B (en) | Domain name over-white list optimization method, device, equipment and medium | |
| CN113779545A (en) | Data cross-process sharing method, terminal equipment and computer readable storage medium | |
| CN112287385A (en) | Sensitive word filtering method and device, computer equipment and readable storage medium | |
| CN105592083B (en) | Method and device for terminal to access server by using token | |
| CN110784457A (en) | Service access method and device | |
| CN110163003B (en) | Password management method and device | |
| CN112468540A (en) | Data distribution method, device and medium based on cloud platform | |
| CN112965955A (en) | Data migration method and device, computer equipment and storage medium | |
| CN110944007B (en) | Network access management method, system, device and storage medium | |
| CN110597843A (en) | Waybill query method and device, computer equipment and storage medium | |
| CN114584326B (en) | Block chain data processing method and device, electronic equipment and storage medium | |
| CN111385279A (en) | Service access authority system and method | |
| CN112637085B (en) | Flow recording method and device, computer equipment and storage medium | |
| CN112597118B (en) | Shared file adding method and device | |
| CN112765190A (en) | IP data updating method, device, equipment and medium | |
| CN111552551A (en) | User management method and device based on master-slave system, computer equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20220614 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |