The resolution of names into addresses is one of the central basic functions of the Internet. The Domain Name System solves this task as a distributed hierarchical database. Areas of responsibility are delegated to those who can provide information at first hand. Information received once can be reused and is temporarily stored locally. This leads to a very scalable and robust system. On the other hand, the delegation hierarchy ensures that only the person who is authorized to do so really provides the information.
Delegations Are Vulnerable
Unfortunately, it has emerged over the decades that these delegations and distributed queries are vulnerable. For example, a resolver pretends a wrong answer to a resolver. In this way, the name of the bank’s web server can resolve to an address that lies with the attacker, who can present a fake website and spy on account access data. No retrieval of the bank website from favorites helps against this attack. This attack is particularly bad if it is carried out against the resolver of a large ISP and then all customers of this provider are affected.
DNSSEC Protects Domains
DNSSEC offers digital signatures in the DNS protocol the possibility to ward off many attacks. With DNSSEC protected domains you can surely determine that behind several resolvers.
The information comes from the really responsible provider. The data received in the transport were not changed. Because of these advantages, DNSSEC is activated by default for all customer domains. As a service provider, it also offers remote signing of your zones. The zone data remain on your servers and can still be maintained with the tools you have introduced. Your name servers also remain responsible for your domains. Using authentication, to collect your zone data and make it available to you again signed. In spite of everything, DNSSEC still has problems that can largely be seen as solved.
