hosting

POST /v1/sites/{siteId}/edge-domains/{hostname}/dns

Publish this domain's DNS records for the customer.

Sve hosting krajnje tačke

Autentifikacija

Pošaljite API ključ kao bearer token. Ključ mora imati dozvolu hosting.deploy.manage; ključ bez nje se odbija sa 403, a ne sa 404.

Ovaj krajnji tačka ne prihvata ID organizacije. Vaš ključ već identifikuje organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamenite bilo šta u uglastim zagradama sopstvenim vrednostima, a ključni placeholder sa ključem sa vaše kontrolne table.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/edge-domains/{hostname}/dns \
  -H "Authorization: Bearer zdk_live_…"

Prijavljeni ste? API konzola na vašoj kontrolnoj tabli automatski popunjava ID vaše stvarne organizacije i vaš sopstveni ključ, i izvršava zahtev nad API-jem uživo tako da možete videti stvarni odgovor. Otvorite ovu krajnju tačku u API konzoli

Detalji

Writes the records and then resolves them, so the answer is what the internet says rather than what we did. Three tiers in order — the customer's own connected DNS provider, then our nameservers with the zone pre-built, then the records to publish by hand — and the tier that was actually used comes back as `mode`. In `nameservers` mode the `nameservers` array is the one thing left for the customer to do. Requires `hosting.deploy.manage`.

Parametri

NazivVrstaObaveznoŠta je ovo
siteId (path)UuidDaSite ID (UUIDv7).
hostname (path)stringDaThe bound hostname, lower-cased and without a trailing dot.

Odgovor

NazivVrstaObaveznoŠta je ovo
hostnamestringDa
modestring<unknown, our_zone, byo_dns, nameservers, manual>Da
zonestringDa
vendorstringDa
detailstringDa
nameserversstring[]DaPopulated only in `nameservers` mode — the zone is built and the records are in it, and setting these at the registrar is the one thing left to do.
recordsDnsRecordPlan[]Da
checksDnsRecordCheck[]Da
resolvesbooleanDa

Greške koje ovaj krajnji tačka može da vrati

401 · 403 · 404 · 422 · 429