Reverse Zones
Reverse DNS maps IP addresses to names via zones named after the reversed IP. ScaiDNS has a dedicated API that accepts CIDR input and manages PTR records by IP instead of by reversed octets.
Base path: /api/v1/reverse-zones/
Required permission: domains:* and records:* on the reverse zone
Concepts#
An IPv4 reverse zone's name is derived from reversing the octets of the network and appending .in-addr.arpa:
192.0.2.0/24→2.0.192.in-addr.arpa10.0.0.0/16→0.10.in-addr.arpa10.0.0.0/8→10.in-addr.arpa
IPv6 reverse zones use the nibble form with .ip6.arpa.
ScaiDNS hides this by accepting CIDR input directly. You give it 192.0.2.0/24, it creates 2.0.192.in-addr.arpa and lets you add PTR records keyed by IP.
Preview#
Before creating, preview what zones will be created from a CIDR:
1 2 3 4 | |
1 2 3 4 5 6 | |
1 2 3 4 5 6 7 8 9 10 11 12 | |
Response includes the zone name that would be created and the IP range it covers:
1 2 3 4 5 6 7 | |
Create from CIDR#
1 2 3 4 5 6 7 8 | |
Returns 201 with a domain record like any other. The zone is created active, with its PowerDNS zone already in place, so you can add PTR records straight away.
There is no ownership check at this step: TXT validation can't work for a reverse zone, because the challenge would have to be published inside a zone that isn't delegated to ScaiDNS yet. Create the zone first, then ask whoever holds the address block (your RIR or upstream provider) to delegate it to the ScaiDNS nameservers. PTR records start resolving publicly once that delegation is in place.
Supported prefix lengths#
IPv4:
| Prefix | Example | Zones created |
|---|---|---|
/8 |
10.0.0.0/8 |
One zone: 10.in-addr.arpa |
/16 |
10.0.0.0/16 |
One zone: 0.10.in-addr.arpa |
/24 |
192.0.2.0/24 |
One zone: 2.0.192.in-addr.arpa |
/25–/32 |
192.0.2.0/28 |
Classless (RFC 2317) — creates a zone with a hyphenated name |
IPv6:
| Prefix | Zones created |
|---|---|
/4, /8, ... /124 (multiples of 4) |
Single zone |
| Other | Not yet supported |
For subnets that don't align to octet/nibble boundaries, RFC 2317 classless delegation is used automatically — the zone name includes the prefix length.
PTR records#
PTR records live inside reverse zones. ScaiDNS lets you address them by IP rather than by reversed name.
Create a PTR#
1 2 3 4 5 6 7 8 | |
1 2 3 4 5 6 7 8 9 | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | |
ScaiDNS validates that the IP falls within the zone's CIDR, then creates the underlying PTR record.
List PTR records#
1 2 | |
Returns a list with ip, hostname, ttl, and the underlying record ID.
Delete a PTR#
1 2 | |
Delete by IP address directly — no need to look up the record ID.
Bulk create#
1 2 3 4 5 6 7 8 9 10 | |
Global reverse lookup#
Given only an IP, find the PTR and owning zone across all of your tenant's reverse zones:
1 2 | |
Response:
1 2 3 4 5 6 | |
Advanced records on reverse zones#
Reverse zones occasionally need records other than PTR — notably the zone's own NS and SOA records are managed automatically, but you may want to add extra NS (for delegation) or TXT (for documentation).
Use the standard /api/v1/domains/{domain_id}/records endpoint on the reverse zone's domain ID. The reverse zone API is a convenience layer for PTR records; the full record API works just fine.
What's next#
- Managing Records — generic record management (also works on reverse zones).
- Reverse Zones reference — endpoint details.