PUT /v1/compute/servers/{serverId}/reverse-dns

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin sites.restart; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Endpoint ini tidak memerlukan id organisasi. Kunci Anda telah mengidentifikasi organisasi tempatnya berafiliasi, dan respons akan dibatasi untuk organisasi tersebut.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

curl -X PUT https://api.zinndigital.com/v1/compute/servers/{serverId}/reverse-dns \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "ip": <string> }'

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

⛔ `ip` is required and is never inferred from the machine: a machine has an IPv4 and an IPv6 address with **different** default states, so "set the PTR of this server" is not a well-formed request. An empty `hostname` resets that address to the provider's own default, which is a real thing to want and is not the same as leaving it alone. ⛔⛔ **The hostname must resolve forward to this address, and that is checked before anything is written.** Receiving mail servers check forward-confirmed reverse DNS, so a PTR whose name does not point back is *worse* than the supplier's default: it looks configured on the screen and still fails delivery. A name that does not resolve at all is refused too — "we could not look it up" is not evidence the record exists. An `ip` the machine does not hold is `422`, and that refusal is the tenancy boundary: the provider would happily set a PTR for any address on the account, including another customer's. Requires `sites.restart`.

Parameter

Isi permintaan

Tanggapan

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429 · 503