Use Orgo DNS, or your own nameservers
Changed on{ "mode": "orgo" } puts the domain on Orgo DNS, which serves the records in GET .../dns. { "mode": "custom", "nameservers": [...] } hands its DNS to another provider: 2 to 13 hostnames, lowercased, duplicates dropped. The records stay saved here but are not served, and every computer connected to the domain stops being reachable at it, so the switch is refused while any are (409 DOMAIN_IN_USE, with computers: their names) unless the body has "force": true.
Resolvers can take up to 48 hours to follow a nameserver change. A change the registry refuses is 502 NAMESERVERS_FAILED with its reason (a locked domain, for example). Needs write access, with a session, an account-wide key or a key for this workspace. Counts against the 60 DNS changes an hour.
Request
- Base URLhttps://www.orgo.ai
- AuthHTTP bearer
Path parameters
Workspace id.
A domain bought through Orgo: its id in GET /api/projects/{id}/domains.
Request body
Response
{ nameservers, serving }
Example response
{
"nameservers": {
"mode": "custom",
"list": [
"ada.ns.cloudflare.com",
"bob.ns.cloudflare.com"
]
}
}Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info
- info
endpoint added
- info