What is DNSSEC and Why Should You Care About It

What is DNSSEC and Why Should You Care About It

As Internet users, we’ve developed certain online habits. We get emotionally attached to certain blogs and various types of media we consume daily. Reading through our news feed first thing in the morning has become an instinct. And regardless of the way we access desired content, directly or over search engines – we expect the website we are looking for to magically appear on our screen.

Except it’s not magic.

Given the fact we operate in one single global cyberspace called the Internet, the address of each website is completely unique. Wondering who coordinates these unique addresses?

Domain Name System (DNS) works as the phone book of the Internet – it tells computers the exact location of a website we want to access and shows them where to send a request and retrieve information.

We already wrote about how domain names work, but here’s a brief reminder: People communicate through words, while computers understand only numbers. When you type in the domain name of the website you want to visit, it has to be translated into a number by a specific system. So, in order for the connection to get established – these names have to be translated to numeric equivalent, i.e. IP addresses. The system that makes this happen is called Domain Name System (DNS). It is also known as the phone book of the Internet as it tells computers the exact location of the websites (or another type of services) and shows them where to send a request and retrieve information. As you can see from this, before the website appears on your screen, your computer first has to figure out where is the website by asking DNS to translate the name into a number (a domain name into an IP address).

But let’s focus on this communication between your computer and the DNS server. It is a non-encrypted conversation where your computer sends a request for translation of the requested domain name into a number. For example www.domain.me translates into 192.124.249.153. This is how it looks like:

The IP address of the DNS server – 10.10.10.240 (all devices on the internet have an IP address) – tells your computer that the www.domain.me  web site is at the 192.124.249.153 IP address.

Of course, this is simplified. Basically, if the domain name server your computer first asks doesn’t know what is the IP address of the website www.domain.me it has to ask another domain name server, and then it stores the information for future use. We will get just a bit more technical here for clarity’s sake:

Domain names are organised in a hierarchical structure. This is how it works on the example of www.domain.me: The ROOT server (located at the public IP location) is at the top of the pyramid and it knows where the top level extension servers are, ie. it answers where .ME name server, connected to this top level extension, can be found. Alternatively, on the example of wikipedia.org – .org would be the top level domain. The .ME name server answers where domain.me name server is, and domain.me name server answers with the location of www.domain.me.

The problem with the DNS conversation is that it can get intercepted without your computer knowing where the answer is coming from – it is not able to verify who gave the answer. That’s where a layer of security steps in: Domain Name System Security Extensions (DNSSEC).

Read more: How to Setup DNSSEC

Explaining DNSSEC

In July 2008, Dan Kaminsky announced that he had discovered a fundamental flaw in the Domain Name System (DNS) protocol. He found out that a person with bad intents can set up a domain name server, listen to a DNS conversation, configure a DNS server for whatever site he or she wanted and start answering with wrong IP addresses. This is called DNS spoofing:

This means that somebody could lead you to open a site you think is regular and maybe type in your username, password, credit card number etc. And you would not even know that a site is fake.

The CERT Coordination Center together with Dan Kaminsky proposed DNSSEC as a way to bring assurance to answers provided by DNS. In July 2010 ICANN published the signed ROOT zone, making DNSSEC functional and available on ROOT DNS.

DNSSEC makes these answers authentic by digitally signing answers. Note that the responses are signed so your computer can check who is it getting the answer from. That way, you are protected and sure that the website on your screen is actually the website you wanted to open.

To find out how it really works read on!

How DNSSEC Works

DNSSEC protects you (and the internet community) by using a public key cryptography for digitally signing authoritative zone data and validating its destination.

DNSSEC is a technology developed to protect against DNS malicious attacks by digitally signing data the answer we get from the DNS is valid.

It means that, on our example, “www.domain.me” the response that comes to your computer from the root name server on the question (where is .ME name server) includes a signature key from the .ME name server, verifying it’s authoritative. So when your computer asks the .ME name server where is domain.me it can verify the answer by comparing the keys it got from the root server with the key it got from the .ME name server. The same procedure applies to the question “where is www.domain.me.” 

To ensure everything runs smoothly, the first root zone servers were signed by ICANN, the most authoritative entity on the internet, and then every top level domain (TLD) operator did the same for their own extension. .ME registry signed .ME name servers so you (as a .ME website owner) can request DNSSEC to be implemented into nameservers that handle your domain name.

Basically,  when you type a domain name or you are redirected by a search engine, your computer sends a request for translation to DNS server that accepts this request, but it also requests the DNSSEC key for authentication. Only when the key is received, compared and verified (confirmed that they are identical), your computer has an official confirmation that everything’s a-ok and the user is directed to the desired website. This validation step is crucial: if the key doesn’t match the key one level above (that is already verified), the website will not open.

Because of this extra layer of security, we can expect a decline in successful phishing attempts via DNS spoofing as with DNSSEC – users will not be redirected to malicious websites.

.ME registry signed .ME name servers so you (as a .ME website owner) can request DNSSEC to be implemented into nameservers that handle your domain name. 

Just like with any security measure, DNSSEC has to continue evolving. One of the planned changes for increased safety is the Key Signing Key Rollover. Simply put, it implies a better security practice of regularly scheduled roll of keys (changing from time to time), similar to the cautionable measure of switching your passwords from time to time.

However, ICANN has announced its plans to postpone this change of the cryptographic key, since it has identified possible issues with the resolvers who do not monitor and accept this change, which would lead them into serious problems. All the answers from the root name system would be treated as unverified, so the part of the internet they serve would stop working.

Next up? Setup DNSSEC and connect it to your domain name.

Terms and Conditions

Copyright © Domain.me, 2008-2018

doMEn d.o.o. will use the information you provide on this form to be in touch with you and to provide updates and marketing. Please let us know all the ways you would like to hear from us: Email, Direct Mail, Customized online advertising. You can change your mind at any time by clicking the unsubscribe link in the footer of any email you receive from us, or by contacting us at newsletter@domain.me. We will treat your information with respect. For more information about our privacy practices please visit our website. By clicking "subscribe", you agree that we may process your information in accordance with these terms.
We use MailChimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to MailChimp for processing. Learn more about MailChimp’s privacy practices here.

css.php
?>