DNSSEC (2024)

DNSSECis a set of security extensions to DNS that provides the means for authenticating DNS records. It allows to prevent malicious activities like cache poisoning, phishing, and other attacks.

The purpose of DNSSEC is to protect Internet clients from counterfeit DNS data by verifying digital signatures embedded in the data.

How it works

DNSSEC creates a specific record with a digital signature for every resource record. The key peculiarity of a digital signature is the use of public key cryptography to ensure that DNS records are authentic. Every member of the system can check the signature, however only those having the secret key can sign new or modified data.

Public keys are published as a DNSKEY resource record along with other resource records. A sequence of records that identifies public keys is called a chain of trust. The key authenticity is checked with its digests (fingerprint, hashes) that are sent to the parent zone as DS-records. Digests of the parent zone public keys are also sent to the corresponding parent zones. The chain of trust is built up to the root zone which public key and digests are published in the official documents of ICANN.

DNSSEC uses 2 types of keys:

• ZSK (Zone Signing Key)— this key is used to sign records within the zone;
• KSK (Key Signing Key)— this key is used to sign keys.

We recommend that you set larger values of the key length and update period for KSK than ZSK.A ZSK-key is used every time the domain zone is modified or updated. Using a short key makes it easier to sing a domain, and a short update period ensures a high level of security.KSK-keys are used only to sign the keys, that's why they are used not so often as ZSK. A long key does not affect the efficiency. Besides, it is safe to specify a long update period for a long key. A long update period of KSK-keys allows sending DS-records to the parent zone more rarely.

To avoid DNSSEC key compromising, the keys are updated. Thekeys are updated in steps so that slave servers and DNS caching servers have enough time for synchronization with the primary DNS server.

KSK-key update algorithm:

1. DS-records of a new KSK-key is published in the parent zone.In ISPmanager the next KSK-key is created right after the domain is signed or the old KSK-key is removed. A user may publish the DS-record of the new key beforehand. To update the KSK-key correctly in ISPmanager, you need to publish the DS-record of the new key in the parent zone one month before the KSK-key is updated;
2. Changing the KSK-key.The active KSK-key is changed into a new one. In ISPmanager the key is changed 2 weeks before the KSK-key is updated;
3. Removing DS-records of the old key from the parent zone.ISPmanager generates a new key allowing users to perform the required operations in the parent zone: delete the DS-record of the old key and add the DS-records of a new key.

ZSK-key update algorithm:

1. Creating and publishing a new ZSK-key in the domain zone.This operation is performed in ISPmanager 2 weeks before the key is changed. A new key is not used for signing the domain;
2. Changing the ZSK-key.A newly published ZSK-key is get activated. The old ZSK-key is no longer used for signing domains;
3. Deleting the old passive ZSK-key.This operation is performed 2 weeks after the ZSK-key was changed.

Enabling DNSSEC

DNSSEC can be activated for the following DNS-servers:

• Bindstarting from version 9.8.4;
• PowerDNSstarting from version 3.2.

To enable DNSSEC and configure the domain key settings, navigate to Settings→ Global settings. For more information please refer to the articleGlobal settings.

Email notifications

When activating DNSSEC protection you need to publish and update the DS-record in the parent zone manually. DNSSEC email notifications will inform you about new DS-records you need to publish.

Navigate toSettings→Email notifications→ selectDNSSEC notifications checkbox

Enabling DNSSEC

DNSSEC activation involves several steps:

1. the system checks the maximum TTL in the domain zone;
2. signs the domain zone;
3. generates a chain of trust.

DNSSEC activation involves several steps:

• the system checks the maximum TTL in the domain zone;
• signs the domain zone;
• generates a chain of trust.

Checking the maximum DNS TTL

The maximum DNS TTL must be less than 2 weeks. The default value is 3 hours.

To set the maximum TTL, navigate toDomains→Domain names→select a domain→clickRecords→TTL, sec.The default value is 1 hour (3600 sec).

Signing domain zone

To sign a domain zone, go toDomains→Domain names→select a domain→clickEdit →Sign domain.The system will start a background process to sign the domain zone. KSK and ZSK will be generated according to the specified parameters. When signing the domain zone, you will see the icon in theStatuscolumn. You cannotEditorDeletethe domains during that process.

Once the system signs the domain zoneyou will see the notification icon in theStatuscolumn.The"Unpublished DS-records"banner in the panel interface and theDNSSECbutton will become active for the domain.

The domain zone signing function is available only to "Users" and "Administrators".

Creating a chain of trust

To create a chain of trust, you need to transfer DS-records (or even DNSKEY-records KSK, depending on a registrar) into the parent zone. You can see the information about the main key parameters and their DNSKEY and DS records inDomains→Domain names→select a domain →DNSSEC.

The following data are displayed for every DS-record:

• Start of record— beginning of the DS-record;
• Tag— KSK-key identifier;
• Algorithm— encryption digest identifier;
• Digest type— digest type identifier;
• Digest— digest content.

Show DNSKEY— click the button to see a table with DNSKEY-records. The following data are shown for every record DNSKEY-record:

• Start of record— beginning of the DNSKEY-record;
• Flags— key type identifier;
• Protocol— DNSSEC protocol number;
• Algorithm— encryption algorithm identifier;
• Public key— public part of the key;
• Tag— KSK-key identifier.

DS-records are sent in one of the following ways:

1. Add records in the domain control panel interface on a registrar side. You need to copy the DS-records from ISPmanager. If records should be added in the form of strings on the registrar side, you need to group the values of all columns of the DS-record table in ISPmanager. Do not forget to add spaces between them.
2. If the domain zone is located along with the parent zone on the same sever managed by ISPmanager or DNSmanager, on theDNSSEC parameterspage, you will see theSend DS-records to the parent zonebutton. Click the button to pass the DS-records.
3. If the domain is the parent for the domain on the remote server, create the DS-records of the child domain:Domain names → Records → Add. Learn more inDomain resource record.

Once in 24 hours, DNSmanager checks DS-records in the parent zone. At least one DS-record for every KSK must be sent. Once completed, the warning in theStatuscolumn will change into the icon confirming that the domain is protected with DNSSEC.

Disabling DNSSEC protection for a domain

If the keys are compromised, you need to sign the domain zone with new keys. To do so, disable DNSSEC protection:

1. Delete all the DS-records from the parent domain zone and wait for several hours;
2. Delete the domain signature inDomains→Domain names→select a domain→Edit→select theDelete recordcheckbox.

Only "Users" and "Administrators" can disable the protection.

Disabling DNSSEC support

To disable DNSSEC navigate to Settings → Global settings.checkbox.Learn more in the articleGlobal settings.

Once completed, the system will un-sign all the domain names and delete their keys.