GoDaddy Email email configuration guide
GoDaddy Professional Email: DKIM records are not detected
A record that never appears is usually saved under the wrong host or has the wrong CNAME target. Check authoritative DNS before assuming propagation delay.
A provider configuration symptom may look like:
DKIM key propagation after a provider configuration change.
Check before waiting
Query both complete selector names at the authoritative nameservers. If the records are absent there, waiting will not fix them.
Evidence to collect
- Confirm which company hosts authoritative DNS.
- Compare both CNAME host names and targets with GoDaddy’s dashboard.
- Check for a duplicated domain suffix or conflicting record.
- Once authoritative DNS is correct, wait for the previous TTL to expire.
Safe correction sequence
Do not repeatedly delete and recreate correct records; that restarts uncertainty. After public resolvers agree, rerun GoDaddy’s check and verify a newly sent message.
MailFixIt boundary
MailFixIt checks current public DNS, not GoDaddy’s internal verification queue.
Frequently asked questions
What does MailFixIt check for GoDaddy Email?
It helps compare public DNS evidence with the provider setup path. It does not access the provider account or claim that a DNS result alone proves sending or receiving.
Should I replace all existing DNS records with provider values?
No. Confirm the exact record owner and type, preserve unrelated legitimate services, and change only the record required for the intended mail route.
Related email diagnostics
Primary sources: GoDaddy: Add SPF, DKIM and DMARC to Professional Email.