WO2019196406A1 - 一种基于区块链的去中心化根域名服务方法及系统 - Google Patents

一种基于区块链的去中心化根域名服务方法及系统 Download PDF

Info

Publication number
WO2019196406A1
WO2019196406A1 PCT/CN2018/115240 CN2018115240W WO2019196406A1 WO 2019196406 A1 WO2019196406 A1 WO 2019196406A1 CN 2018115240 W CN2018115240 W CN 2018115240W WO 2019196406 A1 WO2019196406 A1 WO 2019196406A1
Authority
WO
WIPO (PCT)
Prior art keywords
local
domain name
server
request
root server
Prior art date
Application number
PCT/CN2018/115240
Other languages
English (en)
French (fr)
Inventor
蒋文保
史博轩
章峰
Original Assignee
北京信息科技大学
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京信息科技大学 filed Critical 北京信息科技大学
Publication of WO2019196406A1 publication Critical patent/WO2019196406A1/zh

Links

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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/30—Decision processes by autonomous network management units using voting and bidding
    • 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/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
    • 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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • 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/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/065—Network architectures or network communication protocols for network security for supporting key management in a packet data network for group communications
    • 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/08—Network architectures or network communication protocols for network security for authentication of entities
    • 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/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general

Definitions

  • the present invention relates to the field of communications, and in particular, to a deblocking root domain name service method and system based on a blockchain.
  • the root domain name servers are distributed all over the world, so that most of the world's DNS (Domain Name System) domain name servers can find a number of 13 domain name servers based on A to M.
  • the root domain name server periodically synchronizes the root zone file from the hidden primary root domain name server.
  • the root domain name server stops serving, issues false information, or tampers with the message to achieve access redirection, a large number of Internet users will not be able to access the domain name normally.
  • the root domain name mirroring server improves the efficiency of domain name resolution, the resolution details need to be transmitted to the root domain name server, and the user's information privacy cannot be protected.
  • the present invention aims to provide at least one of the above-mentioned drawbacks to provide a deblocking root domain name service method and system based on blockchain to achieve equal interconnection of networks.
  • An aspect of the present invention provides a deblocking root domain name service method based on a blockchain, comprising: setting a deblocking root domain name service system based on a blockchain, and decentralizing a root domain name service system based on a blockchain
  • the method includes: N local subsystems, each local subsystem includes at least M clients, a local server cluster, and a local root server; wherein the local server cluster includes S servers, N ⁇ 1, M ⁇ 1, S ⁇ 1
  • the alliance chain which includes a local root server in each local subsystem; wherein: any of the local subsystems, any client, local root server, and alliance chain perform a top-level domain name change process, including: client-side
  • the local root server sends a domain name change request; the local root server receives the domain name change request, and sends a resolution request to the alliance chain; each local root server in the alliance chain receives the resolution request, makes a resolution, and after the resolution is passed, the domain name change is written into the respective Blockchain; the local root server sends the
  • the domain name resolution request is sent to the local root server.
  • the local root server receives the domain name resolution request and resolves the domain name resolution request.
  • the domain name is sent to the local server cluster.
  • the local server cluster receives the domain name location and sends the domain name to the target server.
  • the cluster sends the parsing request, receives the parsing result sent by the target server cluster, and sends the parsing result to the client;
  • the root server key change process is performed between the local root server and the federation chain in any local subsystem, including: local root
  • the server sends a key change request to the alliance chain; each local root server in the alliance chain receives the key change request and performs resolution; after the local root server resolution is passed, the key change operation is performed, and the public root server changes the broadcast public ; Public key after each league chain local root server receives changes recorded.
  • Another aspect of the present invention provides a deblocking root domain name service system based on a blockchain, comprising: N local subsystems, each local subsystem including at least M clients, a local server cluster, and a local root server
  • the local server cluster includes S servers, N ⁇ 1, M ⁇ 1, S ⁇ 1
  • the alliance chain the alliance chain includes local root servers in each local subsystem; wherein: any of the local subsystems
  • the top-level domain name change process is performed between the client, the local root server, and the federation chain, wherein: the client is configured to send a domain name change request to the local root server; the local root server is configured to receive the domain name change request, and send a resolution request to the alliance chain.
  • Each local root server in the alliance chain is used to receive resolution requests, make resolutions, and, after the resolution is passed, write the domain name changes to their respective blockchains; the local root server is also used to send the client to the client after the resolution is passed. Send the resolution result; execute between any client, local server cluster, and local root server in any local subsystem
  • the name resolution process wherein: the client is configured to send a domain name resolution request to the local server cluster; the local server cluster is configured to receive the domain name resolution request, recursively parse the cache, and send the domain name resolution to the local root server when the domain name does not exist in the cache
  • the local root server is configured to receive the domain name resolution request, and resolve the domain name resolution request, and send the domain name location to the local server cluster when the domain name exists; the local server cluster is also used to receive the domain name location, and send the analysis application to the target server cluster.
  • Public key after server change alliance The respective local root server, after receiving the public key is also used to change the recording.
  • the deblocking root domain name service method and system based on the blockchain provided by the embodiment of the present invention can implement the countries without relying on the centralized network node (server).
  • the network is sovereign and independent, achieving an independent and controllable, equal and interconnected network world.
  • FIG. 1 is a schematic structural diagram of a deblocking root domain name service system based on a blockchain according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a top-level domain name change in a deblocking root domain name service method based on a blockchain according to an embodiment of the present invention
  • FIG. 3 is a flowchart of domain name resolution in a deblocking root domain name service method based on a blockchain according to an embodiment of the present invention
  • FIG. 4 is a flowchart of verification in a deblocking root domain name service method based on a blockchain according to an embodiment of the present invention
  • FIG. 5 is a flowchart of applying for a subordinate domain name of a top-level universal domain name in a deblocking root domain name service method based on a blockchain according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a root server key change in a deblocking root domain name service method based on a blockchain according to an embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a deblocking root domain name service system based on a blockchain according to an embodiment of the present invention.
  • a deblocking root domain name service system based on a blockchain according to an embodiment of the present invention is provided. include:
  • N local subsystems 10 each of which includes at least M clients 101, a local server cluster 102, and a local root server 103; wherein the local server cluster 102 includes S servers, N ⁇ 1, M ⁇ 1 , S ⁇ 1;
  • Alliance chain 20 which includes a local root server in each local subsystem
  • a top-level domain name change process is performed between any of the client 101, the local root server 103, and the federation chain 20, including:
  • the client 101 is configured to send a domain name change request to the local root server 103.
  • the local root server 103 is configured to receive a domain name change request, and send a resolution request to the link chain 20;
  • Each local root server in the alliance chain 20 is configured to receive the resolution request, make a resolution, and, after the resolution is passed, write the domain name change into the respective blockchain;
  • the local root server 103 is further configured to send a resolution result to the client 101 after the resolution is passed;
  • the domain name resolution process is performed between any of the client 101, the local server cluster 102, and the local root server 103, including:
  • the client 101 is configured to send a domain name resolution request to the local server cluster 102.
  • the local server cluster 102 is configured to receive a domain name resolution request, and recursively parse the cache. When the domain name does not exist in the cache, the domain name resolution request is sent to the local root server 103.
  • the local root server 103 is configured to receive a domain name resolution request, parse the domain name resolution request, and send the domain name location to the local server cluster 102 when the domain name exists;
  • the local server cluster 102 is further configured to receive a domain name location, send a resolution request to the target server cluster, receive an analysis result sent by the target server cluster, and send the analysis result to the client 101.
  • the root server key change process is performed between the local root server 103 and the link chain 20 in any of the local subsystems 10, including:
  • the local root server 103 is configured to send a key change request to the linkchain 20;
  • Each local root server in the alliance chain 20 is configured to receive a key change request and perform a resolution
  • the local root server 103 is further configured to perform a key change operation after the resolution is passed, and broadcast the changed public key of the local root server 103;
  • Each local root server 103 in the alliance chain 20 is also configured to receive the changed public key for recording.
  • the present invention provides a new blockchain-based decentralized root domain name service system, and the blockchain-based decentralized root domain name service system provided by the embodiment of the present invention can be independent of centralization.
  • Network nodes servers
  • each country can set up a root server (the data of the root servers of each country is consistent), and the sub-clusters of the root servers relying on each country are determined by each country.
  • Top-level domain name changes (including application and modification, etc.) need to be resolved in the alliance chain, using relevant consensus algorithms to make overall decisions and record.
  • the domain name request is parsed, and the root servers of each country are responsible for parsing the requests of the countries, returning the results, and selecting whether to perform security verification according to the requirements.
  • Each root server can be asymmetrically encrypted and has the public key of another root server.
  • the public key modification needs to be passed through the resolution of the federation chain.
  • the keys of each sub-cluster are issued by the server signature of the upper level, and the key of the root server is determined at the beginning. If it needs to be changed, the resolution of the alliance chain is required and recorded.
  • the system of the present invention can be made sufficiently open and transparent, and the data of the blockchain is disclosed to all nodes therein.
  • the stability and reliability of the system is higher. Once the information is verified and added to the blockchain, it will be stored. Unless more than 51% of the nodes can be controlled at the same time, the modification of the database on the single node is invalid. The data cannot be falsified, which enhances the credibility of the data. Further, data exchange between nodes operates in accordance with a fixed smart contract.
  • the local root server 103 receives the domain name change request by sending a resolution request to the link chain 20: the local root server 103 is further configured to receive the domain name change request, and set the verification legality. In the case of the process, the validity of the domain name change request is verified; when the domain name change request is legal, a resolution request is sent to the link chain 20. By setting whether the validity of the domain name change request needs to be verified on the local root server 103, the autonomous controllability of the verification can be achieved.
  • the local root server 103 is further configured to determine the scope of the domain name change request before the domain name change request belongs to the jurisdiction of the local root server 103, after receiving the domain name change request, and verifying the validity of the domain name change request. Verify the legality of the domain name change request.
  • the verification process is performed between any of the client 101, the local server cluster 102, and the local root server 103, wherein
  • the client 101 is configured to send a domain name verification request to the target server cluster;
  • the local server cluster 102 is configured to receive the domain name domain sent by the target server cluster, send an authentication request to the local root server 103, and the local root server 103 is configured to receive the verification.
  • the request sends the verification information to the local server cluster 102.
  • the local server cluster 102 is further configured to receive the verification information, verify the verification information, and send the verification result to the client 101 after the verification is passed.
  • the client 101 can be authenticated to the target server, and the authenticity of the target server is improved to ensure the security of subsequent data interaction.
  • the verification request includes a signature query request; the local root server 103 receives the verification request by sending the verification information to the local server cluster 102: the local root server 103 is further configured to receive the signature query request, query the signature of the domain name, and The local server cluster 102 sends a signature; the local server cluster 102 receives the verification information, verifies the verification information, and sends the verification result to the client 101 after the verification is passed: the local server cluster 102 is also used to receive the signature and verify The signature is sent, and after the verification is passed, the verification result is sent to the client 101. Therefore, the authenticity of the target server can be verified by means of signature and verification, so as to improve the security of subsequent data interaction.
  • any of the local subsystems 10, the client 101 and the local root server 103 perform a subordinate domain name application process of the top-level universal domain name, wherein the client 101 is used for Sending a domain name location request to the local root server 103; the local root server 103 is configured to receive the domain name location request, parse the domain name location request, and send the universal domain location to the client 101; the client 101 is further configured to receive the universal domain location Sending a domain name application request to the universal domain name cluster and receiving the processing result sent by the universal domain name cluster. Since the domain name change of the responsible regions of each country is handled by the countries themselves, the autonomy of each country's own domain name management is guaranteed.
  • FIG. 2 to FIG. 5 are flowcharts showing a method for decentralized root domain name service based on blockchain according to an embodiment of the present invention.
  • a blockchain-based decentralized root domain name service method provided by an embodiment of the present invention includes:
  • the deblocking root domain name service system based on blockchain includes:
  • each local subsystem includes at least M clients, a local server cluster, and a local root server; wherein, the local server cluster includes S servers, N ⁇ 1, M ⁇ 1, S ⁇ 1;
  • Alliance chain which includes a local root server in each local subsystem
  • the client sends a domain name change request to the local root server
  • the local root server receives the domain name change request and sends a resolution request to the alliance chain;
  • Each local root server in the alliance chain receives the resolution request, makes a resolution, and after the resolution is passed, writes the domain name change into its respective blockchain;
  • the resolution result is sent to the client;
  • the domain name resolution process is performed between any of the local subsystems, the local server cluster, and the local root server, including:
  • the client sends a domain name resolution request to the local server cluster
  • the local server cluster receives the domain name resolution request, and recursively resolves the cache.
  • the domain name resolution request is sent to the local root server.
  • the local root server receives the domain name resolution request, resolves the domain name resolution request, and sends the domain name location to the local server cluster when the domain name exists;
  • the local server cluster receives the domain name location, sends a resolution request to the target server cluster, receives the parsing result sent by the target server cluster, and sends the parsing result to the client;
  • the root server key change process between the local root server and the federation chain in any local subsystem including:
  • the local root server sends a key change request to the coalition chain
  • Each local root server in the alliance chain receives a key change request and performs a resolution
  • the key change operation is performed, and the public key of the local root server is broadcasted;
  • Each local root server in the federation chain receives the changed public key and records it.
  • the method for decentralizing the root domain name service based on the blockchain may not be provided on the premise that a new blockchain-based decentralized root domain name service system is set up in the present invention. It relies on centralized network nodes (servers) to realize the sovereign independence of each country's networks and realize an independent and controllable, equal and interconnected network world.
  • servers centralized network nodes
  • each country can set up a root server (the data of the root servers of each country is consistent), and the sub-clusters of the root servers relying on each country are determined by each country.
  • Top-level domain name changes (including application and modification, etc.) need to be resolved in the alliance chain, using relevant consensus algorithms to make overall decisions and record.
  • the domain name request is parsed, and the root servers of each country are responsible for parsing the requests of the countries, returning the results, and selecting whether to perform security verification according to the requirements.
  • Each root server can be asymmetrically encrypted and has the public key of another root server.
  • the public key modification needs to be passed through the resolution of the federation chain.
  • the keys of each sub-cluster are issued by the server signature of the upper level, and the key of the root server is determined at the beginning. If it needs to be changed, the resolution of the alliance chain is required and recorded.
  • the system can be made sufficiently open and transparent, and the data of the blockchain is disclosed to all nodes therein.
  • the stability and reliability of the system is higher. Once the information is verified and added to the blockchain, it will be stored. Unless more than 51% of the nodes can be controlled at the same time, the modification of the database on the single node is invalid. The data cannot be falsified, which enhances the credibility of the data. Further, data exchange between nodes operates in accordance with a fixed smart contract.
  • the local root server receives the domain name change request, and sends the resolution request to the alliance chain, where the local root server receives the domain name change request, and verifies the domain name change in the process of setting the verification legality.
  • the legality of the request ; the local root server sends a resolution request to the coalition chain if the domain name change request is legal.
  • the autonomous controllability of verification can be achieved by setting the validity of the domain name change request on the local root server.
  • the method further includes: determining, by the local root server, the scope of the domain name change request, where the domain name change request belongs to the jurisdiction of the local root server, The steps to verify the legality of a domain name change request.
  • the verification process is performed between any client, the local server cluster, and the local root server, including: the client The target server cluster sends a domain name verification request; the local server cluster receives the domain name domain sent by the target server cluster, and sends an authentication request to the local root server; the local root server receives the verification request, and sends the verification information to the local server cluster; the local server cluster receives the verification information, The verification information is verified, and after the verification is passed, the verification result is sent to the client.
  • the client to verify the target server and improve the authenticity of the target server to ensure the security of subsequent data interaction.
  • the verification request includes a signature query request; the local root server receives the verification request, and sends the verification information to the local server cluster, including: the local root server receives the signature query request, queries the signature of the domain name, and sends a signature to the local server cluster; the local server cluster Receiving the verification information, verifying the verification information, and sending the verification result to the client after the verification is passed, the local server cluster receives the signature, verifies the signature, and sends the verification result to the client after the verification is passed. Therefore, the authenticity of the target server can be verified by means of signature and verification, so as to improve the security of subsequent data interaction.
  • the application process of the subordinate domain name of the top-level universal domain name is performed between any of the local subsystems and the local root server, and the client sends the domain name to the local root server.
  • the local root server receives the domain name location request, parses the domain name location request, and sends the universal domain name location to the client;
  • the client receives the universal domain name location, sends the domain name application request to the universal domain name cluster, and receives the general domain name cluster sending process. result. Since the domain name change of the responsible regions of each country is handled by the countries themselves, the autonomy of each country's own domain name management is guaranteed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本发明提供了一种基于区块链的去中心化根域名服务方法及系统，其中方法包括：设置基于区块链的去中心化根域名服务系统包括：N个本地子系统，每个本地子系统至少包括M个客户端、本地服务器集群以及一个本地根服务器；其中，本地服务器集群包括S个服务器；联盟链，联盟链包括各个本地子系统中的本地根服务器；任一本地子系统中，任一客户端、本地根服务器以及联盟链之间执行顶级域名变更流程；任一客户端、本地服务器集群以及本地根服务器之间执行域名解析流程；本地根服务器以及联盟链之间执行根服务器密钥变动流程。由此可以不依赖于中心化的网络节点(服务器)，从而实现各国的网络主权独立，实现自主可控，平等互联的网络世界。

