CN116069738A - Root zone file generation method, terminal equipment and computer readable storage medium - Google Patents
Root zone file generation method, terminal equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN116069738A CN116069738A CN202310202815.7A CN202310202815A CN116069738A CN 116069738 A CN116069738 A CN 116069738A CN 202310202815 A CN202310202815 A CN 202310202815A CN 116069738 A CN116069738 A CN 116069738A
- Authority
- CN
- China
- Prior art keywords
- root zone
- data source
- zone file
- file
- data
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a root zone file generation method, terminal equipment and a computer readable storage medium, which relate to the technical field of communication, and the root zone file generation method is applied to a root zone file management system and comprises the following steps: determining a plurality of target data sources needing data acquisition from a plurality of preset data sources; acquiring data of a plurality of target data sources to acquire root zone files contained in the target data sources, and determining head files corresponding to the root zone files; and respectively adding each header file to the corresponding root zone file to generate a root zone file to be combined, and combining each root zone file to be combined according to a preset combining rule to obtain a target root zone file. The invention can construct an autonomous controllable root domain name information release mechanism through the root zone files contained in the plurality of data sources, thereby generating the autonomous controllable root zone files.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a root zone file generating method, a terminal device, and a computer readable storage medium.
Background
DNS (domain name system) is an important component of an internet key infrastructure, is a key for guaranteeing safe and stable operation of the internet, and is mainly kept in operation by using a root zone file issued by an IANA (The Internet Assigned Numbers Authority-internet digital distribution agency), namely, the DNS is operated in a central system-based manner at present;
therefore, some users who master the root domain name resolution system can maliciously delete or tamper the top-level domain information mastered by other users through the root zone file published by the IANA, so that other users who do not master the root domain name resolution system enter a state of 'stopping taking off the network'. Therefore, how to generate the root zone file by the autonomous controllable root domain name information publishing mechanism to avoid the situation that the top-level domain information is maliciously deleted or tampered becomes a technical problem to be solved in industry.
Disclosure of Invention
The invention mainly aims to provide a root zone file generation method, terminal equipment and a computer readable storage medium, aiming at constructing an autonomous controllable root domain name information issuing mechanism through root zone files contained in a plurality of data sources so as to generate the autonomous controllable root zone file.
In order to achieve the above object, the present invention provides a method for generating a root zone file, the method being applied to a root zone file management system, the method for generating a root zone file comprising the steps of:
determining a plurality of target data sources needing data acquisition from a plurality of preset data sources, wherein the plurality of data sources comprise a blockchain data source, a local definition data source, a starting authority data source, a top domain name reporting data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source;
acquiring data of a plurality of target data sources to acquire root zone files contained in the target data sources, and determining head files corresponding to the root zone files;
and respectively adding each header file to the corresponding root zone file to generate a root zone file to be combined, and combining each root zone file to be combined according to a preset combining rule to obtain a target root zone file.
Further, the root zone file management system includes at least one management node, and the step of performing data collection on the plurality of target data sources to obtain root zone files contained in the plurality of target data sources includes:
Acquiring data of the block chain data source to acquire each root zone file contained in the block chain data source;
and/or that the number of the groups of groups,
acquiring data of the local definition data source to acquire respective definition top-level domain data contained in the local definition data source, and determining each custom top-level domain data as each root zone file contained in the local definition data source;
and/or that the number of the groups of groups,
acquiring data of the initial authority data source to acquire each root zone file contained in the initial authority data source;
and/or that the number of the groups of groups,
the data acquisition is carried out on the top-level domain name reporting and preparing data source so as to obtain top-level domain data which is issued by the management node through the top-level domain name reporting and preparing data source, and the top-level domain data is determined to be each root zone file contained in the top-level domain name reporting and preparing data source;
and/or that the number of the groups of groups,
data acquisition is carried out on the top-level domain name exchange data source to obtain the top-level domain data corresponding to each of the plurality of management nodes, and each top-level domain data is determined to be each root zone file contained in the top-level domain name exchange data source;
and/or that the number of the groups of groups,
Acquiring data of the web crawler data source to acquire root crawler data and top domain name crawler data contained in the web crawler data source, integrating the root crawler data and the top domain name crawler data, and determining the integrated data as root zone files contained in the web crawler data source;
and/or that the number of the groups of groups,
and acquiring data of the root zone file exchange data source to acquire complete root zone files corresponding to the management nodes, and determining the complete root zone files as the root zone files contained in the root zone file exchange data source.
Further, the step of performing data collection on the initial authority data source to obtain each root zone file contained in the initial authority data source includes:
acquiring each root zone file, each server address and each signature file contained in the data source of the initial authorization mechanism through a preset hypertext transfer protocol, and respectively verifying each root zone file, each server address and each signature file to obtain each first verification result, wherein the verification results comprise verification success and verification failure;
And when the first verification results are the verification success, storing the root zone files, the server addresses and the signature files to form the root zone files.
Further, the step of performing data collection on the initial authority data source to obtain each root zone file contained in the initial authority data source further includes:
recursion is carried out on a target website corresponding to the initial authorization mechanism data source to obtain each root zone file contained in the initial authorization mechanism data source, and each root zone file is verified to obtain each second verification result;
and when the second verification results are the verification success, storing the root zone files.
Further, the step of determining the header file corresponding to each root zone file includes:
acquiring the corresponding acquisition time stamp, data source information, data source position information, data source address information, local address information and acquisition state information of each root zone file;
and integrating the acquisition time stamp, the data source information, the data source position information, the data source address information, the local address information and the acquisition state information which are respectively corresponding to the root zone files to obtain head files respectively corresponding to the root zone files.
Further, the merging rule includes a dividing rule, a filtering rule and a data retention rule, and the step of merging each to-be-merged root area file according to a preset merging rule to obtain a target root area file includes:
dividing each to-be-combined root zone file according to the dividing rule to obtain a top-level domain name field, a domain name field, an IN field, a domain name category field and a data source information field which are respectively corresponding to each to-be-combined root zone file;
determining a target field in each field according to the screening rule, and screening each to-be-combined root zone file based on the target field to obtain each target to-be-combined root zone file corresponding to the target field;
and merging the target root zone files to be merged according to the data retention rule to generate a target root zone file.
Further, after the step of merging the root zone files to be merged according to the preset merging rule to obtain the target root zone file, the method further includes:
determining the domain name fields corresponding to the entries contained in the target root zone file, determining the attribute values corresponding to the domain name fields, and sorting the entries based on the attribute values and a preset attribute value sorting rule;
And/or that the number of the groups of groups,
determining that the target root zone file contains the domain name category fields corresponding to the entries, and sorting the entries based on the domain name category fields and a preset domain name arrangement rule.
Further, before the step of adding each header file to the corresponding root zone file to generate a root zone file to be merged, the method further includes:
determining each core data source and each backup data source in a plurality of data sources, and determining each core root zone file corresponding to each core data source and each backup root zone file corresponding to each backup data source in each root zone file;
comparing each core root zone file with each backup root zone file to judge whether an abnormal root zone file exists in each root zone file or not;
if the abnormal root area files exist in the root area files, generating an abnormal log according to the abnormal root area files, and outputting the abnormal log to a management terminal for the management terminal to modify the abnormal root area files based on the abnormal log.
The method for generating the root zone file, the terminal equipment and the computer readable storage medium provided by the embodiment of the invention are applied to a root zone file management system, and a plurality of target data sources needing data acquisition are determined in a plurality of preset data sources, wherein the plurality of data sources comprise a blockchain data source, a local definition data source, a starting authority data source, a top domain name reporting data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source; acquiring data of a plurality of target data sources to acquire root zone files contained in the target data sources, and determining head files corresponding to the root zone files; and respectively adding each header file to the corresponding root zone file to generate a root zone file to be combined, and combining each root zone file to be combined according to a preset combining rule to obtain a target root zone file.
In this embodiment, when the terminal device is running, configuration information sent by a user through a management terminal is received first, a plurality of data sources are determined as target data sources needing to be subjected to data acquisition in a preset blockchain data source, a local definition data source, a starting authority data source, a top domain name reporting and standby data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source according to the configuration information, then the terminal device performs data acquisition on each target data source to obtain each root zone file contained in each target data source, the terminal device further determines each head file corresponding to each root zone file, then the terminal device adds the obtained head files to each corresponding root zone file to generate each root zone file to be combined, and the terminal device further combines each root zone file to be combined according to a preset combining rule to obtain each target root zone file.
In this way, the invention establishes a root domain name information issuing mechanism based on a plurality of data sources by determining a plurality of target data sources needing data acquisition in a plurality of preset data sources according to configuration information, sequentially acquiring each root zone file contained in each target data source, further adding a file header to each acquired root zone file and combining according to a preset combining rule to obtain the target root zone file, so that the root zone file contained in a single data source cannot influence DNS when being maliciously deleted or tampered, thereby solving the technical problem that some users currently controlling the root domain name resolution system can maliciously delete or tamper the top domain information mastered by other users through the root zone file issued by IANA, and further enabling users not mastering the root domain name resolution system to enter a 'stop-taking-off' state, thereby realizing the technical effect of constructing an autonomous controllable root domain name information issuing mechanism through the root zone files contained in a plurality of data sources and generating the autonomous controllable root zone file.
Drawings
Fig. 1 is a schematic structural diagram of a terminal device of a hardware running environment according to an embodiment of the present invention;
FIG. 2 is a flowchart of a first embodiment of a method for generating a root zone file according to the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a method for generating a root zone file according to the present invention;
FIG. 4 is a flowchart of a root zone file generation method according to a preferred embodiment of the present invention;
fig. 5 is a schematic diagram of a filtering rule related to an embodiment of a root zone file generating method according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic diagram of a terminal device structure of a hardware running environment according to an embodiment of the present invention.
It should be noted that fig. 1 may be a schematic structural diagram of a hardware operating environment of a terminal device. The terminal equipment of the embodiment of the invention can be the terminal equipment for executing the root zone file generation method provided by the invention, and the terminal equipment can be a data storage control terminal, a PC or a portable computer and other terminals.
As shown in fig. 1, the terminal device may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
It will be appreciated by those skilled in the art that the structure shown in fig. 1 does not constitute a limitation of the terminal device, and may include more or less components than illustrated, or may combine certain components, or may be arranged in different components.
As shown in fig. 1, the memory 1005, which is one type of storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and a root zone file generation method program.
In the terminal device shown in fig. 1, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the terminal device of the present invention may be provided in the terminal device, and the terminal device calls the root zone file generation method program stored in the memory 1005 through the processor 1001, and executes the root zone file generation method provided in the embodiment of the present invention.
Based on the terminal equipment, various embodiments of the root zone file generation method are provided.
Referring to fig. 2, fig. 2 is a flowchart illustrating a first embodiment of a root zone file generating method according to the present invention.
It should be understood that although a logical order is depicted in the flowchart, in some cases the method of generating a root zone file of the present invention may of course perform the steps shown or described in a different order than that which is depicted.
In this embodiment, the method for generating a root zone file according to the present invention may include the following steps:
Step S10: determining a plurality of target data sources needing data acquisition from a plurality of preset data sources, wherein the plurality of data sources comprise a blockchain data source, a local definition data source, a starting authority data source, a top domain name reporting data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source;
in this embodiment, the blockchain data source is a alliance blockchain formed by different root area management nodes, where the blockchain data source may be used to make the root area management nodes exchange and share the independently published root area data when the root area management nodes reach consensus, where the locally defined data source is the data source autonomously defined by the local root area management node, and the locally defined data source includes two parts of root server information autonomously defined by the user of the node and autonomously published TLD data, where the same, the initial authority data source is a global root system standard data source obtained by an IANA organization official, the same, top domain name backup data source is a data source of autonomously published TLD data prepared by the root area management nodes, the same, top domain name exchange data source is a data source capable of making the root area management nodes obtain the TLD information of other root area management nodes in the alliance respectively in an http request manner, and the same, and the web crawler data source includes a root crawler part and a data source of the TLD crawler part, where the root crawler part includes 13 root server information and the root crawler part can also obtain the root crawler part and the other data of the root crawler part in an http request manner from the root area 1, and the root crawler part can obtain the complete data of the root crawler in a root area of the complete system by the way of the root crawler from the root server node, and the root crawler is a root crawler node in the way of the root area of the root crawler is a root server.
The terminal equipment firstly receives configuration information sent by a user through the management terminal, determines a plurality of target data sources needing data acquisition in a preset blockchain data source, a local definition data source, a starting authority data source, a top domain name backup data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source according to the configuration information, and determines priority relations corresponding to the plurality of target data sources.
For example, a user firstly sets a terminal device in a plurality of data sources through a root zone management interface configured in a management terminal to set a blockchain data source, a local definition data source, an IANA data source, a TLD backup data source and a TLD exchange data source as core data sources, sets respective corresponding data acquisition intervals of the core data sources, sets a web crawler data source and a root zone file exchange data source as backup data sources through the root zone management interface and generates corresponding data acquisition intervals of the backup data sources to generate a configuration file, and sends the configuration file to the terminal device.
It should be noted that in this embodiment, the terminal device may set all seven data sources as target data sources, and may select any number of data sources among the seven data sources as target data sources, for example, the terminal device may set a blockchain data source, a local definition data source, an IANA data source, a TLD backup data source, a TLD exchange data source as target data source, or set a smaller number of data sources as target data sources based on configuration information, and it is understood that the terminal device should set at least two data sources as target data sources, so as to prevent a root zone file contained in a single data source from being maliciously deleted or tampered.
Step S20: acquiring data of a plurality of target data sources to acquire root zone files contained in the target data sources, and determining head files corresponding to the root zone files;
in this embodiment, when determining a priority relationship corresponding to a plurality of target data sources, the terminal device sequentially performs data acquisition on the plurality of target data sources according to the priority relationship to obtain each root area file contained in each target data source, and determines header files corresponding to each root area file according to the obtained data sources corresponding to each root area file.
For example, when determining that the priority relationship corresponding to the multiple target data sources is blockchain data source > local definition data source > IANA data source > TLD backup data source > TLD exchange data source > web crawler data source > root zone file exchange data source, the terminal device sequentially performs data acquisition on the blockchain data source, the local definition data source, the IANA data source, the TLD backup data source, the TLD exchange data source, the web crawler data source and the root zone file exchange data source according to the priority order to acquire each root zone file contained in each target data source, and then determines the header file corresponding to each root zone file according to the data source type corresponding to each root zone file acquired by the terminal device zone.
Further, in a possible embodiment, the step of "performing data collection on the plurality of target data sources to obtain the root zone files contained in the plurality of target data sources" in the step S20 may specifically include:
step S201: acquiring data of the block chain data source to acquire a root zone file contained in the block chain data source;
step S202: acquiring data of the local definition data source to acquire self-defined top-level domain data contained in the local definition data source, and determining the self-defined top-level domain data as the root zone file contained in the local definition data source;
Step S203: acquiring data of the initial authority data source to acquire the root zone file contained in the initial authority data source;
step S204: the data acquisition is carried out on the top-level domain name reporting and preparing data source so as to obtain top-level domain data which is issued by the management node through the top-level domain name reporting and preparing data source, and the top-level domain data is determined to be each root zone file contained in the top-level domain name reporting and preparing data source;
step S205: data acquisition is carried out on the top-level domain name exchange data source to obtain the top-level domain data corresponding to each of the plurality of management nodes, and each top-level domain data is determined to be each root zone file contained in the top-level domain name exchange data source;
step S206: acquiring data of the web crawler data source to acquire root crawler data and top-level domain name crawler data contained in the web crawler data source, and integrating the root crawler data and the top-level domain name crawler data to acquire the root zone file contained in the web crawler data source;
step S207: acquiring data of the root zone file exchange data source to acquire complete root zone files corresponding to the management nodes, and determining the complete root zone files as the root zone files contained in the root zone file exchange data source;
For example, the terminal device firstly performs data acquisition on a preset alliance blockchain formed by different root zone management nodes according to a priority order, so as to obtain each root zone file contained in a blockchain data source, then the terminal device collects a preset local definition data source according to the priority order, acquires root server information autonomously defined by a user and TLD data autonomously issued by the user and contained in the local definition data source, the terminal device further determines the TLD data as each root zone file contained in the local definition data source, then the terminal device performs data acquisition on the IANA data source according to the priority order, acquires each root zone file in the IANA data source respectively through a preset HTTP-based data acquisition mode and an AXFR data acquisition mode, and further merges each root zone file respectively acquired through the HTTP-based data acquisition mode and the AXFR data acquisition mode to serve as each root zone file contained in the IANA data source;
the terminal equipment further performs data acquisition on the TLD backup data sources according to the priority order to acquire TLD data which is autonomously released by the local root zone management nodes through the TLD backup data sources, so that acquired TLD data are used as root zone files corresponding to the TLD backup data sources, then the terminal equipment performs data acquisition on the TLD exchange data sources according to the priority order to acquire TLD data which are autonomously released by the root zone management nodes contained in the TLD exchange data sources, the terminal equipment determines the TLD data which are respectively corresponding to the root zone management nodes as root zone files contained in the TLD exchange data sources, then the terminal equipment performs data acquisition on the web crawler data sources according to the priority order to acquire 14 global root crawler data which are contained in the web crawler data sources and the TLD crawler data which are acquired through a DNS query mode, the terminal equipment further combines the acquired global root crawler data and the TLD crawler data to obtain the root zone files corresponding to the root zone management nodes, and then the terminal equipment can acquire the root zone files corresponding to the web crawler data sources according to the priority order, and the root zone files can be automatically released by the terminal equipment according to the priority order.
Further, in a possible embodiment, the step S203 may specifically include:
step S2031: acquiring each root zone file, each server address and each signature file contained in the data source of the initial authorization mechanism through a preset hypertext transfer protocol, and respectively verifying each root zone file, each server address and each signature file to obtain each first verification result, wherein the verification results comprise verification success and verification failure;
in this embodiment, the terminal device accesses the data source of the starting authority according to a preset hypertext transfer protocol request, so as to obtain each root area file, each server address and each signature file in the data source of the starting authority, and then, the terminal device verifies each root area file, each server address and each signature file through a preset verification tool to obtain each first verification result, and meanwhile, the terminal device determines whether the first verification result is verification success or verification failure.
Step S2032: when the first verification results are the verification success, storing the root zone files, the server addresses and the signature files to form the root zone files;
In this embodiment, when determining that each first verification result is verification success, the terminal device stores each acquired root area file, each server address and each signature file, and integrates each root area file with each corresponding server address and signature file as a root area file corresponding to the data source of the starting authority.
For example, the terminal device accesses the IANA data source according to a preset http protocol, so as to obtain each root area file, each server ip address and each signature file contained in the IANA data source, then the terminal device invokes a gpg tool pre-installed by a technician, and verifies each root area file, each server ip address and each signature file through a gog tool to generate each first verification result, then the terminal device judges each first verification result and determines whether each first verification result is verification success or verification failure, and then when determining that each first verification result is verification success, the terminal device stores each obtained root area file, each server ip address and each signature file, and integrates each root area file with each corresponding server ip address and signature file as the root area file corresponding to the IANA data source.
Further, in a possible embodiment, the step S203 may further include:
step S2033: recursion is carried out on a target website corresponding to the initial authorization mechanism data source to obtain each root zone file contained in the initial authorization mechanism data source, and each root zone file is verified to obtain each second verification result;
in this embodiment, the terminal device recursively acquires each root area file included in the data source of the starting authority by periodically recursing the website corresponding to the data source of the starting authority according to a time interval preset by the user, and then invokes the verification tool to verify each acquired root area file and obtain each second verification result, and the terminal device further determines each second verification result to determine whether the second result is successful verification or failed verification.
Step S2034: when the second verification results are successful in verification, storing the root zone files;
in this embodiment, when determining that each second verification result is verification success, the terminal device stores each acquired root area file, and determines each root area file as each root area file corresponding to the data source of the starting authority.
For example, the terminal device recursively acquires each root area file included in the IANA data source by periodically recursing the website xfr.lax.dns.icann.org corresponding to the IANA data source according to a time interval preset by a user through the root area configuration interface, then the terminal device invokes a verification tool dnssec-verify tool pre-installed by a technician, verifies the acquired each root area file respectively through the dnssec-verify tool to obtain each second verification result, then the terminal device judges whether the second verification result is verification success or verification failure, and stores the acquired each root area file and determines each root area file as each root area file corresponding to the IANA data source when determining that each second verification result is verification success.
Further, in a possible embodiment, the step of determining the header file corresponding to each root area file in the step S20 may specifically include:
step S208: acquiring the corresponding acquisition time stamp, data source information, data source position information, data source address information, local address information and acquisition state information of each root zone file;
in this embodiment, when the terminal device obtains each root area file, the terminal device determines, according to the data source type corresponding to each root area file, the acquisition timestamp, the data source information, the data source position information, the data source address information, the local address information and the acquisition status information corresponding to each root area file.
Step S209: integrating the acquisition time stamp, the data source information, the data source position information, the data source address information, the local address information and the acquisition state information which are respectively corresponding to the root zone files to obtain head files respectively corresponding to the root zone files;
in this embodiment, the terminal device determines the acquired acquisition timestamp, data source information, data source location information, data source address information, local address information and acquisition status information corresponding to each root area file, and integrates the acquisition timestamp, data source information, data source location information, data source address information, local address information and acquisition status information corresponding to each root area file according to a preset format to generate each header file.
For example, when the terminal device obtains the root zone file in the IANA data source, the acquisition timestamp corresponding to the root zone file is determined to be: 20210101T120000Z, the same, terminal equipment determines that the data source information source id corresponding to the root zone file is iana-http-1, the same, terminal equipment determines that the data source position information source locator corresponding to the root zone file is https:// www.internic.net/domain/root. Zone, the same, terminal equipment determines that the data source ip address information source IP address corresponding to the root zone file is 192.0.32.9, the same, terminal equipment determines that the local ip address information backup point IP address corresponding to the root zone file is 10.1.2.3, the same, terminal equipment determines that the acquisition status information status corresponding to the root zone file is success, and then the terminal equipment integrates the acquisition timestamp timstamp, the data source information source locator, the data source ip address information source IP address, the local ip address information backup point IP address and the acquisition status information status corresponding to the root zone file to begin with "/n" and end according to the type: the format of the value "is integrated to obtain a header file:
；timestamp： 20210101T120000Z
；source id： iana-http-1
； source locator： https://www.internic.net/domain/root.zone
； source IP address： 192.0.32.9
； backup point IP address： 10.1.2.3
； status：success。
Step S30: respectively adding each header file to the corresponding root zone file to generate a root zone file to be combined, and combining each root zone file to be combined according to a preset combining rule to obtain a target root zone file;
in this embodiment, after determining the header files corresponding to the root area files, the terminal device adds each header file to the root area file corresponding to each header file to form a root area file to be combined with the header file, and further obtains a preset combining rule, and combines the obtained root area files to be combined according to the combining rule to generate the target root area file.
For example, after determining a header file corresponding to a root zone file adopted by the IANA data source, the terminal device adds the header file to the front end of the root zone file to form a root zone file to be combined with the header file, and then reads an internally configured storage device to obtain a combining rule stored in advance by a technician, and screens and combines the obtained root zone files to be combined according to the combining rule to generate a target root zone file.
Further, in a possible embodiment, the merging rule includes a dividing rule, a filtering rule, and a data retention rule, and the step of merging each to-be-merged root area file according to a preset merging rule in the step S30 to obtain a target root area file may specifically include:
Step S301: dividing each to-be-combined root zone file according to the dividing rule to obtain a top-level domain name field, a domain name field, an IN field, a domain name category field and a data source information field which are respectively corresponding to each to-be-combined root zone file;
IN this embodiment, when acquiring a merge rule, a terminal device first determines a partition rule included IN the merge rule, and divides each root zone file to be merged according to the partition rule, so as to determine a top domain name field, a domain name field, an IN field, a domain name category field, and a data source information field corresponding to each root zone file to be merged.
Step S302: determining a target field in each field according to the screening rule, and screening each to-be-combined root zone file based on the target field to obtain each target to-be-combined root zone file corresponding to the target field;
in this embodiment, after the terminal device completes the division of the root area files to be merged, it further determines a filtering rule included in the merging rule, and determines a target field in each field according to the filtering rule, so as to filter each root area file to be merged based on the filtering rule and the target field to obtain each target root area file to be merged corresponding to the target field.
Step S303: merging the target root zone files to be merged according to the data retention rule to generate a target root zone file;
in this embodiment, the terminal device further determines a data retention rule included in the merge rule, and determines a file to be retained in each root zone file to be merged according to the data retention rule, so as to determine the file to be retained as a target root zone file.
For example, please refer to fig. 5, fig. 5 is a schematic diagram illustrating a filtering rule related to an embodiment of a root zone file generating method according to the present invention; when the terminal equipment acquires a merging rule, firstly determining a dividing rule contained IN the merging rule, dividing each root zone file to be merged according to the dividing rule, thus obtaining a top-level domain name field table_name, a domain name field host_name, an IN field class_name, a domain name category field type_name and a data source information field source corresponding to each root zone file to be merged, further, when the terminal equipment further defines the data source corresponding to each domain name field table_name, a domain name field host_name, an IN field class_name, a domain name category field type_name and a data source information field source corresponding to each root zone file to be merged according to the dividing rule, combining and storing the top-level domain name field table_name, the domain name field host_name, the IN field class name and the domain name field source IN a preset pyhton dictionary IN a form of [ table_name ] [ type_name ] [ source' ], and then, when the screening rule is set up the data source information corresponding to the domain name is only, and then, the terminal equipment further generates a target root zone to be merged according to the target zone, sequentially, and sequentially stores the target zone to the terminal equipment IN the root zone to be merged, and the terminal equipment is then sequentially stores the target zone to the target zone;
For example, when the terminal device first obtains the root area file from the IANA data source according to the priority order, the root area file includes the header files as follows:
example.org.3600INA11.11.11.11；
example.org.3600INA12.21.23.21；
then, the header file contained in the root zone file acquired by the terminal device in the TLD backup data source is:
example.org.17200INA11.23.11.00；
example.org.17200INA22.31.23.22；
and reserving the root zone file of the IANA data source as a target root zone file based on a preset data reservation rule.
Further, in a possible embodiment, after the step S30, the method for generating a root zone file according to the present invention may further include:
step A10: determining the domain name fields corresponding to the entries contained in the target root zone file, determining the attribute values corresponding to the domain name fields, and sorting the entries based on the attribute values and a preset attribute value sorting rule;
step A20: determining that the target root zone file contains each domain name category field corresponding to each item, and sorting the items based on each domain name category field and a preset domain name arrangement rule;
in this embodiment, the terminal device determines a domain name field host_name corresponding to each row of entries in the target root zone file, and divides the domain name field host_name into three parts, for example, when the domain name field host_name is a.nic. add, the terminal device divides the domain name field host_name into three parts of a, nic and add, and then the terminal device sequentially compares a value corresponding to a character string of the last part, a value corresponding to a character string of the last part and a value corresponding to a character string of the last part, and sorts the value in front according to a preset attribute value sorting rule, and sorts the value in back so as to finish sorting;
And/or that the number of the groups of groups,
the terminal equipment determines a domain name category field type_name corresponding to each row of entries in the target root zone file, and according to a preset domain name ordering rule: and (3) sequencing the domain name category fields type_name corresponding to each row of entries respectively by SOA > NS > DS > A > AAAA.
In this embodiment, the terminal device first receives configuration information sent by a user through the management terminal, and determines a plurality of target data sources to be subjected to data acquisition in a preset blockchain data source, a local definition data source, a start authority data source, a top domain name backup data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source according to the configuration information, determines a priority relation corresponding to the plurality of target data sources, sequentially performs data acquisition on the plurality of target data sources according to the priority relation when determining the priority relation corresponding to the plurality of target data sources, so as to obtain each root zone file contained in each target data source, determines a header file corresponding to each root zone file according to the data source corresponding to each obtained root zone file, and then, after determining the header files corresponding to each root zone file, respectively adds each header file into the root zone files corresponding to each header file to form a root zone file to be combined with the header file, and further obtains a preset combining rule, and performs data acquisition on the plurality of target zone files to be combined according to the preset combining rule.
In this way, the invention establishes a root domain name information issuing mechanism based on a plurality of data sources by determining a plurality of target data sources needing data acquisition in a plurality of preset data sources according to configuration information, sequentially acquiring each root zone file contained in each target data source, further adding a file header to each acquired root zone file and combining according to a preset combining rule to obtain the target root zone file, so that the root zone file contained in a single data source cannot influence DNS when being maliciously deleted or tampered, thereby solving the technical problem that some countries controlling the root domain name resolution system currently can maliciously delete or tamper the top domain information mastered by other countries through the root zone file issued by IANA, and further enabling countries not mastering the root domain name resolution system to enter a 'stop-server' state.
Further, referring to fig. 3, fig. 3 is a flowchart illustrating a second embodiment of a root zone file generating method according to the present invention, and based on the first embodiment of the root zone file generating method according to the present invention, the second embodiment of the root zone file generating method according to the present invention is provided herein.
Before the step S20, the method for generating a root zone file according to the present invention may further include:
step B10: determining each core data source and each backup data source in a plurality of data sources, and determining each core root zone file corresponding to each core data source and each backup root zone file corresponding to each backup data source in each root zone file;
in this embodiment, the terminal device determines a core data source and a backup data source from among the plurality of data sources according to the acquired configuration information, and determines a core root zone file from the core data source and a backup root zone file from the backup data source from among the acquired root zone files.
Step B20: comparing each core root zone file with each backup root zone file to judge whether an abnormal root zone file exists in each root zone file or not;
in this embodiment, the terminal device compares each obtained core root area file with each obtained backup root area file to obtain each comparison result, and the terminal device further determines whether an abnormal root area file exists in each obtained root area file according to each comparison result of the root areas.
Step B30: if the abnormal root zone files exist in the root zone files, generating an abnormal log according to the abnormal root zone files, and outputting the abnormal log to a management terminal for the management terminal to modify the abnormal root zone files based on the abnormal log;
In this embodiment, if the terminal device determines that an abnormal root area file exists in each root area file, an abnormal log is generated based on the abnormal root area file, and the abnormal log is sent to a management terminal connected to the terminal device, so that the management terminal modifies the abnormal root area file based on the abnormal log.
For example, the terminal device first reads the storage device to obtain a preset initial database table, further stores the obtained root zone files to be combined into the initial database table to generate a target database table, then determines a blockchain data source, a local definition data source, an IANA data source, a TLD backup data source and a TLD exchange data source as core data sources according to the obtained configuration information, determines root zone files to be combined from the blockchain data source, the local definition data source, the IANA data source, the TLD backup data source and the TLD exchange data source contained in the target database table as core root zone files, determines the root zone files to be combined from the blockchain data source, the local definition data source, the IANA data source, the TLD backup data source and the TLD exchange data source as backup root zone files, and simultaneously determines the webworm data source and the root zone file exchange data source as backup root zone files according to the obtained configuration information, then compares the core root zone files with the backup root zone files to determine whether the root zone files to be combined are in the root zone files to be combined, and further manages the root zone files to be combined by the terminal device to be connected to the user device through the log device when the abnormal root zone is further modified by the abnormal device.
It should be noted that, in this embodiment, the terminal device may further compare the abnormal log with the log backup stored in the root area backup storage server to obtain an abnormal cause, and further send the abnormal cause to the management terminal, so that the management terminal modifies the abnormal root area file based on the abnormal cause;
in addition, in another embodiment, the terminal device may further compare each to-be-merged root area file included in the target database table with each history root area file stored in the root area backup storage server, so as to obtain a comparison result, and further determine whether an abnormal root area file exists in each to-be-merged root area file according to the comparison result, and generate an abnormal log when determining that the abnormal root area file exists.
In this embodiment, the terminal device determines a core data source and a backup data source from a plurality of data sources according to the obtained configuration information, determines a core root zone file from the core data source and a backup root zone file from the backup data source from the obtained root zone files, then compares the obtained core root zone files with the obtained backup root zone files to obtain comparison results, and determines whether an abnormal root zone file exists in the obtained root zone files according to the comparison results of the terminal device and the root zone files, and finally, if the terminal device determines that the abnormal root zone file exists in the root zone files, generates an abnormal log based on the abnormal root zone file, and sends the abnormal log to a management terminal connected with the terminal device so that the management terminal modifies the abnormal root zone file based on the abnormal log.
In this way, the invention filters the abnormal root zone files by comparing the root zone files obtained from the multiple data sources, and generates the abnormal log according to the abnormal root zone files, so that the management terminal can modify the abnormal root zone files according to the abnormal log, thereby achieving the purpose of timely finding the abnormal root zone files when the root zone files contained in the single data source are tampered or deleted, and further enabling the management terminal to modify the abnormal root zone files in time.
Further, referring to fig. 4, fig. 4 is a flowchart illustrating a preferred embodiment of a root zone file generating method according to the present invention; based on the first embodiment and/or the second embodiment of the root zone file generating method of the present invention, preferred embodiments of the root zone file generating method of the present invention are provided herein.
In this embodiment, a user firstly enters a root management interface as shown in fig. 4 through a management terminal, sets a plurality of preset data sources in the root management interface to generate a configuration file, the management terminal further sends the configuration file to a terminal device, the terminal device determines the preset blockchain data source, the local definition data source, the IANA data source, the TLD backup data source, the TLD exchange data source, the web crawler data source and the root file exchange data source as target data sources needing to be subjected to data acquisition according to the configuration file, simultaneously sets the blockchain data source, the local definition data source, the IANA data source, the TLD backup data source and the TLD exchange data source as core data sources according to the configuration file, determines the priority sequence corresponding to the core data source as blockchain data source > local definition data source > IANA data source > TLD backup data source > TLD exchange data source, similarly, the terminal device determines that the web crawler data source and the root zone file exchange data source are backup data sources according to the configuration information, then the terminal device firstly reads rootchain data contained in the blockchain data source according to the priority order, further reads the custom data contained in the local definition data source, then the terminal device respectively reads the IANA data source through a preset http-based transmission mode and an AXFR-based transmission mode, combines the read data to integrate the IANA data, then the terminal device continues to read TLD data contained in the TLD backup data source, further reads exchange-TLD data contained in the TLD exchange data source, and simultaneously integrates 13 root crawler data, 1 AXFR root crawler data and TLD crawler data obtained in the web crawler data source to obtain carwler data, finally, the terminal equipment reads the root zone file exchange data to obtain exchange-rz data;
The terminal equipment adds corresponding header files to the acquired root zone file data to obtain root zone files to be combined, and inputs the root zone files to be combined into a root zone file storage server configured in the terminal equipment, meanwhile, the terminal equipment stores the acquired root zone files to be combined into a database table, compares the root zone files to be combined from each core data source with the root zone files to be combined from each backup data source in the database table to determine inconsistent conditions among the root zone files to be combined, and then, when the terminal equipment determines that the root zone files to be combined have no abnormal root zone files, the terminal equipment combines the root zone files to be combined according to preset combining rules to generate target root zone files, and issues the target root zone files according to preset time;
in addition, when the terminal equipment determines that the abnormal root zone files exist in the root zone files to be combined, generating an abnormal log based on the abnormal root zone files, sending the abnormal log to the management terminal through a mail report so that a user can adjust the abnormal root zone files through the management terminal, and meanwhile, the terminal equipment also needs to compare the abnormal root zone files with log backups stored in the root zone file storage server to obtain comparison results, and further determines the abnormal root zone files based on the comparison results.
In addition, the invention also provides a terminal device, the terminal device is provided with a root zone file generating program capable of running on a processor, and the terminal device realizes the steps of the root zone file generating method according to any one of the embodiments when executing the root zone file generating program.
The specific embodiment of the terminal device of the present invention is basically the same as each embodiment of the root zone file generating method described above, and will not be described herein.
In addition, the present invention also provides a computer readable storage medium, on which a root zone file generation program is stored, where the root zone file generation program, when executed by a processor, implements the steps of the root zone file generation method according to any one of the above embodiments.
The specific embodiments of the computer readable storage medium are basically the same as the embodiments of the root zone file generation method, and are not described herein.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of embodiments, it will be clear to a person skilled in the art that the above embodiment method may be implemented by means of software plus a necessary general hardware platform, but may of course also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a terminal device for performing the root zone file generation method provided by the present invention, which may be specifically a data storage control terminal, a PC or a portable computer, etc.) to perform the method described in the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (10)
1. A method for generating a root zone file, wherein the method is applied to a root zone file management system, and the method for generating the root zone file comprises the following steps:
determining a plurality of target data sources needing data acquisition from a plurality of preset data sources, wherein the plurality of data sources comprise a blockchain data source, a local definition data source, a starting authority data source, a top domain name reporting data source, a top domain name exchange data source, a web crawler data source and a root zone file exchange data source;
acquiring data of a plurality of target data sources to acquire root zone files contained in the target data sources, and determining head files corresponding to the root zone files;
and respectively adding each header file to the corresponding root zone file to generate a root zone file to be combined, and combining each root zone file to be combined according to a preset combining rule to obtain a target root zone file.
2. The method of generating a root zone file according to claim 1, wherein the root zone file management system comprises at least one management node, and the step of performing data collection on the plurality of target data sources to obtain the root zone files contained in the plurality of target data sources comprises:
Acquiring data of the block chain data source to acquire each root zone file contained in the block chain data source;
and/or that the number of the groups of groups,
acquiring data of the local definition data source to acquire respective definition top-level domain data contained in the local definition data source, and determining each custom top-level domain data as each root zone file contained in the local definition data source;
and/or that the number of the groups of groups,
acquiring data of the initial authority data source to acquire each root zone file contained in the initial authority data source;
and/or that the number of the groups of groups,
the data acquisition is carried out on the top-level domain name reporting and preparing data source so as to obtain top-level domain data which is issued by the management node through the top-level domain name reporting and preparing data source, and the top-level domain data is determined to be each root zone file contained in the top-level domain name reporting and preparing data source;
and/or that the number of the groups of groups,
data acquisition is carried out on the top-level domain name exchange data source to obtain the top-level domain data corresponding to each of the plurality of management nodes, and each top-level domain data is determined to be each root zone file contained in the top-level domain name exchange data source;
and/or that the number of the groups of groups,
Acquiring data of the web crawler data source to acquire root crawler data and top domain name crawler data contained in the web crawler data source, integrating the root crawler data and the top domain name crawler data, and determining the integrated data as root zone files contained in the web crawler data source;
and/or that the number of the groups of groups,
and acquiring data of the root zone file exchange data source to acquire complete root zone files corresponding to the management nodes, and determining the complete root zone files as the root zone files contained in the root zone file exchange data source.
3. The method of generating a root zone file according to claim 2, wherein the step of performing data collection on the starting authority data source to obtain each root zone file contained in the starting authority data source comprises:
acquiring each root zone file, each server address and each signature file contained in the data source of the initial authorization mechanism through a preset hypertext transfer protocol, and respectively verifying each root zone file, each server address and each signature file to obtain each first verification result, wherein the verification results comprise verification success and verification failure;
And when the first verification results are the verification success, storing the root zone files, the server addresses and the signature files to form the root zone files.
4. The method of claim 3, wherein the step of performing data collection on the starting authority data source to obtain each root zone file contained in the starting authority data source further comprises:
recursion is carried out on a target website corresponding to the initial authorization mechanism data source to obtain each root zone file contained in the initial authorization mechanism data source, and each root zone file is verified to obtain each second verification result;
and when the second verification results are the verification success, storing the root zone files.
5. The method of generating a root zone file according to claim 1, wherein the step of determining a header file corresponding to each root zone file comprises:
acquiring the corresponding acquisition time stamp, data source information, data source position information, data source address information, local address information and acquisition state information of each root zone file;
And integrating the acquisition time stamp, the data source information, the data source position information, the data source address information, the local address information and the acquisition state information which are respectively corresponding to the root zone files to obtain head files respectively corresponding to the root zone files.
6. The method for generating root zone files according to claim 1, wherein the merging rule comprises a partitioning rule, a filtering rule and a data retention rule, and the step of merging the root zone files to be merged according to a preset merging rule to obtain the target root zone file comprises the following steps:
dividing each to-be-combined root zone file according to the dividing rule to obtain a top-level domain name field, a domain name field, an IN field, a domain name category field and a data source information field which are respectively corresponding to each to-be-combined root zone file;
determining a target field in each field according to the screening rule, and screening each to-be-combined root zone file based on the target field to obtain each target to-be-combined root zone file corresponding to the target field;
and merging the target root zone files to be merged according to the data retention rule to generate a target root zone file.
7. The method for generating root zone files according to claim 6, wherein after the step of merging each of the root zone files to be merged according to a preset merging rule to obtain a target root zone file, the method further comprises:
determining the domain name fields corresponding to the entries contained in the target root zone file, determining the attribute values corresponding to the domain name fields, and sorting the entries based on the attribute values and a preset attribute value sorting rule;
and/or that the number of the groups of groups,
determining that the target root zone file contains the domain name category fields corresponding to the entries, and sorting the entries based on the domain name category fields and a preset domain name arrangement rule.
8. The method of generating a root zone file according to claim 1, wherein before the step of adding each of the header files to the corresponding root zone file to generate a root zone file to be merged, respectively, the method further comprises:
determining each core data source and each backup data source in a plurality of data sources, and determining each core root zone file corresponding to each core data source and each backup root zone file corresponding to each backup data source in each root zone file;
Comparing each core root zone file with each backup root zone file to judge whether an abnormal root zone file exists in each root zone file or not;
if the abnormal root area files exist in the root area files, generating an abnormal log according to the abnormal root area files, and outputting the abnormal log to a management terminal for the management terminal to modify the abnormal root area files based on the abnormal log.
9. A terminal device, characterized in that the terminal device comprises: memory, a processor and a root zone file generation program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the root zone file generation method according to any one of claims 1 to 8.
10. A computer-readable storage medium, wherein a root zone file generation program is stored on the computer-readable storage medium, which when executed by a processor, implements the steps of the root zone file generation method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310202815.7A CN116069738B (en) | 2023-03-06 | 2023-03-06 | Root zone file generation method, terminal equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310202815.7A CN116069738B (en) | 2023-03-06 | 2023-03-06 | Root zone file generation method, terminal equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116069738A true CN116069738A (en) | 2023-05-05 |
| CN116069738B CN116069738B (en) | 2023-08-25 |
Family
ID=86175057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310202815.7A Active CN116069738B (en) | 2023-03-06 | 2023-03-06 | Root zone file generation method, terminal equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116069738B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017075869A1 (en) * | 2015-11-03 | 2017-05-11 | 中国互联网络信息中心 | Configuration method and service method of local dns root server |
| US9904721B1 (en) * | 2013-01-25 | 2018-02-27 | Gravic, Inc. | Source-side merging of distributed transactions prior to replication |
| CN108924271A (en) * | 2018-06-21 | 2018-11-30 | 广州大学 | It is a kind of country root node between method for interchanging data |
| CN109756589A (en) * | 2019-02-20 | 2019-05-14 | 中国互联网络信息中心 | A kind of domain-name information maintenance system controlled altogether in many ways based on block chain |
| CN111008235A (en) * | 2019-12-03 | 2020-04-14 | 成都四方伟业软件股份有限公司 | Spark-based small file merging method and system |
| CN113067836A (en) * | 2021-04-20 | 2021-07-02 | 哈尔滨工业大学 | Intelligent contract system based on decentralized DNS root zone management |
-
2023
- 2023-03-06 CN CN202310202815.7A patent/CN116069738B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9904721B1 (en) * | 2013-01-25 | 2018-02-27 | Gravic, Inc. | Source-side merging of distributed transactions prior to replication |
| WO2017075869A1 (en) * | 2015-11-03 | 2017-05-11 | 中国互联网络信息中心 | Configuration method and service method of local dns root server |
| CN108924271A (en) * | 2018-06-21 | 2018-11-30 | 广州大学 | It is a kind of country root node between method for interchanging data |
| CN109756589A (en) * | 2019-02-20 | 2019-05-14 | 中国互联网络信息中心 | A kind of domain-name information maintenance system controlled altogether in many ways based on block chain |
| CN111008235A (en) * | 2019-12-03 | 2020-04-14 | 成都四方伟业软件股份有限公司 | Spark-based small file merging method and system |
| CN113067836A (en) * | 2021-04-20 | 2021-07-02 | 哈尔滨工业大学 | Intelligent contract system based on decentralized DNS root zone management |
Non-Patent Citations (1)
| Title |
|---|
| 张宇等: "一个自主开放的互联网根域名解析体系", 一个自主开放的互联网根域名解析体系, vol. 2, no. 7, pages 57 - 69 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116069738B (en) | 2023-08-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7222036B2 (en) | Model training system and method and storage medium | |
| CN110602052B (en) | Micro-service processing method and server | |
| CN106612246A (en) | Unified authentication method for simulation identity | |
| CN108566449A (en) | Domain name mapping data managing method, system and storage system based on block chain | |
| CN107798037A (en) | The acquisition methods and server of user characteristic data | |
| CN106789227B (en) | A kind of internet behavior analysis method and internet behavior analytical equipment | |
| CN109672760B (en) | DNS root data distribution method and system based on block chain | |
| CN113220633A (en) | Unified file coding management method and system | |
| CN110611611B (en) | Web security access method for home gateway | |
| CN115189897A (en) | Access processing method and device for zero trust network, electronic equipment and storage medium | |
| CN101425117A (en) | Method and device for constructing SQL statement | |
| CN108073630B (en) | Service search access management method and system based on dynamic configuration | |
| CN109714363B (en) | Method and system for modifying switch password | |
| EP1280060A2 (en) | A system for managing a computer network | |
| CN116069738B (en) | Root zone file generation method, terminal equipment and computer readable storage medium | |
| CN113542418A (en) | File management method and device, electronic equipment and storage medium | |
| CN111506661B (en) | Content access management method, device and storage medium | |
| CN109117152B (en) | Service generation system and method | |
| JP2003162449A (en) | Integrated access management system, integrated access management device and its method and program | |
| CN110730063B (en) | Security verification method and system, internet of things platform, terminal and readable storage medium | |
| CN111339193B (en) | Category encoding method and device | |
| CN104717176A (en) | Access control method, access control system, and server | |
| CN114968276A (en) | Application program deployment method and device, computer equipment and storage medium | |
| JPH0950422A (en) | Interaction succession type access control method on computer network and server computer therefor | |
| CN111314745A (en) | Video network user management 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |