Guide
Connecting GoDaddy to publish DNS
Let this product publish a sending identity's DNS records instead of copying a 250-character DKIM value by hand.
A sending identity needs several DNS records, one of which is a DKIM value a few hundred characters long. The commonest failure in setting one up is not a misunderstanding -- it is a transcription error: a trailing dot, a wrapped line, or the zone name appended twice.
Connecting GoDaddy turns that into a button.
The key
Create one at https://developer.godaddy.com/keys, signed in as the account that owns the domain. The key inherits that account's domains and can write to those and no others.
**Choose Production.** An OTE key looks identical, edits a sandbox zone, and reports success while changing nothing real. It is the one mistake here that leaves no trace.
There is one value to copy. Current keys are used on their own; the Secret box exists only for an older key that came as a pair, and pasting the key into both boxes is treated as leaving the second blank.
What publishing does and does not touch
It writes only the records the identity needs, each at one exact type and name, and it never deletes anything. Every other record in the zone is left alone.
That restraint is deliberate. A sending identity has no business removing an A record, and a bug that did would take a website down rather than an email.
If a record fails
Each record is reported on its own, because a partial success is normal -- a zone holding a conflicting CNAME rejects one record and accepts the rest. A failure naming a domain that is not on the account means exactly that: the domain is registered somewhere else, and the key cannot reach it.
Propagation takes a few minutes. Re-checking immediately shows the old answer, which is not a failure.
Full API documentation: https://developer.godaddy.com/doc/endpoint/domains