Description

一种基于区块链的去中心化根域名服务方法及系统
相关申请的交叉引用
本申请要求北京信息科技大学于2018年4月13日提交的、发明名称为“一种基于区块链的去中心化根域名服务方法及系统”的、中国专利申请号“2018103296180”的优先权。
技术领域
本发明涉及通信领域，尤其涉及一种基于区块链的去中心化根域名服务方法及系统。
背景技术
根域名服务器分布在世界各地，使世界上大部分DNS(Domain Name System)域名服务器都能就近找到一个编号为A～M的13台根据域名服务器。根域名服务器定期从隐藏主根域名服务器同步根区文件。
然而，根域名服务器一旦停止服务、发布虚假信息或者篡改消息实现访问的重定向，大量Internet用户将无法正常访问域名。根域名镜像服务器提升域名解析效率的同时，还需将解析的细节传送到根域名服务器上，用户的信息私密无法得到保护。
另外，主根域名服务器如果屏蔽指定的域名，则它们的地址将无法解析，集中式的管理无法摆脱控制。因此，需要一种更为安全有效的系统来集成世界各地的域名服务。
发明内容
本发明旨在至少克服上述缺陷之一提供一种基于区块链的去中心化根域名服务方法及系统，以实现网络的平等互联。
为达到上述目的，本发明的技术方案具体是这样实现的：
本发明的一个方面提供了一种基于区块链的去中心化根域名服务方法，包括：设置基于区块链的去中心化根域名服务系统，基于区块链的去中心化根域名服务系统包括：N个本地子系统，每个本地子系统至少包括M个客户端、本地服务器集群以及一个本地根服务器；其中，本地服务器集群包括S个服务器，N≥1，M≥1，S≥1；联盟链，联盟链包括各个本地子系统中的本地根服务器；其中：任一本地子系统中，任一客户端、本地根服务器以及联盟链之间执行顶级域名变更流程，包括：客户端向本地根服务器发送域名变更请 求；本地根服务器接收域名变更请求，向联盟链发送决议请求；联盟链中的各个本地根服务器接收决议请求，进行决议，并在决议通过后，将域名变更写入各自的区块链；本地根服务器在决议通过后，向客户端发送决议结果；任一本地子系统中，任一客户端、本地服务器集群以及本地根服务器之间执行域名解析流程，包括：客户端向本地服务器集群发送域名解析请求；本地服务器集群接收域名解析请求，递归解析缓存，在缓存中不存在域名时，向本地根服务器发送域名解析请求；本地根服务器接收域名解析请求，解析域名解析请求，在域名存在时，向本地服务器集群发送域名位置；本地服务器集群接收域名位置，向目标服务器集群发送解析申请，接收目标服务器集群解析后发送的解析结果，并向客户端发送解析结果；任一本地子系统中本地根服务器以及联盟链之间执行根服务器密钥变动流程，包括：本地根服务器向联盟链发送密钥变动请求；联盟链中的各个本地根服务器接收密钥变动请求，进行决议；本地根服务器决议通过后，执行密钥变动操作，并广播本地根服务器变动后的公钥；联盟链中的各个本地根服务器接收变动后的公钥，进行记录。
本发明另一方面提供了一种基于区块链的去中心化根域名服务系统，包括：N个本地子系统，每个本地子系统至少包括M个客户端、本地服务器集群以及一个本地根服务器；其中，本地服务器集群包括S个服务器，N≥1，M≥1，S≥1；联盟链，联盟链包括各个本地子系统中的本地根服务器；其中：任一本地子系统中，任一客户端、本地根服务器以及联盟链之间执行顶级域名变更流程，其中：客户端，用于向本地根服务器发送域名变更请求；本地根服务器，用于接收域名变更请求，向联盟链发送决议请求；联盟链中的各个本地根服务器，用于接收决议请求，进行决议，并在决议通过后，将域名变更写入各自的区块链；本地根服务器，还用于在决议通过后，向客户端发送决议结果；任一本地子系统中，任一客户端、本地服务器集群以及本地根服务器之间执行域名解析流程，其中：客户端，用于向本地服务器集群发送域名解析请求；本地服务器集群，用于接收域名解析请求，递归解析缓存，在缓存中不存在域名时，向本地根服务器发送域名解析请求；本地根服务器，用于接收域名解析请求，解析域名解析请求，在域名存在时，向本地服务器集群发送域名位置；本地服务器集群，还用于接收域名位置，向目标服务器集群发送解析申请，接收目标服务器集群解析后发送的解析结果，并向客户端发送解析结果；任一本地子系统中本地根服务器以及联盟链之间执行根服务器密钥变动流程，其中：本地根服务器，用于向联盟链发送密钥变动请求；联盟链中的各个本地根服务器，用于接收密钥变动请求，进行决议；本地根服务器，还用于在决议通过后，执行密钥变动操作，并广播本地根服务器变动后的公钥；联盟链中的各个本地根服务器，还用于接收变动后的公钥，进行记录。
由上述本发明提供的技术方案可以看出，通过本发明实施例提供的基于区块链的去中 心化根域名服务方法及系统，可以不依赖于中心化的网络节点(服务器)，从而实现各国的网络主权独立，实现自主可控，平等互联的网络世界。
附图说明
图1为本发明实施例提供的基于区块链的去中心化根域名服务系统的结构示意图；
图2为本发明实施例提供的基于区块链的去中心化根域名服务方法中的顶级域名变更流程图；
图3为本发明实施例提供的基于区块链的去中心化根域名服务方法中的域名解析流程图；
图4为本发明实施例提供的基于区块链的去中心化根域名服务方法中的验证流程图；
图5为本发明实施例提供的基于区块链的去中心化根域名服务方法中的顶级通用域名的下属域名申请流程图；
图6为本发明实施例提供的基于区块链的去中心化根域名服务方法中的根服务器密钥变动流程图。
具体实施方式
下面结合附图对本发明的实施方式进行详细说明。
图1示出了本发明实施例提供的基于区块链的去中心化根域名服务系统的结构示意图，参见图1，本发明实施例提供的基于区块链的去中心化根域名服务系统，包括：
N个本地子系统10，每个本地子系统10至少包括M个客户端101、本地服务器集群102以及一个本地根服务器103；其中，本地服务器集群102包括S个服务器，N≥1，M≥1，S≥1；
联盟链20，联盟链20包括各个本地子系统中的本地根服务器；
其中：
任一本地子系统10中，任一客户端101、本地根服务器103以及联盟链20之间执行顶级域名变更流程，包括：
客户端101，用于向本地根服务器103发送域名变更请求；
本地根服务器103，用于接收域名变更请求，向联盟链20发送决议请求；
联盟链20中的各个本地根服务器，用于接收决议请求，进行决议，并在决议通过后，将域名变更写入各自的区块链；
本地根服务器103，还用于在决议通过后，向客户端101发送决议结果；
任一本地子系统10中，任一客户端101、本地服务器集群102以及本地根服务器103之间执行域名解析流程，包括：
客户端101，用于向本地服务器集群102发送域名解析请求；
本地服务器集群102，用于接收域名解析请求，递归解析缓存，在缓存中不存在域名时，向本地根服务器103发送域名解析请求；
本地根服务器103，用于接收域名解析请求，解析域名解析请求，在域名存在时，向本地服务器集群102发送域名位置；
本地服务器集群102，还用于接收域名位置，向目标服务器集群发送解析申请，接收目标服务器集群解析后发送的解析结果，并向客户端101发送解析结果；
任一本地子系统10中本地根服务器103以及联盟链20之间执行根服务器密钥变动流程，包括：
本地根服务器103，用于向联盟链20发送密钥变动请求；
联盟链20中的各个本地根服务器，用于接收密钥变动请求，进行决议；
本地根服务器103，还用于在决议通过后，执行密钥变动操作，并广播本地根服务器103变动后的公钥；
联盟链20中的各个本地根服务器103，还用于接收变动后的公钥，进行记录。
由此可见，本发明架设了一个新的基于区块链的去中心化根域名服务系统，通过本发明实施例提供的基于区块链的去中心化根域名服务系统，可以不依赖于中心化的网络节点(服务器)，从而实现各国的网络主权独立，实现自主可控，平等互联的网络世界。
其中，在应用上，各国都可以设置一台根服务器(各国根服务器的数据一致)，各国依托于各个国家的根服务器的子集群由各个国家自主决定。
顶级的域名变更(包括申请与修改等)需要在联盟链进行提出决议，采用相关的共识算法来进行整体决议并记录。
域名请求解析，各国根服务器负责解析各国的请求，并返回结果，根据需求来选择是否进行安全性验证。
各个根服务器可以采用非对称加密的方式，拥有其他根服务器的公钥，公钥修改需要通过联盟链的决议来通过。
各个子集群的密钥由其上一级的服务器签名颁发，根服务器的密钥，则在开始时就确定，如需变动，需要联盟链的决议并且进行记录。
由此可见，由于使用分布式核算和存储，不存在中心化节点，系统中的数据块由整个系统中具有维护功能的节点(联盟链)来共同维护。
同时，应用本发明的系统，可以使得系统足够开放、透明，且区块链的数据对其中的所有节点公开。
系统的稳定性和可靠性更高，一旦信息经过验证并添加至区块链就会存储起来，除非能够同时控制超过51％的节点，否则单个节点上对数据库的修改是无效的，从而实现了数据的不可篡改，增强了数据的可信度。进一步，节点之间的数据交换遵循固定的智能合约进行操作。
此外，还避免了霸权主义国家对DNS的独裁统治，构建平等互联的网络世界，极大的促进各国之间互通有无。
作为本发明实施例的一个可选实施方式，本地根服务器103通过如下方式接收域名变更请求，向联盟链20发送决议请求：本地根服务器103，还用于接收域名变更请求，在设置验证合法性的流程的情况下，验证域名变更请求的合法性；在域名变更请求合法的情况下，向联盟链20发送决议请求。通过在本地根服务器103上设置是否需要验证域名变更请求的合法性，可以实现验证的自主可控性。进一步地，本地根服务器103在接收域名变更请求之后，验证域名变更请求的合法性之前，还用于判断域名变更请求的所属范围，在域名变更请求属于本地根服务器103的管辖范围的情况下，验证域名变更请求的合法性。通过事先判断域名变更请求的所属范围，可以在不属于所属范围的情况下不需要进行后续处理，只有在属于所属范围的情况下才进行后续处理，提高了程序执行效率。
作为本发明实施例的一个可选实施方式，任一本地子系统10中，在设置验证流程的情况下，任一客户端101、本地服务器集群102以及本地根服务器103之间执行验证流程，其中：客户端101，用于向目标服务器集群发送域名验证请求；本地服务器集群102，用于接收目标服务器集群发送的域名域，向本地根服务器103发送验证请求；本地根服务器103，用于接收验证请求，向本地服务器集群102发送验证信息；本地服务器集群102，还用于接收验证信息，对验证信息进行验证，并在验证通过后，向客户端101发送验证结果。由此可以使得客户端101对目标服务器进行验证，提高了目标服务器的真实性，以保证后续数据交互的安全性。进一步地，验证请求包括签名查询请求；本地根服务器103通过如下方式接收验证请求，向本地服务器集群102发送验证信息：本地根服务器103，还用于接收签名查询请求，查询域名的签名，并向本地服务器集群102发送签名；本地服务器集群102通过如下方式接收验证信息，对验证信息进行验证，并在验证通过后，向客户端101发送验证结果：本地服务器集群102，还用于接收签名，验证签名，并在验证通过后，向客户端101发送验证结果。由此可以通过签名和验签的方式，验证目标服务器的真实性，以提高后续数据交互的安全性。
作为本发明实施例的一个可选实施方式，任一本地子系统10中，任一客户端101以及本地根服务器103之间执行顶级通用域名的下属域名申请流程，其中，客户端101，用于向本地根服务器103发送获取域名位置请求；本地根服务器103，用于接收获取域名位置请求，解析获取域名位置请求，向客户端101发送通用域名位置；客户端101，还用于接收通用域名位置，向通用域名集群发送域名申请请求，并接收通用域名集群发送的处理结果。由于各国的负责区域的域名变更由各国自行处理，因此保证了各国对各国自身的域名管理的自主性。
图2至图5示出了本发明实施例提供的基于区块链的去中心化根域名服务方法中的各个流程图，本发明实施例提供的基于区块链的去中心化根域名服务方法应用于上述系统，以下仅对本发明实施例提供的基于区块链的去中心化根域名服务方法进行简单说明，其他未尽事宜，具体参见上述系统的相关说明。参见图2至图5，本发明实施例提供的基于区块链的去中心化根域名服务方法，包括：
设置基于区块链的去中心化根域名服务系统，基于区块链的去中心化根域名服务系统包括：
N个本地子系统，每个本地子系统至少包括M个客户端、本地服务器集群以及一个本地根服务器；其中，本地服务器集群包括S个服务器，N≥1，M≥1，S≥1；
联盟链，联盟链包括各个本地子系统中的本地根服务器；
其中：
任一本地子系统中，任一客户端、本地根服务器以及联盟链之间执行顶级域名变更流程，包括：
客户端向本地根服务器发送域名变更请求；
本地根服务器接收域名变更请求，向联盟链发送决议请求；
联盟链中的各个本地根服务器接收决议请求，进行决议，并在决议通过后，将域名变更写入各自的区块链；
本地根服务器在决议通过后，向客户端发送决议结果；
任一本地子系统中，任一客户端、本地服务器集群以及本地根服务器之间执行域名解析流程，包括：
客户端向本地服务器集群发送域名解析请求；
本地服务器集群接收域名解析请求，递归解析缓存，在缓存中不存在域名时，向本地根服务器发送域名解析请求；
本地根服务器接收域名解析请求，解析域名解析请求，在域名存在时，向本地服务器 集群发送域名位置；
本地服务器集群接收域名位置，向目标服务器集群发送解析申请，接收目标服务器集群解析后发送的解析结果，并向客户端发送解析结果；
任一本地子系统中本地根服务器以及联盟链之间执行根服务器密钥变动流程，包括：
本地根服务器向联盟链发送密钥变动请求；
联盟链中的各个本地根服务器接收密钥变动请求，进行决议；
本地根服务器在决议通过后，执行密钥变动操作，并广播本地根服务器变动后的公钥；
联盟链中的各个本地根服务器接收变动后的公钥，进行记录。
由此可见，本发明在架设了一个新的基于区块链的去中心化根域名服务系统的前提下，通过本发明实施例提供的基于区块链的去中心化根域名服务方法，可以不依赖于中心化的网络节点(服务器)，从而实现各国的网络主权独立，实现自主可控，平等互联的网络世界。
其中，在应用上，各国都可以设置一台根服务器(各国根服务器的数据一致)，各国依托于各个国家的根服务器的子集群由各个国家自主决定。
顶级的域名变更(包括申请与修改等)需要在联盟链进行提出决议，采用相关的共识算法来进行整体决议并记录。
域名请求解析，各国根服务器负责解析各国的请求，并返回结果，根据需求来选择是否进行安全性验证。
各个根服务器可以采用非对称加密的方式，拥有其他根服务器的公钥，公钥修改需要通过联盟链的决议来通过。
各个子集群的密钥由其上一级的服务器签名颁发，根服务器的密钥，则在开始时就确定，如需变动，需要联盟链的决议并且进行记录。
由此可见，由于使用分布式核算和存储，不存在中心化节点，系统中的数据块由整个系统中具有维护功能的节点(联盟链)来共同维护。
同时，应用本发明的方法，可以使得系统足够开放、透明，且区块链的数据对其中的所有节点公开。
系统的稳定性和可靠性更高，一旦信息经过验证并添加至区块链就会存储起来，除非能够同时控制超过51％的节点，否则单个节点上对数据库的修改是无效的，从而实现了数据的不可篡改，增强了数据的可信度。进一步，节点之间的数据交换遵循固定的智能合约进行操作。
此外，还避免了霸权主义国家对DNS的独裁统治，构建平等互联的网络世界，极大的促进各国之间互通有无。
作为本发明实施例的一个可选实施方式，本地根服务器接收域名变更请求，向联盟链发送决议请求包括：本地根服务器接收域名变更请求，在设置验证合法性的流程的情况下，验证域名变更请求的合法性；本地根服务器在域名变更请求合法的情况下，向联盟链发送决议请求。通过在本地根服务器上设置是否需要验证域名变更请求的合法性，可以实现验证的自主可控性。进一步地，本地根服务器接收域名变更请求之后，验证域名变更请求的合法性之前，还包括：本地根服务器判断域名变更请求的所属范围，在域名变更请求属于本地根服务器的管辖范围的情况下，执行验证域名变更请求的合法性的步骤。通过事先判断域名变更请求的所属范围，可以在不属于所属范围的情况下不需要进行后续处理，只有在属于所属范围的情况下才进行后续处理，提高了程序执行效率。
作为本发明实施例的一个可选实施方式，任一本地子系统中，在设置验证流程的情况下，任一客户端、本地服务器集群以及本地根服务器之间执行验证流程，包括：客户端向目标服务器集群发送域名验证请求；本地服务器集群接收目标服务器集群发送的域名域，向本地根服务器发送验证请求；本地根服务器接收验证请求，向本地服务器集群发送验证信息；本地服务器集群接收验证信息，对验证信息进行验证，并在验证通过后，向客户端发送验证结果。由此可以使得客户端对目标服务器进行验证，提高了目标服务器的真实性，以保证后续数据交互的安全性。进一步地，验证请求包括签名查询请求；本地根服务器接收验证请求，向本地服务器集群发送验证信息包括：本地根服务器接收签名查询请求，查询域名的签名，并向本地服务器集群发送签名；本地服务器集群接收验证信息，对验证信息进行验证，并在验证通过后，向客户端发送验证结果包括：本地服务器集群接收签名，验证签名，并在验证通过后，向客户端发送验证结果。由此可以通过签名和验签的方式，验证目标服务器的真实性，以提高后续数据交互的安全性。
作为本发明实施例的一个可选实施方式，任一本地子系统中，任一客户端以及本地根服务器之间执行顶级通用域名的下属域名申请流程，包括：客户端向本地根服务器发送获取域名位置请求；本地根服务器接收获取域名位置请求，解析获取域名位置请求，向客户端发送通用域名位置；客户端接收通用域名位置，向通用域名集群发送域名申请请求，并接收通用域名集群发送的处理结果。由于各国的负责区域的域名变更由各国自行处理，因此保证了各国对各国自身的域名管理的自主性。
流程图中或在此以其他方式描述的任何过程或方法描述可以被理解为，表示包括一个或更多个用于实现特定逻辑功能或过程的步骤的可执行指令的代码的模块、片段或部分，并且本发明的优选实施方式的范围包括另外的实现，其中可以不按所示出或讨论的顺序，包括根据所涉及的功能按基本同时的方式或按相反的顺序，来执行功能，这应被本发明的 实施例所属技术领域的技术人员所理解。
本技术领域的普通技术人员可以理解实现上述实施例方法携带的全部或部分步骤是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，该程序在执行时，包括方法实施例的步骤之一或其组合。
以上的实施例仅是对本发明的优选实施方式进行描述，并非对本发明的范围进行限定，在不脱离本发明设计精神的前提下，本领域普通工程技术人员对本发明的技术方案做出的各种变形和改进，均应落入本发明的权利要求书确定的保护范围内。

