Reverse Zones Reference

Endpoints for IPv4 and IPv6 reverse zones and their PTR records. For the conceptual model, see Reverse Zones.

Base path: /api/v1/reverse-zones/

GET /api/v1/reverse-zones/#

List reverse zones in the current tenant.

Query parameters:

Response: Same shape as GET /api/v1/domains/, filtered to reverse_ipv4 and reverse_ipv6 types.

POST /api/v1/reverse-zones/preview#

Preview the zone that would be created from a CIDR without making changes.

Request:

1

{"cidr": "192.0.2.0/24"}

Response:

1
2
3
4
5
6
7

{
  "zone_name": "2.0.192.in-addr.arpa",
  "start_ip": "192.0.2.0",
  "end_ip": "192.0.2.255",
  "ip_count": 256,
  "domain_type": "reverse_ipv4"
}

POST /api/v1/reverse-zones/#

Create a reverse zone from a CIDR.

Request:

Response: DomainDetailResponse for the new zone (status pending_validation).

GET /api/v1/reverse-zones/{domain_id}/ptr#

List PTR records in a reverse zone.

Query parameters:

Response:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

{
  "data": [
    {
      "id": "r_abc123",
      "ip": "192.0.2.10",
      "hostname": "host-10.example.com.",
      "ttl": 3600
    }
  ],
  "total": 12,
  "page": 1,
  "page_size": 50
}

POST /api/v1/reverse-zones/{domain_id}/ptr#

Create a PTR record.

Request:

Response: Created PTR record.

POST /api/v1/reverse-zones/{domain_id}/ptr/bulk#

Create multiple PTR records atomically.

Request:

1
2
3
4
5
6

{
  "records": [
    {"ip": "192.0.2.10", "hostname": "host-10.example.com."},
    {"ip": "192.0.2.11", "hostname": "host-11.example.com."}
  ]
}

Response:

1
2
3
4
5
6

{
  "created": [...],
  "errors": [],
  "total_created": 2,
  "total_errors": 0
}

DELETE /api/v1/reverse-zones/{domain_id}/ptr/{ip}#

Delete a PTR by IP address (URL-encoded if IPv6).

Response: 204 No Content.

GET /api/v1/reverse-zones/lookup/{ip}#

Global lookup — find the PTR for an IP across all reverse zones in the tenant. Useful when you don't know which zone the IP belongs to.

Response:

1
2
3
4
5
6

{
  "ip": "192.0.2.10",
  "hostname": "host-10.example.com.",
  "zone_id": "d_abc123",
  "zone_name": "2.0.192.in-addr.arpa"
}

Returns 404 if no PTR exists for the IP.

Supported CIDR sizes#

IPv4: /8, /16, /24 produce standard in-addr.arpa zones. Prefixes /25–/32 use RFC 2317 classless delegation with hyphenated zone names.

IPv6: Prefixes that are multiples of 4 (/4, /8, ..., /124) produce standard ip6.arpa zones.

Error codes#

Related#

• Reverse Zones guide — conceptual walkthrough.
• Domains reference — generic zone endpoints (also work on reverse zones).
• Records reference — generic record endpoints for non-PTR records on reverse zones.