Skip to main content
POST
Create a reverse DNS record

Authorizations

Authorization
string
header
required

Your API key, sent as a bearer token. Create one in the control panel under API Keys, give it only the permissions the integration needs, and copy it when it is created. It cannot be shown again. Each key is restricted to one owned team. The key determines the team for every request.

Path Parameters

server
string
required

The server UUID

Example:

"ecc6f4f1"

ipId
string
required

The ip id ID.

Example:

58213

Body

application/json

Send a JSON object containing the fields below. Required fields are marked in the schema.

ipAddress
string
required

The value of ip_address.

hostname
string
required

The fully qualified hostname.

Pattern: ^[a-zA-Z0-9]([a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(\.[a-zA-Z0-9]([a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$

Response

The record, as a JSON object. There is no envelope.

A reverse DNS record for an IP address.

id
string
required

The id ID.

Example:

"08ef3670-8639-48c9-b12c-2711c8f53674"

type
string
required

Always PTR, the record type used for reverse DNS.

Example:

"PTR"

ttl
integer
required

The value of ttl.

Example:

300

ipAddress
string
required

The value of ip_address.

Example:

"203.0.113.24"

value
string
required

The hostname the address resolves back to.

Example:

"lambda-core.blackmesa.example.com"

status
enum<string>
required

Whether the nameserver has caught up with the record yet. The record itself is in effect from the moment it is stored here, so this is progress rather than validity.

Available options:
pending,
synced,
failed
Example:

"synced"

error
string | null
required

The value of error.

Example:

null

syncedAt
string | null
required

The date and time for synced at, in UTC.

Example:

"2026-03-02T19:31:09+00:00"

dateCreated
string | null
required

The value of date_created.

Example:

"2026-03-02T19:31:05+00:00"