Last time we — we recalled how the project began and what problems it was supposed to solve in the ARPANET network. Today, we will talk about the first DNS server, BIND.
Photo - — CC BY-SA
The First DNS Servers
After Paul Mockapetris and Jon Postel proposed the concept of The system developed by the university students automatically converted DNS names to IP addresses and vice versa. Interestingly, when its code was uploaded to
BSD DEC The BIND server includes several libraries and components that implement the client-server architecture of DNS and manage the configuration of the DNS server's functions. BIND is widely used, especially on Linux, and remains a popular implementation of a DNS server. It is
installed on servers supporting the root zone. .
There are alternatives to BIND. For example, PowerDNS, included with Linux distributions. It was developed by Bert Hubert from the Dutch company PowerDNS.COM and is supported by the open source community. PowerDNS was implemented on the servers of the Wikimedia Foundation in 2005. This solution is also used by major cloud providers, European telecommunications companies, and organizations in the Fortune 500 list.
BIND and PowerDNS are among the most widely used, but they are not the only DNS servers. It is also worth mentioning , and .
Development of the Domain Name System
Throughout the history of DNS, its specification has undergone numerous changes. One of the first major updates was the NOTIFY and IXFR mechanisms in 1996. They simplified the replication of domain database systems between primary and secondary servers. This new solution allowed for configuring notifications about changes in DNS records. Such an approach guaranteed the identity of the secondary and primary DNS zones and saved bandwidth — synchronization occurred only when necessary, rather than at fixed intervals.

Photo - — CC BY-SA
Initially, the DNS network was not accessible to the general public, and potential security issues were not a priority during the system's development; however, this approach had repercussions later. With the growth of the internet, vulnerabilities in the system began to be exploited — for example, attacks such as DNS spoofing emerged. In this case, the cache of DNS servers is filled with data that lacks an authoritative source and redirects requests to malicious servers.
To address the issue, DNS cryptographic signatures for DNS responses (DNSSEC) — a mechanism that allows for building a chain of trust for a domain from the root zone. Note that a similar mechanism was added for host authentication when transferring DNS zones — it was named TSIG.
Modifications that simplify DNS database replication and address security issues were warmly welcomed by the IT community. However, there were also changes that were not well received by the community. In particular, the transition from free to paid domain names. This is just one example of the 'wars' in the history of DNS. We will discuss this further in the next article.
At 1cloud, we offer the service “” which allows you to rent and configure a remote VDS/VPS server in just a few minutes.
There are also for all users. Post referral links to our service and earn rewards for referred clients.
Source: habr.com
