CN112468605B - Block chain-based decentralization domain name updating system and method - Google Patents

Block chain-based decentralization domain name updating system and method Download PDF

Info

Publication number
CN112468605B
CN112468605B CN201910845473.4A CN201910845473A CN112468605B CN 112468605 B CN112468605 B CN 112468605B CN 201910845473 A CN201910845473 A CN 201910845473A CN 112468605 B CN112468605 B CN 112468605B
Authority
CN
China
Prior art keywords
domain name
updated
intelligent contract
chain
sub
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.)
Active
Application number
CN201910845473.4A
Other languages
Chinese (zh)
Other versions
CN112468605A (en
Inventor
白杰
李冬云
吴先锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aowei Co ltd
Original Assignee
Aowei Co ltd
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 Aowei Co ltd filed Critical Aowei Co ltd
Priority to CN201910845473.4A priority Critical patent/CN112468605B/en
Priority to PCT/CN2020/094211 priority patent/WO2021042787A1/en
Priority to FR2008901A priority patent/FR3100675A1/en
Publication of CN112468605A publication Critical patent/CN112468605A/en
Priority to FI20215453A priority patent/FI20215453A1/en
Application granted granted Critical
Publication of CN112468605B publication Critical patent/CN112468605B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015—Name registration, generation or assignment
    • H04L61/302—Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • 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]
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • 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
    • 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
    • H04L67/104—Peer-to-peer [P2P] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Bioethics (AREA)
  • General Engineering & Computer Science (AREA)
  • Primary Health Care (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application provides a block chain-based decentralised domain name updating system and method. The system comprises a public chain and a sub-chain consisting of partial nodes in the public chain. Wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; obtaining a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node with the ownership of the target domain name intelligent contract in a sub-chain; after the domain name update request is sent to the target node, the target node decides whether to accept the domain name update request. The domain name updating system is not controlled by the ICANN any more, and the risk that domain name updating in the DNS system is possibly limited and shielded by the ICANN is avoided, so that the network security of each party participating in and providing network services can be improved.

Description

Block chain-based decentralization domain name updating system and method
Technical Field
The present disclosure relates to the field of blockchain technologies, and in particular, to a system and a method for updating a decentralised domain name based on a blockchain.
Background
A domain name is the name of a computer or group of computers on the internet consisting of a string of names separated by dots, which is used to identify the geographical location of the computer during data transmission. The domain names may be divided into different levels including root domain names, top-level domain names, and application domain names. Wherein the root domain name is the highest level domain name node, e.g., domain name "+" is the root domain name; the top-level domain name includes a national top-level domain name and an international top-level domain name, for example, the domain name ". Com." is a top-level domain name; an application domain name refers to a domain name below a top-level domain name, e.g. "abc.com." or "www.abc.com." in a domain name is an application domain name.
Domain name updating is a frequent occurrence in the internet, and as time goes by, the service provider needs may change, and accordingly, the domain name needs to be updated. In the prior art, the service provider typically performs domain name updating in a domain name system (Domain Name System, DNS) system, but the DNS system is a centralized system, which is essentially controlled by an internet name and number address assignment mechanism (The Internet Corporation for Assigned Names and Numbers, ICANN), that is, the domain name updating process is also essentially controlled by the ICANN. This unified control by an organization violates the neutral principle of the internet, and there is a risk that parties participating in and providing network services may be limited and shielded by ICANN, thereby affecting the network security of parties participating in and providing network services.
Based on this, there is a need for a system and a method for decentralizing domain name updating based on blockchain, which are used for solving the problem that in the prior art, domain name updating in a DNS system has risks of being limited and shielded by ICANN, thereby affecting network security of each party participating in and providing network services.
Disclosure of Invention
The application provides a block chain-based decentralization domain name updating system and a block chain-based decentralization domain name updating method, which can be used for solving the technical problem that in the prior art, domain name updating in a DNS system has risks of being limited and shielded by ICANN, and network security of parties participating in and providing network services is affected.
In a first aspect, embodiments of the present application provide a blockchain-based decentralised domain name updating system, the system including a public chain composed of a plurality of nodes, and a sub-chain composed of some nodes in the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner;
the nodes in the sub-chain are further configured to: acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the domain name to be updated;
the target node is configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and updating the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted.
Optionally, the subdomain name intelligent contracts include a top-level domain name intelligent contract and an application domain name intelligent contract.
Optionally, the nodes in the sub-chain are further configured to: generating a top-level domain name intelligent contract by executing the root domain name intelligent contract, and/or generating an application domain name intelligent contract by executing the top-level domain name intelligent contract.
Optionally, the root domain name intelligent contract is used for managing a top-level domain name, and the top-level domain name intelligent contract is used for managing an application domain name.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be updated, and if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract; and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the top-level domain name intelligent contract corresponding to the top-level domain name to be updated.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be updated, if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determining a target node with ownership of the top-level domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the secondary domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the application domain name intelligent contract corresponding to the to-be-updated secondary domain name.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be updated, if the domain name to be updated is a three-level domain name to be updated, determining that a target domain name intelligent contract for managing the three-level domain name to be updated is an application domain name intelligent contract, and determining a target node with ownership of the application domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the tertiary domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the domain name system BNS data corresponding to the three-level domain name to be updated.
Optionally, the target node is further configured to: and if the domain name updating request is refused, the domain name to be updated fails to be updated.
Optionally, the nodes in the sub-chain are further configured to: acquiring a domain name to be updated sent by an initiating node;
the originating node is configured to: the domain name to be updated provided by the service provider is obtained.
In a second aspect, embodiments of the present application provide a method for decentralizing domain name updating based on a blockchain, where the method is applied to the system described above, and the system includes a public chain composed of a plurality of nodes, and a sub-chain composed of some nodes in the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the following steps:
the nodes in the sub-chain acquire the domain name to be updated;
the nodes in the sub-chain determine a target domain name intelligent contract for managing the domain name to be updated, and determine target nodes in the sub-chain, which have ownership of the target domain name intelligent contract;
the node in the sub-chain sends a domain name updating request to the target node, wherein the domain name updating request comprises the domain name to be updated;
the target node checks the domain name updating request;
and the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated.
Optionally, the subdomain name intelligent contracts include a top-level domain name intelligent contract and an application domain name intelligent contract.
Optionally, the root domain name intelligent contract is used for managing a top-level domain name, and the top-level domain name intelligent contract is used for managing an application domain name.
Optionally, the node in the sub-chain determines a target domain name intelligent contract for managing the domain name to be updated, including:
if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract by the nodes in the sub-chains;
the method further comprises the steps of:
and the nodes in the sub-chains check the domain name updating request, determine whether to accept the domain name updating request according to the checking result, and update the top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be updated is a secondary domain name to be updated, the node in the sub-chain determines that the target domain name intelligent contract managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determines that the target node in the sub-chain owns ownership of the application domain name intelligent contract
The target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated, including:
and the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the application domain name intelligent contract corresponding to the to-be-updated secondary domain name.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be updated is a three-level domain name to be updated, determining that a target domain name intelligent contract for managing the three-level domain name to be updated is an application domain name intelligent contract by a node in the sub-chain, and determining that the target node in the sub-chain has the ownership of the application domain name intelligent contract;
the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated, including:
and the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the domain name system BNS data corresponding to the three-level domain name to be updated.
Optionally, the method further comprises:
and if the domain name updating request is refused, the domain name to be updated fails to be updated.
Optionally, the node in the sub-chain acquires the domain name to be updated, including;
the node in the sub-chain acquires the domain name to be updated, which is sent by the initiating node; the initiating node is used for acquiring a domain name to be updated provided by a service provider.
The embodiment of the application also provides a device with the function of realizing the block chain-based decentralization domain name updating method. The functions may be implemented by hardware executing corresponding software, and in one possible design, the apparatus comprises: a processor, transceiver, memory; the memory is used for storing computer-executable instructions, the transceiver is used for enabling the device to communicate with other communication entities, the processor is connected with the memory through the bus, and when the device runs, the processor executes the computer-executable instructions stored in the memory so that the device executes the block chain-based decentralization domain name updating method.
Embodiments of the present invention also provide a computer storage medium having stored therein a software program that, when read and executed by one or more processors, implements the blockchain-based decentralised domain name updating method described in the various possible implementations described above.
Embodiments of the present invention also provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the blockchain-based decentralised domain name updating method described in the various possible implementations described above.
According to the above technical scheme, the present application provides a block chain-based decentralised domain name updating system, comprising: a common chain composed of a plurality of nodes, and a sub-chain composed of partial nodes in the common chain. Wherein, all nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; obtaining a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; after the domain name updating request is sent to the target node, the target node checks the domain name updating request, decides whether to accept the domain name updating request according to the checking result, and updates the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted. According to the method and the system, the DNS system is deployed in the blockchain network in the form of the sub-chain, so that complete decentralization deployment can be realized. Compared with the prior DNS system, the domain name updating system provided by the application is not controlled by the ICANN any more, and the risk that the domain name updating in the DNS system is possibly limited and shielded by the ICANN is avoided, so that the network security of each party participating in and providing network services can be improved.
Drawings
FIG. 1 is a schematic diagram of a block chain based de-centralized domain name update system applicable to embodiments of the present application;
fig. 2 is a schematic flow chart of domain name updating by a domain name updating system according to an embodiment of the present application;
fig. 3 is a schematic diagram of a domain name updating flow of a top-level domain name according to an embodiment of the present application;
fig. 4 is a schematic diagram of a domain name updating flow of a secondary domain name according to an embodiment of the present application;
fig. 5 is a schematic diagram of a domain name updating flow of a three-level domain name according to an embodiment of the present application;
fig. 6 is a flow chart corresponding to a method for updating a decentralized domain name based on a blockchain according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
In the technical scheme provided by the application, the blockchain network refers to a point-to-point network with a decentralised application architecture, and the blockchain network can perform distributed storage, public consensus, digital encryption, transaction accounting and verification inside the network. I.e., blockchain networks, are transaction platforms that cover distributed technology, cryptography, P2P network architecture, and various consensus algorithms that may be applied.
In this application, the blockchain or blockchain data refers to billing information generated according to transaction information when transactions occur in a blockchain network, that is, a plurality of transactions form one blockdata, and a plurality of blockdata form one blockchain with a timestamp. The blockchain network includes nodes that establish point-to-point network connections with each other, each configured with a corresponding consensus mechanism, such as a smart contract, and with sufficient computing power to perform transaction verification and accounting procedures. The nodes also have interface specifications thereon that conform to a unified standard to enable access to more nodes or other types of blockchain networks via the interface specifications. The public chain is a point-to-point network structure formed by a plurality of nodes in the blockchain network, and each node has a distributed storage function and a transaction and accounting function; the nodes on the public chain provide unified interface specifications to the outside.
A possible system architecture to which the embodiments of the present application are applicable will be first described with reference to fig. 1.
Referring to fig. 1, a schematic diagram of a block chain-based decentralised domain name update system is shown. The system may include: a common chain composed of a plurality of nodes, and a sub-chain composed of a part of the nodes in the common chain. Obviously, in this embodiment, the nodes in the common chain may also be used as child link points at the same time. And the nodes in the sub-chain are composed of partial nodes in the common chain, so that the nodes are both the nodes in the sub-chain and the nodes in the common chain. That is, the nodes that make up the child chain have the same intelligent contracts and functions as the nodes of the public chain.
In practice, the public chain may provide basic blockchain services in the network, such as transaction, authentication, storage, etc. The public chain itself may not have any specific function corresponding to the field, but rather serves as a bridge to aggregate all sub-chains (or third party blockchain networks) accessing the public chain into the same blockchain network, so that different access chains may trade or transfer information with each other.
In the technical scheme provided by the application, the nodes in the public chain are all configured with root domain name intelligent contracts. The intelligent contract is a consensus mechanism program agreed based on blockchain transaction, and transaction operation of various functions can be realized through the intelligent contract. In the embodiment of the application, through the root domain name intelligent contract, the node can complete the domain name updating registration service by executing the root domain name intelligent contract.
The nodes in the sub-chain may be configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner. After a certain sub-link node obtains ownership of the sub-domain name intelligent contract, the sub-link node can serve as an owner of the sub-domain name intelligent contract, that is, the sub-link node is configured with the sub-domain name intelligent contract.
Since the nodes constituting the sub-chain have the same intelligent contracts as the nodes of the public chain, the nodes in the sub-chain can directly execute the root domain name intelligent contracts, thereby generating sub-domain name intelligent contracts. Wherein the subdomain name intelligence contracts include a top-level domain name intelligence contract, an application domain name intelligence contract, and domain name system (Blockchain Name System, BNS) data.
In the domain name system, domain names can be divided into root domain names, top-level domain names, and application domain names. Further, the application domain name can be further divided into a secondary domain name, a tertiary domain name, a quaternary domain name and the like. A complete domain name consists of two or more parts, each part is separated by English periods "," at the end of which is called root domain name; the right part of the penultimate "," is called the Top Level Domain (TLD), also called the primary Domain, containing a legal string, and a Domain suffix; the left part string of the top-level domain name is called the second-level domain name (Second Level Domain, SLD) until the next "; the left portion of the secondary domain name is referred to as the tertiary domain name, and so on, the domain name of each stage controls the assignment of its next-stage domain name.
In the embodiment of the application, different intelligent contracts are provided for domain names of different levels. The root domain name may correspond to a root domain name intelligence contract, which may be used to manage and maintain a top-level domain name, and to generate a top-level domain name intelligence contract; the top-level domain name may correspond to a top-level domain name intelligence contract that may be used to manage and maintain the application domain name (e.g., manage the second-level domain name), and to generate the application domain name intelligence contract; the application domain name may correspond to an application domain name intelligent contract, which may be used to manage and maintain BNS data; the BNS data can include information related to a tertiary domain name, information related to a quaternary domain name, and the like.
Further, the nodes in the sub-chain may be specifically configured to: a top-level domain name intelligent contract is generated by executing the root domain name intelligent contract.
Alternatively, the nodes in the sub-chain may in particular be further configured to: an application domain name intelligence contract is generated by executing a top-level domain name intelligence contract.
Based on the system architecture shown in fig. 1 and described above, the case of domain name updating is described in detail below.
Fig. 2 is a schematic flow chart illustrating a domain name updating system for updating a domain name according to an embodiment of the present application.
As shown in fig. 2, the nodes in the sub-chain (e.g., node 1 shown in fig. 2) may be further configured to: acquiring a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node (such as node 2 shown in fig. 2) with ownership of the target domain name intelligent contract in a sub-chain; and sending a domain name updating request to the target node. Wherein the domain name update request includes the domain name to be updated.
Accordingly, the target node may be configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and updating the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted.
According to the above technical scheme, the present application provides a block chain-based decentralised domain name updating system, comprising: a common chain composed of a plurality of nodes, and a sub-chain composed of partial nodes in the common chain. Wherein, all nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; obtaining a domain name to be updated, determining a target domain name intelligent contract for managing the domain name to be updated, and determining a target node with ownership of the target domain name intelligent contract in a sub-chain; after the domain name updating request is sent to the target node, the target node checks the domain name updating request, decides whether to accept the domain name updating request according to the checking result, and updates the intelligent contract corresponding to the domain name to be updated if the domain name updating request is accepted. According to the method and the system, the DNS system is deployed in the blockchain network in the form of the sub-chain, so that complete decentralization deployment can be realized. Compared with the prior DNS system, the domain name updating system provided by the application is not controlled by the ICANN any more, and the risk that the domain name updating in the DNS system is possibly limited and shielded by the ICANN is avoided, so that the network security of each party participating in and providing network services can be improved.
From what is shown in fig. 2, it can be seen that the transaction request received by the node in the sub-chain (i.e., node 1) originates from node 0. Node 0 may be the initiating node of the present domain name update transaction, that is, the node in the sub-chain (e.g., node 1 shown in fig. 2) may be further configured to: and acquiring the domain name to be updated, which is sent by the initiating node.
In the embodiment of the present application, the operation of updating the domain name needs to be initiated by the owner corresponding to the domain name to be updated. That is, the originating node may be configured to: the domain name to be updated provided by the service provider is obtained.
In the practical application environment, the initiating node can directly conduct transaction or information interaction with the nodes in the sub-chain, namely, the domain name to be updated can be directly sent to the nodes in the sub-chain through the initiating node. That is, the initiating node and the nodes in the sub-chain may be in the same blockchain network transaction, i.e., the initiating node is also a node in the domain name updating system.
In view of the fact that the domain name to be updated can be a domain name with different levels in the application, the target domain name intelligent contracts capable of managing the domain name to be updated are correspondingly different. The domain name updating flow of the domain name to be updated of different levels is described in detail below by way of example.
Example one:
fig. 3 is a schematic diagram of a domain name updating process of a top-level domain name according to an embodiment of the present application. The nodes in the sub-chain (e.g., node 1 shown in fig. 3) may be further configured to: acquiring a domain name to be updated, and if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract; and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the top-level domain name intelligent contract corresponding to the top-level domain name to be updated.
According to the management and managed relation between the intelligent contracts and the domain names, if the domain name to be updated is the top-level domain name to be updated, it is obvious that the target intelligent contract for managing the top-level domain name to be updated is the root intelligent contract; in the domain name updating system provided by the embodiment of the application, the nodes in the public chain are all configured with root domain name intelligent contracts, and the nodes in the sub-chain are composed of partial nodes in the public chain, that is, the nodes in the sub-chain are also configured with root domain name intelligent contracts; therefore, the target node to be determined by the node in the sub-chain is itself, and further, the node in the sub-chain may decide whether to accept the update request of the top-level domain name to be updated.
Example two:
fig. 4 is a schematic diagram of a domain name updating process of a secondary domain name according to an embodiment of the present application. The nodes in the sub-chain (e.g., node 1 shown in fig. 4) may be further configured to: acquiring a domain name to be updated, if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determining a target node (such as node 2 shown in fig. 4) having ownership of the top-level domain name intelligent contract in a sub-chain; and sending a domain name updating request to the target node. Wherein the domain name update request comprises a secondary domain name to be updated;
accordingly, the target node (e.g., node 2 shown in fig. 4) may be further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and updating the application domain name intelligent contract corresponding to the secondary domain name to be updated if the domain name updating request is accepted.
Example three:
fig. 5 is a schematic diagram of a domain name updating process of a three-level domain name according to an embodiment of the present application. The nodes in the sub-chain (e.g., node 1 shown in fig. 5) may be further configured to: acquiring a domain name to be updated, if the domain name to be updated is a three-level domain name to be updated, determining that a target domain name intelligent contract for managing the three-level domain name to be updated is an application domain name intelligent contract, and determining a target node (such as node 2 shown in fig. 5) having ownership of the application domain name intelligent contract in a sub-chain; and sending a domain name updating request to the target node. Wherein the domain name update request comprises a tertiary domain name to be updated;
the target node (node 2 as shown in fig. 5) may be further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the BNS data of the domain name system corresponding to the three-level domain name to be updated.
It should be noted that, if the domain name to be updated is a domain name of four or more levels, the domain name update may be implemented by using the method shown in fig. 5, which will not be described in detail herein.
Based on the same inventive concept, the embodiment of the application also provides a block chain-based decentralization domain name updating method. Fig. 6 is a schematic flow diagram corresponding to a method for updating a decentralised domain name based on a blockchain according to an embodiment of the present application. The method can be applied to the above-described decentralised domain name updating system, which can include a common chain composed of a plurality of nodes, and a sub-chain composed of part of the nodes in the common chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method specifically comprises the following steps:
step 101, the node in the sub-chain acquires the domain name to be updated.
Step 102, determining a target domain name intelligent contract for managing the domain name to be updated by the nodes in the sub-chain, and determining a target node having ownership of the target domain name intelligent contract in the sub-chain.
And step 103, the nodes in the sub-chain send domain name updating requests to the target node.
Wherein the domain name update request includes the domain name to be updated.
And 104, checking the domain name updating request by the target node.
Step 105, the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated.
By adopting the method, the DNS system is deployed in the blockchain network in the form of the sub-chain, so that complete decentralization deployment can be realized. Compared with the prior DNS system, the domain name updating method provided by the application is not controlled by the ICANN any more, and the risk that the domain name updating is possibly limited and shielded by the ICANN in the DNS system is avoided, so that the network security of each party participating in and providing network services can be improved.
The nodes in the sub-chain acquire the domain name to be updated;
the nodes in the sub-chain determine a target domain name intelligent contract for managing the domain name to be updated, and determine target nodes in the sub-chain, which have ownership of the target domain name intelligent contract;
the node in the sub-chain sends a domain name updating request to the target node, wherein the domain name updating request comprises the domain name to be updated;
the target node checks the domain name updating request;
and the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated.
Optionally, the subdomain name intelligent contracts include a top-level domain name intelligent contract and an application domain name intelligent contract.
Optionally, the root domain name intelligent contract is used for managing a top-level domain name, and the top-level domain name intelligent contract is used for managing an application domain name.
Optionally, the node in the sub-chain determines a target domain name intelligent contract for managing the domain name to be updated, including:
if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract by the nodes in the sub-chains;
the method further comprises the steps of:
and the nodes in the sub-chains check the domain name updating request, determine whether to accept the domain name updating request according to the checking result, and update the top-level domain name intelligent contract corresponding to the top-level domain name to be updated if the domain name updating request is accepted.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be updated is a secondary domain name to be updated, the node in the sub-chain determines that the target domain name intelligent contract managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determines that the target node in the sub-chain owns ownership of the application domain name intelligent contract
The target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated, including:
and the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the application domain name intelligent contract corresponding to the to-be-updated secondary domain name.
Optionally, the determining, by the node in the sub-chain, a target domain name intelligent contract for managing the domain name to be updated, and determining, by the node in the sub-chain, a target node having ownership of the target domain name intelligent contract, includes:
if the domain name to be updated is a three-level domain name to be updated, determining that a target domain name intelligent contract for managing the three-level domain name to be updated is an application domain name intelligent contract by a node in the sub-chain, and determining that the target node in the sub-chain has the ownership of the application domain name intelligent contract;
the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the intelligent contract corresponding to the domain name to be updated, including:
and the target node decides whether to accept the domain name updating request according to the checking result, and if so, updates the domain name system BNS data corresponding to the three-level domain name to be updated.
Optionally, the method further comprises:
and if the domain name updating request is refused, the domain name to be updated fails to be updated.
Optionally, the node in the sub-chain acquires the domain name to be updated, including;
the node in the sub-chain acquires the domain name to be updated, which is sent by the initiating node; the initiating node is used for acquiring a domain name to be updated provided by a service provider.
In an exemplary embodiment, there is also provided a computer-readable storage medium having stored therein a computer program or a smart contract that is loaded and executed by a node to implement the transaction method provided by the above embodiment. Alternatively, the above-mentioned computer readable storage medium may be a Read-Only Memory (ROM), a random-access Memory (Random Access Memory, RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, or the like.
It will be apparent to those skilled in the art that the techniques in the embodiments of the present application may be implemented in software plus the necessary general hardware platform. Based on such understanding, the technical solutions in the embodiments of the present application may be embodied in essence or what contributes to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present application.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (7)

1. A blockchain-based decentralised domain name updating system, the system comprising a public chain of a plurality of nodes, and a sub-chain of partial nodes in the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner;
the nodes in the sub-chain are further configured to: acquiring a domain name to be updated;
if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract; checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating a top-level domain name intelligent contract corresponding to the top-level domain name to be updated;
if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract, and determining a target node with ownership of the top-level domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the secondary domain name to be updated;
the target node is further configured to: checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the application domain name intelligent contract corresponding to the secondary domain name to be updated;
if the domain name to be updated is a three-level domain name to be updated, determining that a target domain name intelligent contract for managing the three-level domain name to be updated is an application domain name intelligent contract, and determining a target node with ownership of the application domain name intelligent contract in a sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the tertiary domain name to be updated;
the target node is further configured to: and checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating the domain name system BNS data corresponding to the three-level domain name to be updated.
2. The system of claim 1, wherein the sub-domain name intelligence contracts include a top-level domain name intelligence contract and an application domain name intelligence contract.
3. The system of claim 2, wherein the nodes in the sub-chain are further configured to: generating a top-level domain name intelligent contract by executing the root domain name intelligent contract, and/or generating an application domain name intelligent contract by executing the top-level domain name intelligent contract.
4. The system of claim 3, wherein the root domain name intelligence contract is for managing top-level domain names, and wherein the top-level domain name intelligence contract is for managing application domain names.
5. The system of claim 1, wherein the target node is further configured to: and if the domain name updating request is refused, the domain name to be updated fails to be updated.
6. The system of any of claims 1-5, wherein the nodes in the sub-chain are further configured to: acquiring a domain name to be updated sent by an initiating node;
the originating node is configured to: the domain name to be updated provided by the service provider is obtained.
7. A method of decentralised domain name updating based on blockchain, characterized in that it is applied to the system of any of the preceding claims 1 to 6, comprising a public chain consisting of a plurality of nodes, and a sub-chain consisting of some nodes of the public chain; wherein, the nodes in the public chain are configured with root domain name intelligent contracts; the nodes in the sub-chain are configured to: generating a subdomain name intelligent contract by executing the root domain name intelligent contract, and acquiring ownership of the subdomain name intelligent contract in a competitive manner; the method comprises the following steps:
the nodes in the sub-chain acquire the domain name to be updated;
if the domain name to be updated is a top-level domain name to be updated, determining that a target domain name intelligent contract for managing the top-level domain name to be updated is a root domain name intelligent contract by the nodes in the sub-chains; checking the domain name updating request, determining whether to accept the domain name updating request according to the checking result, and if so, updating a top-level domain name intelligent contract corresponding to the top-level domain name to be updated;
if the domain name to be updated is a secondary domain name to be updated, determining that a target domain name intelligent contract for managing the secondary domain name to be updated is a top-level domain name intelligent contract by a node in the sub-chain, and determining a target node with ownership of the top-level domain name intelligent contract in the sub-chain; sending a domain name updating request to the target node, wherein the domain name updating request comprises the secondary domain name to be updated; the target node checks the domain name updating request, decides whether to accept the domain name updating request according to the checking result, and updates the application domain name intelligent contract corresponding to the secondary domain name to be updated if the domain name updating request is accepted;
if the domain name to be updated is a three-level domain name to be updated, determining that a target domain name intelligent contract for managing the three-level domain name to be updated is an application domain name intelligent contract by a node in the sub-chain, and determining that the target node in the sub-chain has the ownership of the application domain name intelligent contract; sending a domain name updating request to the target node, wherein the domain name updating request comprises the tertiary domain name to be updated; and the target node checks the domain name updating request, decides whether to accept the domain name updating request according to the checking result, and updates the domain name system BNS data corresponding to the three-level domain name to be updated if the domain name updating request is accepted.
CN201910845473.4A 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method Active CN112468605B (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201910845473.4A CN112468605B (en) 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method
PCT/CN2020/094211 WO2021042787A1 (en) 2019-09-06 2020-06-03 Blockchain-based decentralized domain-name update system and method
FR2008901A FR3100675A1 (en) 2019-09-06 2020-09-02 Blockchain-based decentralized domain name updating system and method
FI20215453A FI20215453A1 (en) 2019-09-06 2021-03-11 Blockchain-based decentralized domain name update system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910845473.4A CN112468605B (en) 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method

Publications (2)

Publication Number Publication Date
CN112468605A CN112468605A (en) 2021-03-09
CN112468605B true CN112468605B (en) 2023-08-08

Family

ID=74806981

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910845473.4A Active CN112468605B (en) 2019-09-06 2019-09-06 Block chain-based decentralization domain name updating system and method

Country Status (4)

Country Link
CN (1) CN112468605B (en)
FI (1) FI20215453A1 (en)
FR (1) FR3100675A1 (en)
WO (1) WO2021042787A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109672755A (en) * 2019-01-24 2019-04-23 中国互联网络信息中心 A kind of domain name record update method and system based on block chain

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018191882A1 (en) * 2017-04-19 2018-10-25 北京大学深圳研究生院 Domain name resolution system based on block chain
US20200145373A1 (en) * 2017-05-22 2020-05-07 Haventec Pty Ltd System for blockchain based domain name and ip number register
CN109995888B (en) * 2018-01-02 2021-11-09 中国移动通信有限公司研究院 Data updating method and network node of block chain Domain Name System (DNS) system
JP6798087B2 (en) * 2018-11-30 2020-12-09 アドバンスド ニュー テクノロジーズ カンパニー リミテッド Blockchain smart contract updates using decentralized decisions
CN109889382B (en) * 2019-02-20 2020-07-21 中国互联网络信息中心 Domain name information maintenance system based on block chain hybrid consensus

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109672755A (en) * 2019-01-24 2019-04-23 中国互联网络信息中心 A kind of domain name record update method and system based on block chain

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"ETHREUM BASED DOMAIN NAME SYSTEM USING SMART CONTRACTS(BC-DNS)";Rodney Pinto;《sacramento state student reseach》;20190520;第1-43页 *

Also Published As

Publication number Publication date
FI20215453A1 (en) 2021-04-16
WO2021042787A1 (en) 2021-03-11
FR3100675A1 (en) 2021-03-12
CN112468605A (en) 2021-03-09

Similar Documents

Publication Publication Date Title
US11329995B2 (en) Blockchain-based system, and electronic apparatus and method in the system
CN108881187B (en) Cross-link data transmission method and device suitable for permission link scene
CN109493050B (en) Transfer method based on block chain main chain and parallel multiple sub-chains
CN112468602B (en) Block chain-based decentralised domain name registration system and method
CN109492380B (en) Equipment authentication method and device and block link point
CN109472572B (en) Contract system based on block chain main chain and parallel multiple sub-chains
CN109246211B (en) Resource uploading and resource requesting method in block chain
KR101937188B1 (en) Method for managing information using merkle tree based on blockchain, server and terminal using the same
US11388083B2 (en) Secure route identification method and apparatus
CN109493052B (en) Cross-chain contract system based on main chain and parallel multiple sub-chains
CN113259394B (en) Cross-domain user authentication method, system and equipment based on routing computation
CN112468525B (en) Domain name management system based on block chain
CN114567643B (en) Cross-blockchain data transfer method, device and related equipment
KR20190095067A (en) Method for managing information using merkle tree based on blockchain, server and terminal using the same
CN108650244A (en) A kind of domain name analytic method, terminal and recurrence dns server
CN113329081A (en) Block chain service access method, device and computer readable storage medium
WO2022256181A1 (en) Method and apparatus for utilizing off-platform-resolved data as input to code execution on a decentralized platform
CN112468605B (en) Block chain-based decentralization domain name updating system and method
CN111404885B (en) IPv6 domain name resolution method and system
US11522995B2 (en) Number management system, number management method, and number management device
CN112468603B (en) Domain name query system and method based on block chain
CN115733666A (en) Password management method and device, electronic equipment and readable storage medium
CN111756678B (en) Information verification method, device and equipment
CN112968915B (en) Processing method, processing system and processing device for DNS (Domain name Server) attack
US11665133B2 (en) Method for determining a delegation chain associated with a domain name resolution in a communication network

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
CB02 Change of applicant information
CB02 Change of applicant information

Address after: 210000 A-002, building D4, No.15 Wanshou Road, Nanjing area, China (Jiangsu) pilot Free Trade Zone, Nanjing City, Jiangsu Province

Applicant after: Jiangsu Aowei Holding Co.,Ltd.

Address before: Room 309, 3 / F, building B, No.9 Xinghuo Road, Jiangbei new district, Nanjing City, Jiangsu Province, 210000

Applicant before: Aowei information technology (Jiangsu) Co.,Ltd.

Address after: 210000 A-002, building D4, No.15 Wanshou Road, Nanjing area, China (Jiangsu) pilot Free Trade Zone, Nanjing City, Jiangsu Province

Applicant after: Aowei Co.,Ltd.

Address before: 210000 A-002, building D4, No.15 Wanshou Road, Nanjing area, China (Jiangsu) pilot Free Trade Zone, Nanjing City, Jiangsu Province

Applicant before: Jiangsu Aowei Holding Co.,Ltd.

GR01 Patent grant
GR01 Patent grant