Successful request

Failed requests

Besides the generic errors these specific error responses can be expected.

Many different scenarios for changes to DNS settings exist, below are general rules to follow and examples for common scenarios.

General rules for managed zones

Zone provisioning

The way the records are provisioned can be changed both via update domain and update zone, some examples for update domain

{
      "zone": {
        "link": false
      }
}

{
      "zone": {
        "template": "example"
      }
}

{
      "zone": {
        "master": "1.2.3.4"
      }
}

{
      "zone": {
        "master": ""
      }
}

Change service

It is possible to change DNS service, migrating the existing records to the new service. If the zone currently has a master only the records and a optional link with a template are migrated, the master synchronisation is not. The zone at the old service is marked for deletion in 7 days.

A zone of the target service must not yet exist, otherwise the existing zone is adopted.

{
      "zone": {
        "service": "BASIC"
      }
}

Vanity name servers

To avoid deletion of a zone, always specify the zone field when changing vanity name servers.

For details on how to setup correct resolution of vanity name server see our Knowledge Base

{
      "ns": ["ns1.yourname.com", "ns2.yourname.com"],
      "zone": {
        "service": "PREMIUM",
        "template: "example"
      }
}

{
      "ns": ["ns1.yourname.com", "ns2.yourname.com"],
      "zone": {}
}

Zone deletion

{
      "ns": ["ns1.other.com", "ns2.other.com"]
}

{
      "ns": []
}

Zone adoption

Adoption of zones cannot be combined with changes to the zone, the service must be specified to adopt other a zone other than BASIC. Other zone field must be omitted or equal to the current zone.

If the current zone is pending deletion it can be reinstated and adopted by, if however a template or master is specified a new zone will be created instead and the pending deletion zone is removed immediately.

{
      "zone": {}
}

Decouple zone

After decoupling, both the zone and domain remain unchanged, however any future changes to the zone or domain that are interdependent are not synchronised automatically anymore. e.g. dnssec changes, vanity name server changes, key rollover, zone cleanup after domain deletion.

This is not supported on BASIC zones since those are only ever active in DNS when in a managed state.

This can be useful if you want to transfer the domain but keep the zone active.

{
      "zone": {
        "managed": false
      }
}