I’m working on configuring Mailgun to use my own domain instead of the default sandbox domain that comes with new accounts. Everything seemed to go smoothly at first, but now I’m stuck on the domain verification step.
The SPF record got verified pretty quickly, maybe around 5 minutes after I added it to my DNS settings. However, the DKIM record is still showing as unverified even though it’s been much longer now.
I’m wondering if this is just a matter of waiting longer for DNS propagation, or if I might have made an error in how I set up the DKIM record. Has anyone else run into similar verification delays with DKIM when setting up their custom domain in Mailgun?
DKIM records often require a longer propagation time compared to SPF records. I’ve frequently observed SPF verifications happen in just a few minutes, whereas DKIM can take up to 24 hours. However, it’s wise to first verify your DNS settings for any potential formatting errors. DKIM records can be particularly sensitive, so ensure there are no unintended quotes or missing parts in the long key string. Utilizing a DNS lookup tool may help clarify if the record is correctly configured. If everything appears to be correct, you are likely just experiencing normal propagation delays.
Same thing happened when I migrated from sandbox last year. DKIM took almost 36 hours to verify - super frustrating since SPF was instant. I used dig to check if the TXT record was actually propagating across different DNS servers. Sometimes it shows up locally but not everywhere else yet. Also check if your registrar has weird rules for long TXT records - some auto-split them which breaks DKIM verification. The wait sucks but it’ll sort itself out within 48 hours max.
same thing happened to me a few months back. DKIM took about 18 hours while SPF was instant. double-check you copied the whole DKIM key without spaces or line breaks - that’s what tripped me up at first. also watch out for extra quotes if your DNS provider adds them automatically.