Add a record
Adds one record to the zone. The record is checked here before the registrar sees any of it: a CNAME at the root or beside another record with the same name, a missing MX priority and a malformed address are each refused with a message naming the record, and nothing is sent upstream.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
id*stringapplication/json- body
name*stringThe record name. @ and the domain itself both mean the root; a bare label like www is taken as being under the domain. Stored and returned absolute and lower case
1 <= length <= 253type*stringA and AAAA point at an IPv4 or IPv6 address. CNAME points a name at another name, and cannot sit at the root or beside any other record with the same name - use ALIAS at the root. MX needs a priority and points at a mail host. TXT holds free text, SRV a service at weight port target, CAA a flag tag "value" certificate rule, NS a delegation
"A""AAAA""CNAME""MX""TXT""SRV""CAA""NS""ALIAS"content*stringWhat the record answers with, in the form its type takes
1 <= length <= 4096ttl?integerHow long resolvers may cache it, in seconds, from 60. Defaults to 3600
60 <= value <= 604800priority?integerLower is tried first. Required on MX and SRV, and refused on every other type
0 <= value <= 65535One record in the zone we host for this domain
application/json- response
One record in the zone we host for this domain
id*stringname*stringThe record name. @ and the domain itself both mean the root; a bare label like www is taken as being under the domain. Stored and returned absolute and lower case
1 <= length <= 253type*stringA and AAAA point at an IPv4 or IPv6 address. CNAME points a name at another name, and cannot sit at the root or beside any other record with the same name - use ALIAS at the root. MX needs a priority and points at a mail host. TXT holds free text, SRV a service at weight port target, CAA a flag tag "value" certificate rule, NS a delegation URL and MBOXFW are set only by forwarding (PUT /domains/{id}/forwarding, PUT /domains/{id}/email-forwarding) and read-only here
"A""AAAA""CNAME""MX""TXT""SRV""CAA""NS""ALIAS""URL""MBOXFW"content*stringWhat the record answers with, in the form its type takes
1 <= length <= 4096ttl*integerHow long resolvers may cache it, in seconds, from 60. Defaults to 3600
60 <= value <= 604800priority*|The priority, or null on a type that has none. Always there
managedBy*|Set when a forwarding feature made this record; change it from the forwarding settings instead of the generic record routes, which refuse it. Null otherwise
curl -X POST "https://example.com/v1/domains/dom_01K6XJ4Q8ZT3M9R5V2B7WDHNCA/dns/records" \ -H "Content-Type: application/json" \ -d '{ "name": "www.acme.com", "type": "A", "content": "203.0.113.10" }'{ "id": "dns_01K6XJ4Q8ZT3M9R5V2B7WDHNCA", "name": "www.acme.com", "type": "A", "content": "203.0.113.10", "ttl": 3600, "priority": null, "managedBy": null}List a zone's records GET
Every record in the zone we host for this domain, each with an id you can change or delete it by. Hosted DNS has to be on first.
Replace every record PUT
Swaps the whole record set in one call, for keeping DNS in a system of your own. At most 200 records. Every record is checked first, so one bad record leaves the zone exactly as it was. The ids are new: these are new records, not edits of the ones they replace.