domains

PUT /v1/domains/{domainId}/dns/records/{recordId}

Update a DNS record.

Barcha domains yakuniy nuqtalari

Autentifikatsiya

API kalitini bearer token sifatida yuboring. Kalit domains.dns.manage ruxsatiga ega boʻlishi shart; ruxsatsiz kalit 404 emas, balki 403 xatosi bilan rad etiladi.

Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.

Sinab ko'rish

Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.

curl -X PUT https://api.zinndigital.com/v1/domains/{domainId}/dns/records/{recordId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "name": <string>, "type": <DnsRecordType>, "value": <string> }'

Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching

Tafsilotlar

Replaces the record `recordId` in the domain's hosted zone. Requires `domains.dns.manage`. A record hidden from the caller's product line (an A/AAAA on the Footprint-Free line) is indistinguishable from an absent one — a 404 — so it cannot be probed by id (register #93). **Repointing a live apex `MX` is refused** `409 MAIL_CHANGE_REFUSED` unless `confirm_mail_change=true` (issue #622) — it silently stops the customer's email reaching the mailboxes it reaches today, which is data loss rather than a configuration change. So is moving the only apex `MX` onto a subdomain: the record survives, the domain's mail does not. A change that alters only TTL or preference is not refused, because mail still arrives at the same host.

Parametrlar

NomiTuriMajburiyNima bu
domainId (path)UuidHaThe domain's id.
recordId (path)stringHaThe DNS record's provider id.
confirm_mail_change (query)booleanYo'qSet `true` to proceed with a record change that would move or remove this domain's inbound email (issue #622). Without it, a write that stops mail reaching a host it reaches tod…

Soʻrov tanasi

NomiTuriMajburiyNima bu
namestringHaThe record name — `@`/empty for the apex, or a relative/absolute host.
typeDnsRecordTypeHaA DNS resource-record type the shared editor supports (docs/31 §5.2).
valuestringHa
ttlintegerYo'q
priorityobjectYo'q
proxiedobjectYo'qServe this record through the provider's HTTP proxy — Cloudflare's orange cloud. **`A` and `AAAA` only**; sending it on any other type is a `422` rather than a silent drop, beca…

Javob

NomiTuriMajburiyNima bu
idstringHaThe provider-assigned record id.
namestringHaThe record name — `@` for the apex, or a relative/absolute host.
typeDnsRecordTypeHaA DNS resource-record type the shared editor supports (docs/31 §5.2).
valuestringHaThe record value (target/content).
ttlintegerHaTime-to-live in seconds.
priorityobjectYo'qPriority for MX/SRV records; null otherwise.
proxiedobjectYo'qWhether this record is served through the provider's HTTP proxy — Cloudflare's **orange cloud**. Applies to `A` and `AAAA`; providers without a proxy ignore it. ⛔⛔ **Three state…
ownerDnsRecordOwnerHaWho may change this record. `platform` means the platform created it and converges it — the A/AAAA record at the apex or `www` that points the domain at the hosting we run for i…
driftDnsRecordDriftYo'qWhat the last reconcile found about a **platform-owned** record at the provider, or `null` when the provider agrees with us (the overwhelmingly common case). `changed` — a recor…

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

401 · 403 · 404 · 409 · 422 · 429 · 502 · 503