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

Pengesahan

Hantar kunci API sebagai token pembawa. Kunci tersebut mesti membawa kebenaran sites.restart; kunci yang tidak mempunyainya akan ditolak dengan 403, bukan 404.

Titik akhir ini tidak memerlukan id organisasi. Kunci anda telah mengenal pasti organisasi kepunyaannya, dan respons dis skopkan kepadanya.

Cuba

Gantikan apa sahaja di dalam kurungan sudut dengan nilai anda sendiri, dan pemegang tempat kunci dengan kunci dari papan pemuka 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 log masuk? Konsol API dalam papan pemuka anda mengisi id organisasi sebenar dan kunci anda sendiri, serta menjalankan permintaan terhadap API langsung supaya anda boleh melihat respons sebenar. Buka penamat ini dalam konsol API

Butiran

⛔ `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

Badan permintaan

Respons

Ralat yang boleh dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429 · 503