Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to prevent DNS hackers from invading Dappy". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "how to prevent DNS hackers from invading Dappy".

Dappy is a decentralized distribution network for files and Web applications. Dappy uses neither a DNS system nor an e-cert authority, it performs the same work, but the service is performed by a decentralized network rather than a centralized service. One of the problems with DNS, and one of the reasons we developed Dappy, is to reduce the risk for Dafu and reduce the threat of any website today to DNS hackers and phishing. In this article, we will focus on the nature of DNS hacker intrusion and how Dappy systems prevent DNS hacker intrusion.

DNS hacking is a malicious operation designed to prevent the DNS server from working properly. All agents (browsers, operating systems, etc.) need to use DNS servers (such as those responsible for the * .fr * domain name). Most of these requests are DNS lookup requests, and all these agents want is the IP address corresponding to a given domain name (for example, * pizza.fr *). The hacker may redirect the client to his server rather than the server of the legitimate owner of * pizza.fr *. For formal enterprises or organizations, this kind of hacking can cause a lot of losses and often damage the brand image.

Instead of discussing how DNS parsing works and how hackers work, the important thing to keep in mind is that the operating system or Web browser points to a given DNS server (for example, cloudflare is 1.1.1.1. ). The server is the entry point, the ultimate source of truth for the agents that rely on it, and all DNS lookups can be addressed to this server, which propagates the request to the correct server and then replies to the client when the IP is finally known.

In order to understand how Dappy systems prevent hackers from hacking into the domain name system (or at least make it more difficult), we must introduce the Dappy name system. Dappy includes a name system on the RChain blockchain, and all purchase, renewal and resale of company-based domain names are handled by a decentralized intelligent contract platform. Of course, if there is a name, anyone can book it, so it has the property of cryptographic guarantee.

In the domain name system, a given server (or service) is responsible for extension. For example, the * .fr * domain name is handled by AFNIC (see the IANA Whois page). In Dappy, there is also an independent network of agents, but on the contrary, their responsibilities are not separated. Here is the key part, each member on the Dappy network is the common authority for name resolution, and the RChain blockchain is a replicated database, and each server should share the same state, so their responses to the same query are exactly the same. Instead of relying on a given server for name resolution (remember the above example), the client will rely on many independent agents.

Instead of executing a single query request, the clients of the Dappy system execute multiple requests; instead of asking the central computer, they ask about the computer network, which is why the Dappy paradigm is scattered and powerful. If hackers want to deceive customers, they must prevent the network from performing their work, which is much more complicated than shutting down or spoofing a single DNS server. Dappy browsers include a consensus layer that allows it to distrust any given service, so the naming system does not have a single point of failure.

Suppose a customer wants to access the resource Pizza:, the Dappy browser will send a lookup request to all individual network members (for example, 20 members). If any single response is different from the others (100% accuracy), the final configuration will treat the lookup operation as a failure. But we do want to have a room for abnormal behavior, so 80% accuracy is a good setting. Every time a customer loads a website, all Dappy network members are queried, and at least 80% of the users give the same answer to make the query successful and allow the customer to continue browsing Web. (but is it still online? )

What matters is not the numbers, but the implementation or design. The key is that the decentralized paradigm is very different from the centralized DNS. Dappy integrates and predicts some possible network failures (possibly network problems, hacker attacks, malicious behavior, etc.), which is why it must be decentralized. Dappy clients never query a single server on the Internet, but instead get some data from the RChain blockchain, they will always query multiple servers, and Dappy systems rely only on scattered, publicly visible computer networks. The only thing members have to do is to be transparent about the status of the blockchain platform, and they have no control over the platform.

Dappy mainly proposes two different types of applications, namely dapps (decentralized applications) and IP applications. This article and the naming system we just mentioned are only concerned with IP applications, while dapps is other types of applications, which we will cover in future articles.

At this point, I believe you have a deeper understanding of "how to prevent DNS hackers from invading Dappy". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.