Claims (12)

  1. 一种基于区块链的去中心化根域名服务方法，其特征在于，包括：
    设置基于区块链的去中心化根域名服务系统，所述基于区块链的去中心化根域名服务系统包括：
    N个本地子系统，每个所述本地子系统至少包括M个客户端、本地服务器集群以及一个本地根服务器；其中，所述本地服务器集群包括S个服务器，N≥1，M≥1，S≥1；
    联盟链，所述联盟链包括各个所述本地子系统中的本地根服务器；
    其中：
    任一所述本地子系统中，任一所述客户端、所述本地根服务器以及联盟链之间执行顶级域名变更流程，包括：
    所述客户端向所述本地根服务器发送域名变更请求；
    所述本地根服务器接收所述域名变更请求，向所述联盟链发送决议请求；
    所述联盟链中的各个本地根服务器接收所述决议请求，进行决议，并在决议通过后，将域名变更写入各自的区块链；
    所述本地根服务器在所述决议通过后，向所述客户端发送决议结果；
    任一所述本地子系统中，任一所述客户端、所述本地服务器集群以及所述本地根服务器之间执行域名解析流程，包括：
    所述客户端向所述本地服务器集群发送域名解析请求；
    所述本地服务器集群接收所述域名解析请求，递归解析缓存，在缓存中不存在所述域名时，向所述本地根服务器发送所述域名解析请求；
    所述本地根服务器接收所述域名解析请求，解析所述域名解析请求，在所述域名存在时，向所述本地服务器集群发送域名位置；
    所述本地服务器集群接收所述域名位置，向目标服务器集群发送解析申请，接收所述目标服务器集群解析后发送的解析结果，并向所述客户端发送所述解析结果；
    任一所述本地子系统中所述本地根服务器以及联盟链之间执行根服务器密钥变动流程，包括：
    所述本地根服务器向所述联盟链发送密钥变动请求；
    所述联盟链中的各个本地根服务器接收所述密钥变动请求，进行决议；
    所述本地根服务器在决议通过后，执行密钥变动操作，并广播所述本地根服务器变动后的公钥；
    所述联盟链中的各个本地根服务器接收所述变动后的公钥，进行记录。
  2. 根据权利要求1所述的方法，其特征在于，所述本地根服务器接收所述域名变更请求，向所述联盟链发送决议请求包括：
    所述本地根服务器接收所述域名变更请求，在设置验证合法性的流程的情况下，验证所述域名变更请求的合法性；
    所述本地根服务器在所述域名变更请求合法的情况下，向所述联盟链发送决议请求。
  3. 根据权利要求2所述的方法，其特征在于，所述本地根服务器接收所述域名变更请求之后，验证所述域名变更请求的合法性之前，还包括：
    所述本地根服务器判断所述域名变更请求的所属范围，在所述域名变更请求属于所述本地根服务器的管辖范围的情况下，执行验证所述域名变更请求的合法性的步骤。
  4. 根据权利要求1所述的方法，其特征在于，
    任一所述本地子系统中，在设置验证流程的情况下，任一所述客户端、所述本地服务器集群以及所述本地根服务器之间执行验证流程，包括：
    所述客户端向目标服务器集群发送域名验证请求；
    所述本地服务器集群接收所述目标服务器集群发送的域名所述域，向所述本地根服务器发送验证请求；
    所述本地根服务器接收所述验证请求，向所述本地服务器集群发送验证信息；
    所述本地服务器集群接收所述验证信息，对所述验证信息进行验证，并在验证通过后，向所述客户端发送验证结果。
  5. 根据权利要求4所述的方法，其特征在于，所述验证请求包括签名查询请求；
    所述本地根服务器接收所述验证请求，向所述本地服务器集群发送验证信息包括：
    所述本地根服务器接收所述签名查询请求，查询所述域名的签名，并向所述本地服务器集群发送所述签名；
    所述本地服务器集群接收所述验证信息，对所述验证信息进行验证，并在验证通过后，向所述客户端发送验证结果包括：
    所述本地服务器集群接收所述签名，验证所述签名，并在验证通过后，向所述客户端发送验证结果。
  6. 根据权利要求1所述的方法，其特征在于，
    任一所述本地子系统中，任一所述客户端以及所述本地根服务器之间执行顶级通用域名的下属域名申请流程，包括：
    所述客户端向所述本地根服务器发送获取域名位置请求；
    所述本地根服务器接收所述获取域名位置请求，解析所述获取域名位置请求，向所述客户端发送通用域名位置；
    所述客户端接收所述通用域名位置，向通用域名集群发送域名申请请求，并接收所述通用域名集群发送的处理结果。
  7. 一种基于区块链的去中心化根域名服务系统，其特征在于，包括：
    N个本地子系统，每个所述本地子系统至少包括M个客户端、本地服务器集群以及一个本地根服务器；其中，所述本地服务器集群包括S个服务器，N≥1，M≥1，S≥1；
    联盟链，所述联盟链包括各个所述本地子系统中的本地根服务器；
    其中：
    任一所述本地子系统中，任一所述客户端、所述本地根服务器以及联盟链之间执行顶级域名变更流程，其中：
    所述客户端，用于向所述本地根服务器发送域名变更请求；
    所述本地根服务器，用于接收所述域名变更请求，向所述联盟链发送决议请求；
    所述联盟链中的各个本地根服务器，用于接收所述决议请求，进行决议，并在决议通过后，将域名变更写入各自的区块链；
    所述本地根服务器，还用于在所述决议通过后，向所述客户端发送决议结果；
    任一所述本地子系统中，任一所述客户端、所述本地服务器集群以及所述本地根服务器之间执行域名解析流程，其中：
    所述客户端，用于向所述本地服务器集群发送域名解析请求；
    所述本地服务器集群，用于接收所述域名解析请求，递归解析缓存，在缓存中不存在所述域名时，向所述本地根服务器发送所述域名解析请求；
    所述本地根服务器，用于接收所述域名解析请求，解析所述域名解析请求，在所述域名存在时，向所述本地服务器集群发送域名位置；
    所述本地服务器集群，还用于接收所述域名位置，向目标服务器集群发送解析申请，接收所述目标服务器集群解析后发送的解析结果，并向所述客户端发送所述解析结果；
    任一所述本地子系统中所述本地根服务器以及联盟链之间执行根服务器密钥变动流程，其中：
    所述本地根服务器，用于向所述联盟链发送密钥变动请求；
    所述联盟链中的各个本地根服务器，用于接收所述密钥变动请求，进行决议；
    所述本地根服务器，还用于在决议通过后，执行密钥变动操作，并广播所述本地根服务器变动后的公钥；
    所述联盟链中的各个本地根服务器，还用于接收所述变动后的公钥，进行记录。
  8. 根据权利要求7所述的系统，其特征在于，所述本地根服务器通过如下方式接收所述域名变更请求，向所述联盟链发送决议请求：
    所述本地根服务器，还用于接收所述域名变更请求，在设置验证合法性的流程的情况下，验证所述域名变更请求的合法性；在所述域名变更请求合法的情况下，向所述联盟链发送决议请求。
  9. 根据权利要求8所述的系统，其特征在于，所述本地根服务器在接收所述域名变更请求之后，验证所述域名变更请求的合法性之前，还用于判断所述域名变更请求的所属范围，在所述域名变更请求属于所述本地根服务器的管辖范围的情况下，验证所述域名变更请求的合法性。
  10. 根据权利要求7所述的系统，其特征在于，
    任一所述本地子系统中，在设置验证流程的情况下，任一所述客户端、所述本地服务器集群以及所述本地根服务器之间执行验证流程，其中：
    所述客户端，用于向目标服务器集群发送域名验证请求；
    所述本地服务器集群，用于接收所述目标服务器集群发送的域名所述域，向所述本地根服务器发送验证请求；
    所述本地根服务器，用于接收所述验证请求，向所述本地服务器集群发送验证信息；
    所述本地服务器集群，还用于接收所述验证信息，对所述验证信息进行验证，并在验证通过后，向所述客户端发送验证结果。
  11. 根据权利要求10所述的系统，其特征在于，所述验证请求包括签名查询请求；
    所述本地根服务器通过如下方式接收所述验证请求，向所述本地服务器集群发送验证信息：
    所述本地根服务器，还用于接收所述签名查询请求，查询所述域名的签名，并向所述本地服务器集群发送所述签名；
    所述本地服务器集群通过如下方式接收所述验证信息，对所述验证信息进行验证，并在验证通过后，向所述客户端发送验证结果：
    所述本地服务器集群，还用于接收所述签名，验证所述签名，并在验证通过后，向所述客户端发送验证结果。
  12. 根据权利要求7所述的系统，其特征在于，
    任一所述本地子系统中，任一所述客户端以及所述本地根服务器之间执行顶级通用域名的下属域名申请流程，其中：
    所述客户端，用于向所述本地根服务器发送获取域名位置请求；
    所述本地根服务器，用于接收所述获取域名位置请求，解析所述获取域名位置请求，向所述客户端发送通用域名位置；
    所述客户端，还用于接收所述通用域名位置，向通用域名集群发送域名申请请求，并接收所述通用域名集群发送的处理结果。
