1. List the domain's existing private nameserver hosts to avoid creating a duplicate.
2. Confirm the hostname is under the owned domain and that the nameserver actually serves the intended DNS zones.
3. POST the full hostname with at least one address in ipv4 or ipv6.
4. Track the returned operation and read the resulting host record.
5. Publish matching forward DNS address records and set the intended registrar delegation through their separate workflows.

A documentation example is:

{
  "hostname": "ns1.example.com",
  "ipv4": ["192.0.2.10"],
  "ipv6": ["2001:db8::10"]
}

Replace all example values with the authorised live nameserver and its addresses.

PATCH the returned hostId and include the current row_version where available. Omitted hostname or address fields are retained. This build also accepts PUT as a compatibility alias for that PATCH behaviour; it is not a separate replace-everything contract.

The registry may protect a host still used by dependent domains. Move those delegations first and verify the replacement service before deleting the old host. Removing its ordinary A record alone does not remove the registry dependency.

After an address migration, compare parent glue and authoritative address data as well as the nameserver's actual reachability. Keep both old and new service arrangements available for the planned transition where required. A successful host operation does not prove the DNS daemon, firewall or every customer zone is ready.

• Replace a domain's authoritative nameservers through the v2 API
• Fix a private nameserver delegation that depends on missing glue
• Move a branded nameserver to a new IP without breaking its customer zones
• Follow a domain operation through pending, failed and manual-review states