DNSSEC at netcup: the status
netcup runs two DNS systems. Existing domains have the “DNS” tab in the Customer Control Panel (CCP), domains on CloudDNS have separate tabs for CloudDNS, DNSSEC and name servers; netcup is moving new registrations to CloudDNS step by step and migrating existing domains gradually. Where the switch is therefore depends on the domain.
On the netcup name servers netcup signs the zone itself and publishes the key data at the registry. For an existing domain that is the “DNSSEC Status” checkbox, which like any other change only applies after “Save DNS Records”.
If the domain uses your own name servers, you enter the keys yourself: public key, flags and algorithm, in other words the DNS provider’s DNSKEY data. According to the help, netcup does not support DS entries there. The zone must already be signed at the external provider, and how many keys and which algorithms are possible depends on the extension.
How to enable DNSSEC at netcup
The way through the netcup control panel:
- In the CCP open “Domains” and click the magnifier icon next to the domain.
- Existing domain: tick “DNSSEC Status” on the “DNS” tab and apply it with “Save DNS Records”.
- Domain on CloudDNS: switch to the “DNSSEC” tab and click “Activate DNSSEC”.
- With your own name servers: use “+ New DNSSEC Entry” (CloudDNS: “DNSSEC” tab, “Add”) to enter the DNS provider’s public key, flags and algorithm, then save.
- Use the checker to verify that the DS record and signatures are publicly visible.
Click path at netcup
Path for existing domains; for domains on CloudDNS: “DNSSEC” tab, then “Activate DNSSEC”.
Official guide from netcup: DNSSEC (Existing Domains)(opens in a new tab)
The order when changing providers
DNSSEC does not forgive a wrong order. The DS record at the registry points to the key of the zone; if the two do not match, validating resolvers answer with SERVFAIL and the domain is unreachable for many users, website and mail included.
- Before changing name servers switch off DNSSEC or remove the DS record.
- Wait until the TTL of the DS record has expired, usually one to two days.
- Only then change the name servers and sign again at the new provider.
Verify and keep an eye on it
The DNSSEC checker below follows the chain from the registry to the zone: DS record, DNSKEY and signatures. You see right away whether DNSSEC is fully set up for a domain at netcup or whether an orphaned DS record puts the domain at risk. DomainWarn keeps checking this afterwards and alerts you when the chain breaks or signatures expire.