PCT/CN2018/115240 2018-04-13 2018-11-13 一种基于区块链的去中心化根域名服务方法及系统 WO2019196406A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810329618.0A CN108616613B (zh) 2018-04-13 2018-04-13 一种基于区块链的去中心化根域名服务方法及系统
CN201810329618.0 2018-04-13

Publications (1)

Publication Number Publication Date
WO2019196406A1 true WO2019196406A1 (zh) 2019-10-17

Family

ID=63660079

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/115240 WO2019196406A1 (zh) 2018-04-13 2018-11-13 一种基于区块链的去中心化根域名服务方法及系统

Country Status (2)

Country Link
CN (1) CN108616613B (zh)
WO (1) WO2019196406A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108616613B (zh) * 2018-04-13 2020-05-08 北京信息科技大学 一种基于区块链的去中心化根域名服务方法及系统
CN109905388B (zh) * 2019-02-20 2021-12-07 中国互联网络信息中心 一种基于区块链的域名信用的处理方法及系统
CN111262959B (zh) * 2020-01-13 2021-05-25 平安科技（深圳）有限公司 区块链节点访问方法、装置及存储介质
CN111901432A (zh) * 2020-07-31 2020-11-06 广东尚恒智汇科技发展有限公司 一种基于区块链的安全数据交换方法
CN113873053A (zh) * 2021-09-03 2021-12-31 中国银行股份有限公司 域名变更方法及装置
CN115334088B (zh) * 2022-08-15 2024-02-27 中国联合网络通信集团有限公司 一种基于区块链的域名系统数据同步方法、装置及系统
CN115460169A (zh) * 2022-09-06 2022-12-09 中国电子信息产业集团有限公司第六研究所 域名解析方法、系统、电子设备及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106789881A (zh) * 2016-11-17 2017-05-31 中国互联网络信息中心 一种基于域名服务dns系统的区块链数字身份认证方法及系统
US20170324738A1 (en) * 2016-05-03 2017-11-09 Alcatel-Lucent Usa Inc. Internet security
CN107613041A (zh) * 2017-09-22 2018-01-19 中国互联网络信息中心 基于区块链的域名管理系统、域名管理方法和域名解析方法
CN108616613A (zh) * 2018-04-13 2018-10-02 北京信息科技大学 一种基于区块链的去中心化根域名服务方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110071986A (zh) * 2013-08-14 2019-07-30 阿里巴巴集团控股有限公司 一种用于域名解析的系统
CN106210171A (zh) * 2016-07-25 2016-12-07 宁圣金融信息服务（上海）有限公司 一种区块链域名解析系统
CN106161674A (zh) * 2016-07-25 2016-11-23 宁圣金融信息服务（上海）有限公司 一种区块链域名解析装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170324738A1 (en) * 2016-05-03 2017-11-09 Alcatel-Lucent Usa Inc. Internet security
CN106789881A (zh) * 2016-11-17 2017-05-31 中国互联网络信息中心 一种基于域名服务dns系统的区块链数字身份认证方法及系统
CN107613041A (zh) * 2017-09-22 2018-01-19 中国互联网络信息中心 基于区块链的域名管理系统、域名管理方法和域名解析方法
CN108616613A (zh) * 2018-04-13 2018-10-02 北京信息科技大学 一种基于区块链的去中心化根域名服务方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZHU, GUOKU ET AL.: "A Decentralized . . Domain Name System for the Network", CYBERSPACE SECURITY, 15 January 2017 (2017-01-15) *

