| Note: Some TLDs, such as Dot.BS , are not currently supported for DNSSec management. |
What is DNSSEC and how do I use it?
Domain Name System Security Extensions (DNSSEC) protect against forged or manipulated DNS data, such as DNS spoofing or cache poisoning. It ensures that the DNS records your visitors receive are identical to the authentic records published on your authoritative DNS server.
How does DNSSEC work?
DNSSEC digitally signs DNS records using public-key cryptography:
- The correct DNSKEY record is authenticated through a chain of trust, starting from verified public keys at the DNS root zone.
- A validating DNS resolver checks the digital signature to confirm the information is identical (unmodified and complete) to what the domain owner published.
- DNSSEC protects all records within the zone, including A, AAAA, MX, TXT and CNAME records.
How to set up DNSSEC at Internic
Internic acts as your domain registrar, submitting Delegation Signer (DS) records directly to top-level registries, such as CIRA for .CA or Verisign for .COM.
Option 1: Using an external DNS provider
If you manage your DNS through a third-party host (for example Cloudflare, Route 53, or an enterprise DNS provider):
- Enable DNSSEC at your DNS provider to sign your zone and generate your DS records.
- Copy the four DS parameters provided by your DNS host.
- Email the parameters to Internic Support at service@internic.ca, following the authorization steps below.
Option 2: Using Plesk hosting DNS
Plesk lets you manage and sign DNSSEC records directly in your hosting control panel. Follow Plesk's DNSSEC Management Guide to generate your DS keys, then email the parameters to Internic Support to complete the registry delegation.
Required parameters
To request DNSSEC activation, email service@internic.ca with:
Domain Name: [yourdomain.tld] Key Tag: [e.g., 2371] DNSKEY Algorithm: [e.g., 13 (ECDSA Curve P-256 with SHA-256)] Digest Type: [e.g., 2 (SHA-256)] Key Digest: [e.g., 4B2A... full hex string]
Who can request DNSSEC changes?
DNSSEC changes, whether adding, updating or removing DS records, are made at the registry level and affect whether your domain resolves at all. For your protection, only the Internic account holder can authorize them.
Account holder vs. domain contacts
It's common to be listed on a domain without being the account holder. Here's the difference:
| Role | What it means | Can authorize DNSSEC changes? |
|---|---|---|
| Account holder | The person or organization that owns the Internic account, identified by the primary and alternate email addresses on the account. They can sign in and manage the domain. | Yes |
| Registrant, administrative or technical contact | People listed on the domain so the registry and Internic can reach them about the domain. These are points of contact, not account access. | No, unless authorized by the account holder |
For example, if you're the IT provider or web developer listed as the technical contact, you'll need the account holder to authorize the request, even though the change is technical.
Internic doesn't currently offer delegated access, such as sub-users or "team member" logins. So the account holder's email address is how we confirm a request is genuinely authorized.
How to authorize a request (either option works)
-
The account holder sends the request. The request comes from the primary or alternate email address on the Internic account.
- CC the account holder. The technical contact or IT provider sends the request and CCs the primary or alternate email address on the account. The account holder then replies to confirm, for example: "I authorize this DNSSEC change for [domain]." We'll process the request as soon as their confirmation arrives.
If the account holder would like you to handle future DNSSEC requests, they can say so in their confirmation. We'll note it on the account, but each change still needs a reply from the account holder's email.
Why we require this
Removing or changing DS records can make a domain stop resolving, or can disable the security protecting it. If we accepted requests from any contact listed on a domain, anyone who managed to get listed as a contact could take a domain offline or weaken its security. Requiring the account holder's authorization protects your domain, your website and your email.
If the account holder no longer has access to the account emails
Contact our support team. We'll walk you through our account verification process to confirm ownership and update the account details before any changes are made.
Important: changing DNS providers
If DNSSEC is enabled and you change DNS providers, or your DNS provider account is closed or deleted, your domain will likely stop resolving. The DS record at the registry still points to your old provider's keys, so validating resolvers will reject your domain.
To avoid downtime:
- Before switching DNS providers, ask us to disable DNSSEC (remove the DS record).
- Wait for the removal to propagate (1 to 5 hours).
- Switch your nameservers to the new provider.
- Once DNS is working at the new provider, enable DNSSEC there and send us the new DS parameters.
If your domain has already stopped resolving because of a DNSSEC mismatch, contact us right away, with the account holder's email address included or CC'd, so we can remove the DS record as quickly as possible.
Turnaround and propagation
-
Submission: once authorized, adding or removing DS records at the registry typically takes under 5 minutes for our domain specialists.
-
Propagation: global DNSSEC propagation for validating resolvers takes 1 to 5 hours after the registry update.
- Removal or rollback: to disable DNSSEC, send an authorized removal request (see "How to authorize a request"). Removing the DS record takes under 5 minutes on our end, with full removal propagating globally within 1 to 5 hours.
Frequently asked questions
I'm listed as the technical contact. Why can't I request this change?
Domain contacts are points of contact for the domain, so the registry and Internic can reach the right people. Being a contact doesn't give access to the account or authority to change it. Only the account holder, identified by the primary or alternate email on the account, can authorize DNSSEC changes. The quickest solution is to CC them on your request.
It's urgent and my domain is down. Can you make an exception?
We understand how urgent a DNS outage is, and we'll act right away once authorization is received. To speed things up, contact the account holder directly and ask them to reply from the account email, or include them in CC from the start.
I don't know which email address is on the account.
For security, we can't share the account's email addresses. Please check with the account holder, the person or organization who owns the domain. If they no longer have access, contact us about our account verification process.
Can the account holder give me permanent access?
Internic doesn't currently offer delegated logins. The account holder can tell us in writing that you're authorized to handle requests for their domain, and we'll note it, but each change still needs to be confirmed from the account holder's email.
Request templates
Enable DNSSEC (from or CC'ing the account holder):
Subject: DNSSEC activation request – [yourdomain.tld] Please enable DNSSEC for the following domain: Domain Name: [yourdomain.tld] Key Tag: [ ] DNSKEY Algorithm: [ ] Digest Type: [ ] Key Digest: [ ] Authorized by: [Account holder name] – [primary/alternate email on file]
Disable DNSSEC (from or CC'ing the account holder):
Subject: DNSSEC removal request – [yourdomain.tld] Please disable DNSSEC (remove all DS records) for [yourdomain.tld]. Authorized by: [Account holder name] – [primary/alternate email on file]
If you have any questions about DNSSEC or authorizing a request, please contact our support team at service@internic.ca.
| Note: It can take up to 48 hours for your application to be processed. Additional time may be required for DNS propagation as well, though this timeframe varies depending on the company. |
Comments
0 comments
Please sign in to leave a comment.