Typically, a DNS zone represents an entire domain and contains one or more A, AAAA, and/or CNAME records for each subdomain. In some cases, you might need to delegate responsibility for a segment of the DNS namespace to someone else — for example, if a segment of a domain (e.g., help.ns1.com) is managed by a different DNS provider than the rest of the domain (e.g., ns1.com). In this case, you can create a separate zone file for the subdomain and update the nameserver (NS) records within the parent zone to point to the subdomain’s nameserver(s).
You can configure DNSSEC online signing for a parent zone and a subdelegation (sometimes referred to as a child zone) by enabling DNSSEC on both zones, adding a DS record to the parent zone containing the child zone’s DNSSEC data, and then adding the DNSSEC details for the parent zone to the domain registrar.
Note
You can enable DNSSEC online signing on any primary (non-secondary) zones, including subdelegations and child zones.
Warning
NS1 recommends testing the configuration below on a designated "test zone" before configuring on production zones. Note that when following the process below, there will be a period of time during which incoming queries to the subdelegated/child zone records will receive an NXDOMAIN response. This occurs after you enable DNSSEC on the subdelegated/child zone until you add the DS record to the parent zone.
Note
The instructions below assume both the parent and child zones are hosted on the NS1 platform. If the parent or subdelegated/child zone is hosted by another DNS provider, then instructions will vary.
If you haven’t already done so, create the parent zone representing your overarching domain and a child zone or subdelegation representing a segment of that domain. Often, these zones are hosted by two different DNS providers so the specific instructions may vary.
-
Create the parent zone. This must be a primary (or non-secondary) zone. Refer to Create a DNS zone for instructions.
-
Create the subdelegation or child zone. Refer to Subdelegations and child zones for details.
-
If you haven't already, add a new NS record to the parent zone matching the NS record found in the subdelegated/child zone.
Warning
Do not remove any existing NS records in the parent zone.
Refer to Enabling DNSSEC for a primary (or non-secondary) zone for instructions. If the parent zone is not hosted by NS1, refer to the respective provider’s instructions for enabling DNSSEC.
Zones with DNSSEC online signing appear in the zone list with the shield icon.

Warning
Once you enable DNSSEC on the parent zone, you must update the domain registrar with the DNSSEC-related data provided by NS1 — including the key tag, algorithm, flags, digest, digest type, and public key.
Follow the instructions below to enable DNSSEC online signing for the child zone hosted on the NS1 platform. Note that these instructions are nearly identical to the instructions for updating a primary zone, except that, in the final step, you will apply the DNSSEC data for the subdelegation to the parent zone instead of updating the domain registrar.
Note
If the subdelegation or child zone is not hosted by NS1, refer to the provider’s instructions for enabling DNSSEC.
-
In the NS1 portal, navigate to the list of zones and click the name of the child zone to drill down into zone details.
-
Navigate to the Zone settings tab.
-
Scroll to the bottom of the page to the DNSSEC section, and then select the checkbox next to Enable DNSSEC.
-
Click Save changes.
-
A new button appears beneath the "Enable DNSSEC" option. Click View Detailed Instructions.
-
Record the DNSSEC details shown, including the key tag, algorithm, digest type, digest, flags, and public key.
You will populate the DS record in the parent zone with these details in the next step.
-
Click Done.
Unlike the parent zone, the subdelegated/child zone delegation information is not transferred to the registrar. Instead, this information is copied to the parent zone within a DS record (see next step), which is then propagated to all systems.
Once enabled, the NS1 platform autogenerates a DNSKEY record within the subdelegated or child zone.

Warning
DNSSEC-enabled resolvers will not validate the responses until the DS record is configured.
Next, you must establish a DNSSEC trust between the parent and child zone by creating a DS record within the parent zone that contains the DNSSEC-related data for the child zone.
-
Navigate to the list of zones, and click the name of the parent zone (e.g., domain.edu) to drill down into zone details.
-
Click the + (add) button to create a new record. The Add Record window appears.
-
Under Record type, select DS from the list.
-
In the name field, enter the subdomain prefix corresponding to the subdelegated/child zone (e.g., sub.domain.edu).
-
Under Answers, complete each form field with the subdelegated/child zone's DNSSEC configuration details (recorded in Step 3), including the key tag, algorithm, digest type, and digest data.
-
Click Save record.
Once the updates propagate, validate the configuration using a public DNSSEC authentication tool, such as https://dnssec-debugger.verisignlabs.com/. If the configuration is successful, an array of green check marks will appear, indicating no errors.