Also Published As

Publication number Publication date
CN108616613B (zh) 2020-05-08
CN108616613A (zh) 2018-10-02

Similar Documents

Publication Publication Date Title
WO2019196406A1 (zh) 一种基于区块链的去中心化根域名服务方法及系统
US10178069B2 (en) Systems and methods for managing top-level domain names using consortium blockchain
US11005812B2 (en) Autonomous decentralization of centralized stateful security services with systematic tamper resistance
CN109327481B (zh) 一种基于区块链的全网统一在线认证方法及系统
US7500100B1 (en) Method and apparatus for verifying revocation status of a digital certificate
US9286369B2 (en) Data replication across enterprise boundaries
US7308502B2 (en) Method and architecture to provide client session failover
US9332008B2 (en) Time-based one time password (TOTP) for network authentication
WO2017036003A1 (zh) 一种可信网络身份管理和验证系统和方法
CN110417790B (zh) 区块链实名制排队系统及方法
US11240027B2 (en) Synchronizing radius server databases using distributed ledger network
US8555365B2 (en) Directory authentication method for policy driven web filtering
US20210160067A1 (en) Method for bidirectional authorization of blockchain-based resource public key infrastructure
US20190020648A1 (en) Systems and methods for managing device association
US20120033811A1 (en) Method and apparatus for securing network communications
US20230020504A1 (en) Localized machine learning of user behaviors in network operating system for enhanced secure services in secure data network
US11962698B2 (en) Token node locking with fingerprints authenticated by digital certificates
CN101404575B (zh) 一种更新签名算法的方法和系统
US10791119B1 (en) Methods for temporal password injection and devices thereof
US11356448B1 (en) Device and method for tracking unique device and user network access across multiple security appliances
CN110213232B (zh) 一种指纹特征和密钥双重验证方法和装置
JP2022528711A (ja) 分散台帳に関連付けられた宛先アドレッシング
CN113656101A (zh) 一种授权管理方法、系统、服务器、用户端
KR102146914B1 (ko) 블록체인 기반 IoT 기기 펌웨어 배포 시스템
CN103118025A (zh) 基于入网认证的单点登录方法、装置及认证服务器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18914394

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18914394

Country of ref document: EP

Kind code of ref document: A1