Set Reverse DNS (PTR) for Your IPs: Portal and API

Method 1: In the portal

1. Log in at amoni.app.
2. In the left-hand menu, open IP Addresses. Every address on your account is listed, grouped by the server or cloud instance that holds it. Groups are collapsed; click a server name to expand it, or use Expand all at the top right.
3. Find the address. The search box filters live on IP, hostname or current rDNS, and the IPv4 / IPv6 pills narrow the list.
4. Hover the rDNS / PTR cell on that row and click the pencil icon that appears.
5. Type the hostname (for example mail.example.com) and press Enter, or click the green tick. Esc cancels.
6. A green rDNS updated confirmation appears and the row shows the new value.

To clear a PTR, open the editor, delete the value and save. New addresses may start with a default PTR (such as ip4-203-0-113-10.rdns.netrouting.net); replace it whenever you like.

Every change is recorded on the Activity page as “Set reverse DNS for 203.0.113.10 to mail.example.com”, with who did it and when.

Method 2: With the API

The same two calls power the portal page. You need an API key with the IPs scope (ips.write): create one under Account → API Keys, tick IPs, and copy the key when it appears. It is shown once. Full reference: api.amoni.app/v1/docs.

1. Find the address id

curl -s https://api.amoni.app/v1/ips \
  -H "Authorization: Bearer nr_live_..."

Addresses come grouped by the resource holding them. Note the numeric id of the one you want:

{
  "success": true,
  "data": {
    "servers": [
      {
        "id": "srv-1042",
        "type": "server",
        "name": "web1.example.com",
        "location": "Amsterdam",
        "ips": [
          {
            "id": 4821,
            "address": "203.0.113.10",
            "ip_version": 4,
            "dns_name": "ip4-203-0-113-10.rdns.netrouting.net",
            "is_primary": true,
            "prefix_length": 29
          }
        ]
      }
    ],
    "total_ips": 1,
    "total_servers": 1
  }
}

To pick it out in a script with jq:

curl -s https://api.amoni.app/v1/ips -H "Authorization: Bearer nr_live_..." \
  | jq '.data.servers[].ips[] | select(.address == "203.0.113.10") | .id'

2. Set the PTR

curl -s -X PUT https://api.amoni.app/v1/ips/4821/rdns \
  -H "Authorization: Bearer nr_live_..." \
  -H "Content-Type: application/json" \
  -d '{"dns_name": "mail.example.com"}'

{ "success": true, "data": { "message": "Reverse DNS updated." } }

The write lands on our authoritative nameservers before the response returns. To clear the PTR, send an empty string: {"dns_name": ""}.

What the API will tell you

Branch on the HTTP status and on code. The error text is written for people and may be reworded.

About 422s: a rule the endpoint checks itself (a weak password, a duplicate key, a layout you may not use) answers in the usual envelope. A field that fails basic validation currently answers in the framework's own shape, {"message": "…", "errors": {"field": ["…"]}}, without success or code. Branch on the HTTP status for those; the envelope is being extended to cover them.

Bulk example: set PTRs for a whole server from a file

Given a file ptrs.txt with one address hostname pair per line:

#!/usr/bin/env bash
KEY="nr_live_..."
IPS=$(curl -s https://api.amoni.app/v1/ips -H "Authorization: Bearer $KEY")

while read -r addr name; do
  id=$(jq -r --arg a "$addr" '.data.servers[].ips[] | select(.address == $a) | .id' <<< "$IPS")
  [ -z "$id" ] && { echo "skip $addr: not on this account"; continue; }
  curl -s -X PUT "https://api.amoni.app/v1/ips/$id/rdns" \
    -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
    -d "{\"dns_name\": \"$name\"}" | jq -r --arg a "$addr" '"\($a): \(.data.message // .error)"'
done < ptrs.txt