Skip to main content

PTR records (rDNS)

A PTR record maps an IP address back to a hostname. It's what mail receivers check before accepting your outbound mail — without one, your server's email goes straight to spam.

List PTR records for a server​

curl https://api.vps-server.host/v1/servers/srv_42/ptr \
  -H "Authorization: Bearer $PAT"
{
  "server_id": "srv_42",
  "ptr_records": [
    {
      "id":         "dnsp_01HRZ7P3T9X2W6V8M1C4Y7B0A2",
      "ip":         "203.0.113.45",
      "ip_version": 4,
      "value":      "web-01.example.com",
      "backend":    "contabo",
      "synced_at":  "2026-05-20T11:02:05Z"
    }
  ]
}

Set a PTR value​

curl -X PUT https://api.vps-server.host/v1/servers/srv_42/ptr/dnsp_01HRZ… \
  -H "Authorization: Bearer $PAT" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"value":"web-01.example.com"}'

Returns 200 if applied synchronously by the upstream provider, or 202 with an Operation when the provider needs to queue the update.

Match your A record

The PTR value should resolve forward to the same IP (i.e. an A or AAAA record exists for that hostname pointing back here). Mail receivers do this check; mismatches get filtered.

Sync from upstream​

If you've edited PTR via the provider's panel or via a support ticket, refresh our local view:

curl -X POST https://api.vps-server.host/v1/servers/srv_42/ptr:sync \
  -H "Authorization: Bearer $PAT"

Returns 202 with an Operation; on success the updated records are visible via GET /servers/{id}/ptr.