hosting

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

What this domain actually resolves to right now.

Dhammaan hosting bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.view; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Details

Resolves every wanted record from a public resolver and reports what came back. Writes no DNS. `resolves` and each check's `observed` are three-valued on purpose — `null` means the resolver did not answer, which is *unknown* and not *no*; rendering it as a failure puts a red mark on a working domain during a resolver hiccup. Requires `sites.view`.

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
siteId (path)UuidHaaSite ID (UUIDv7).
hostname (path)stringHaaThe bound hostname, lower-cased and without a trailing dot.

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
hostnamestringHaa
modestring<unknown, our_zone, byo_dns, nameservers, manual>Haa
zonestringHaa
vendorstringHaa
detailstringHaa
nameserversstring[]HaaPopulated 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[]Haa
checksDnsRecordCheck[]Haa
resolvesbooleanHaa

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 429