Retry Endpoint DNS
Start DNS provisioning again for an endpoint whose DNS record could not be created. When you create an endpoint on a custom domain in auto provisioning mode, ngris writes its DNS record through your DNS provider in the background; the endpoint's status is pending_dns meanwhile and becomes dns_failed when every attempt failed (dns_last_error on Get Endpoint says why). Fix the cause — for example the provider credentials on the domain — then call this.
The endpoint goes back to pending_dns with dns_attempts reset to 0 and dns_last_error cleared, and a new provisioning job is queued. The call returns as soon as the job is queued: poll Get Endpoint for the outcome.
Only an endpoint in dns_failed or pending_dns can be retried, and only when its domain is in auto provisioning mode with a DNS provider configured — manual and wildcard domains have no per-endpoint record to write. Requires the endpoints:update permission in the active account.
Path parameters
uuid from List Endpoints.Request body
None. Send the Content-Type: application/json header anyway (the API answers 415 without it).
Response (202 Accepted)
pending_dns: the endpoint's new status.Errors
endpoint not in a DNS-retryable state (its status is not dns_failed or pending_dns); endpoint has no managed DNS (the endpoint is linked to no domain); or domain has no per-endpoint managed DNS (manual/wildcard mode, or no provider configured).endpoints:update, you are not a member of the active account, or the account is suspended (account_suspended).endpoint not found — no endpoint with this uuid in the active account.quota_paused: the endpoint is paused over your plan's limits and is read-only.Content-Type: application/json header.failed to enqueue DNS job: …); the endpoint is marked dns_failed again, so you can retry.DNS CNAME target / apex fallback IP not configured).