GoDaddy hosts your domain's DNS, not your email, so the DKIM record you paste there always comes from whichever provider actually sends your mail: Google Workspace, Microsoft 365, or your ESP. GoDaddy's role is limited to publishing the TXT record correctly once you have that value in hand.
The record itself is a TXT record at a host built from your provider's selector plus ._domainkey, for example google._domainkey for Google Workspace. GoDaddy's own instructions are the same for any TXT record: sign in to your domain, open DNS management, choose TXT as the record type. The Name field takes the selector prefix without your domain name attached, using @ only if you were setting a record on the root domain itself, which a DKIM selector is not.
Most "DKIM does not verify" cases at GoDaddy are not a GoDaddy mistake. The record is usually pasted correctly, and the real problem is that the sending provider's key was never turned on, or the record has not finished propagating yet. GoDaddy states most DNS updates apply within an hour, with full global propagation taking up to 48 hours, so a check run minutes after publishing the record can fail correctly and still resolve on its own.
Once you have waited past the propagation window, the DNS & auth checker confirms the DKIM record resolves and matches what your provider expects, in the same pass it checks SPF and DMARC.
Neither, directly. It goes on the selector host, <selector>._domainkey, which GoDaddy's Name field builds from the selector prefix without your domain name attached. Use @ only for a record meant for the root domain itself.
GoDaddy states most updates take effect within an hour, with full propagation taking up to 48 hours across all resolvers, so a failed check inside that window is not yet a configuration error.
Usually not. The far more common cause is that the record has not finished propagating yet, or the sending provider's own DKIM signing was never switched on, both of which look identical from a single failed check.