IBM NS1 Connect signs a primary zone with one setting, using algorithm 13 only, and shows the DS — or the key — for the registrar. Keys are not rotated automatically.
| What it is | DNS host |
| DNSSEC | Yes |
| Signing | One setting per primary zone |
| Algorithm | ECDSAP256SHA256 (13) only |
| DS record | No — add it at the registrar |
Is DNSSEC working for your domain?
Enter a domain: we read the DS record at its registry and the keys its nameservers publish, check that they match and the signatures are current, and ask a validating resolver.
Turning it on at IBM NS1 Connect
- DNS, Zones, the zone, Zone settings, the DNSSEC box.
- Wait the SOA minimum TTL, then take the values from View detailed instructions — key tag, algorithm, digest type and digest, or the flags and public key — to the registrar.
Worth knowing
Keys are not rotated automatically: support rolls the zone-signing key; rolling the key-signing key needs you and support together.
Common mistakes
- Turning DNSSEC off in the zone after the DS has been published: validation fails.
Whose nameservers a domain uses: IBM NS1 Connect’s.
Sources
Checked on 27 September 2026 against these official sources:
- Enabling DNSSEC on a primary zone — ibm.com
- DNSSEC FAQ — ibm.com
- Setting up multi-signer DNSSEC in NS1 Connect (API only) — ibm.com