Delegating a domain to NS1 Connect

To complete zone configuration and initiate traffic flow through IBM® NS1 Connect®, you must update the nameserver delegation for your domains to point to NS1 Connect's authoritative nameservers assigned to the zone. For more information about nameserver assignments, see Nameserver assignments. Depending on the type of zone and your configuration, you need to update the delegation at the domain registrar, primary DNS provider, or parent zone.

After configuring a zone and its records, complete the following instructions to update the nameserver delegation for the corresponding domain.
Attention: Do not update the registrar until you are ready to send DNS traffic to the new nameservers. If you are undergoing a large migration to the NS1 Connect platform or between NS1 Connect services, adhere to the guidance provided by the IBM support before updating the registrar.
  1. Locate and record the NS1 Connect nameservers listed as answers within the zone's nameserver (NS) record. Refer to Locating assigned nameservers.
  2. Depending on the type of zone and your configuration, update the nameserver delegation at the domain registrar, primary zone, or parent zone.
    • For primary zones — as in, NS1 Connect is the primary DNS provider for the domain — update the nameservers (NS record) at the domain registrar. Refer to the documentation provided by your registrar for instructions.
    • For secondary zones, update the NS record within the primary zone to include (not replace) NS1 Connect nameservers. Refer to Configuring NS1 Connect as a secondary DNS provider.
    • For parent and child zones or sub-delegations, refer to Subdelegations and child zones for instructions on where to update the delegation depending on the details of your configuration.

You should update the nameserver delegation at the domain registrar to non-NS1 nameservers immediately to move traffic away from NS1 nameservers and prevent lame delegation hijacking.