Replace a domain's authoritative nameservers through the v2 API

1. Read the domain's current desired nameservers and confirm its public delegation.
2. Create or verify the full destination zone, including website, mail, verification and subdomain records.
3. Query every intended destination nameserver directly to confirm consistent answers.
4. Plan DNSSEC separately. An old parent DS must not remain incompatible with the new signing arrangement.
5. Obtain the domain owner's approval for the delegation change and retain the previous list for recovery.

Your credential needs domains:nameservers. Resolve the current domain identifier and use JSON with a stable idempotency key.

PUT /v2/domains/DOMAIN_ID/nameservers
Idempotency-Key: nameserver-change-local-1042
Content-Type: application/json

{
  "nameservers": ["ns1.example.net", "ns2.example.net"]
}

Replace the documentation hostnames with the complete actual list. The values are nameserver hostnames, not website URLs or IP addresses. The allowed count and registry checks depend on the TLD and provider.

Follow the returned operation to its provider result. Then inspect parent delegation and query the intended authoritative servers. The nameserver GET route returns stored desired records, so it is not by itself proof that the registry has published the change.

Keep the old DNS service functioning while cached delegation remains in use. A record's TTL and the parent delegation's cache lifetime are different values.

Do not mix unrelated old and new provider nameservers as an informal fallback unless both are intentionally configured to serve the same zone. Otherwise users can receive inconsistent website or mail answers.

Adding an NS record inside a zone is not the same as replacing the domain's registrar nameservers. Creating glue hosts is also a separate operation needed for certain private nameserver arrangements.

For a timeout, inspect the original operation before resubmission. Correct provider validation or ownership problems directly. If the destination is wrong, use a reviewed corrective change and verify its outcome; repeated blind switching can prolong inconsistent caches.

Keep the original request ID and full intended nameserver list. If an unchanged transport retry is appropriate, retain the original idempotency key. Check parent delegation independently before deciding whether a corrective update is necessary.

• Read a domain's desired nameservers through the v2 API
• Get started with the current Nabtech Domain Nexus v2 API
• Operate DNSSEC from zone signing through parent DS verification
• Point your domain to a website without disrupting business email
• Create private nameservers and the matching DNS records