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

Autentifikacija

Pošaljite API ključ kao nosivi token. Ključ mora imati dozvolu sites.view; ključ bez nje se odbija s kodom 403, a ne 404.

Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.

curl -X GET https://api.zinndigital.com/v1/compute/servers/{serverId}/reverse-dns \
  -H "Authorization: Bearer zdk_live_…"

Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli

Pojedinosti

⭐ The highest-value control on a machine we source ourselves, and the platform had none anywhere before it. A freshly built machine's IPv4 PTR is the supplier's own hostname, which does two things at once: it names our supplier to anyone who runs dig -x, and it breaks outbound mail, because every receiving mail server of consequence checks forward-confirmed reverse DNS. ⛔⛔ A blank hostname means the address has NO PTR at all — it does not mean "the default". Measured across every machine on our own account: each IPv4 carries a supplier default and each IPv6 carries nothing. Render the two differently, or you tell a customer their IPv6 leaks when it does not, and hide the address that does. Read live on every request and never cached: a PTR can be changed at the provider, and a cached one is a claim about the past presented as the present. Requires sites.view.

Parametri

Odgovor

Pogreške koje ova krajnja točka može vratiti

401 · 403 · 404 · 422 · 429 · 503