GoDaddy
Support
API ReferenceDomainDomain LifecycleDomains & DNSv1 (Legacy)Manage DNSReplace DNS records by type PUT

Replace DNS records by type

View as Markdown

Replaces all DNS records of the specified type across all names.

Full description

Replaces all DNS records of the specified type across all names. Records of other types are preserved. Returns 204 No Content.

PUT
/v1/domains/{domain}/records/{type}

Authorization

bearerAuth
AuthorizationBearer <token>

Personal Access Token (PAT). Generate one from the developer dashboard. Pass as: Authorization: Bearer .

In: header

Path Parameters

domain*string

Domain whose DNS Records are to be replaced

type*string

DNS Record Type for which DNS Records are to be replaced

Value in

  • "A"
  • "AAAA"
  • "CAA"
  • "CNAME"
  • "MX"
  • "NS"
  • "SOA"
  • "SRV"
  • "TXT"

Header Parameters

X-Shopper-Id?string

Shopper ID which owns the domain. NOTE: This is only required if you are a Reseller managing a domain purchased outside the scope of your reseller account.

Request Body

DNS Records to replace whatever currently exists

[index: integer]?

Response Body

curl -X PUT "https://example.com/v1/domains/string/records/A" \  -H "Content-Type: application/json" \  -d '[    {      "data": "string",      "name": "string"    }  ]'
Empty

Agent & Automation Notes

Scopesdomains.domain:read, domains.domain:create, domains.domain:delete, domains.domain:update, domains.contact:update, domains.dns:update, domains.transfer:execute
Rate limit60 req/min per credential
On failureGET operations are safe to retry. PUT/PATCH DNS are idempotent by shape. POST purchase is NOT idempotent — verify state before retrying.

Related

Last updated on

How is this guide?