GoDaddy
GoDaddy DKIM: add the record and confirm mail is signed
GoDaddy DKIM setup: where to add the CNAME or TXT record, what to type in Name, and how to confirm Microsoft 365 or Google Workspace mail is signed.
Before you start
To set up GoDaddy DKIM, copy the record from the service that sends your mail, add it under DNS Records in your GoDaddy account, then turn on signing at that service.
Check two things first:
- GoDaddy hosts your DNS. Run
nslookup -type=NS example.com 1.1.1.1. The answer lists the name servers that hold your records. GoDaddy documentsns1.domaincontrol.comas a nameserver example; compare the exact pair with the one in your account. If they belong to another company, add the record there, because records saved at GoDaddy will not be used. - You can sign in to the GoDaddy account that holds the domain.
| Sender | Type | Name in GoDaddy | Value |
|---|---|---|---|
| Microsoft 365 | CNAME, two records |
selector1._domainkey and selector2._domainkey |
From Publish CNAMEs in Defender |
| Google Workspace | TXT, one record |
google._domainkey or your chosen prefix |
v=DKIM1; k=rsa; p= plus your key |
If GoDaddy sold you the mailboxes, including a Microsoft 365 plan, check GoDaddy's help center for your plan first, because its steps may differ.
Steps
Get the values from your sender
- Microsoft 365: in the Defender portal, open Email authentication settings > DKIM and try to turn on the toggle for your domain. A Client error dialog opens as part of the procedure. Select OK, open the domain and copy the values in Publish CNAMEs. DKIM for Microsoft 365 has the full path.
- Google Workspace: in the Admin console, open Apps > Google Workspace > Gmail > Authenticate email, then select Generate New Record. Leave Start authentication for later.
Add DKIM in GoDaddy
- Sign in to GoDaddy, select your login name in the upper right, then select My Products.
- Under Domains, on the Portfolio tab, select the three dots next to the domain, then Edit DNS.
- Under DNS Records, select Add New Record. Microsoft's DKIM article calls it Add Record.
- Set Type to
CNAMEorTXT, as your sender says. - In Name, enter only the part before your domain, such as
selector1._domainkey. - In Value, paste the value exactly. Microsoft lists a trailing dot as not needed at GoDaddy.
- Set TTL to 1 Hour and select Save. Repeat for Microsoft's second record.
Caution: if a record already exists at that name, find out what uses it before you change or delete it. A receiver that finds no key at a selector fails the signature. That mail can then fail DMARC unless SPF passes and aligns.
Turn on signing
- Microsoft 365: wait a few minutes or longer for Microsoft to detect the CNAMEs. In the domain details, select Sign messages for this domain with DKIM signatures.
- Google Workspace: select Start authentication.
Caution: Domain Connect may offer to replace existing MX records when Exchange and Exchange Online Protection is selected. If you keep another mail provider, add only the DKIM CNAMEs manually instead.
Confirm it worked
- Look up your selector with
nslookup -type=TXT selector1._domainkey.example.com 1.1.1.1, or use the DKIM checker. The name should appear once, followed by your sender's target or key. - Microsoft 365 shows Signing DKIM signatures for this domain. Google shows Authenticating email with DKIM.
- Send a message to an address in another email system, such as outlook.com or gmail.com, because Microsoft omits the signature when both addresses are in the same domain or in domains controlled by the same organization. In the headers, look for
dkim=passinAuthentication-Results. - Read
d=inDKIM-Signature. DMARC counts the signature only if that domain aligns with your From domain. Next, set up SPF at GoDaddy and DMARC at GoDaddy.
Microsoft says DNS changes at GoDaddy typically take about 15 minutes and occasionally longer.
Google says DKIM may take up to 48 hours to start. During that time, Authenticate email may still show You must update the DNS records for this domain; if the record is correct, wait instead of replacing it.
Common problems
- Wrong DNS name. Enter the selector prefix in Name, such as
selector1._domainkey, and check the full saved name. - A TXT record where Microsoft expects a CNAME. This leaves
CnameMissing. Identify the signer using that TXT first. Coordinate its migration before removing an active key, then publish Microsoft’s CNAME; do not overwrite a key another service still needs. - Two TXT records at one selector. RFC 6376 leaves the result undefined. Keep only the record whose key matches the one your sender shows now, and delete the other. To change keys later, publish the new key under a new selector, then switch the sender to it.
- A long TXT key is cut short. Google warns that a 2048-bit key may not fit in one 255-character string. If your lookup shows a shorter value, ask GoDaddy whether it takes longer TXT values, or split the key into quoted strings as Google describes.