Are you sure you want to close the chat?Chat will be closed and the chat history will be cleared.
continue to sign out,
or stay on chat.
To review this chat session please click this windows.
Chat Online
Chat Online0
Support

Forum

A place for Dynadot and community experts alike to ask questions, share ideas, and more.
DKIM not working
5/30/2016 16:17
Hi, I'm trying to set up my dns to work with mailgun. I set up almost all records correctly (two MX, a CNAME for email subdomain and the SPF TXT record on the main domain). However, there is one single field that cannot be seen correctly from my mailgun control panel. It is the DKIM record.

The service asks me to set pic._domainkey.mydomain.com to "k=rsa; p=...". I have done that using the subdomain fields in the DNS panel, but it does not work. I waited 24 hours but the problem is there. And all other fields have propagated correctly.
Reply Quote
6/6/2016 02:20
Looks like you set an A record and a CNAME record for a subdomain. We don't see other settings you mentioned.
Please feel free to contact us again if we can be of any further assistance.
Reply Quote
Posted By rainer
6/11/2016 08:46
The field in your webinterface takes only 255 characters.

The DKIM key is ways longer (more than 400 characters):

rd@home:~$ dig -t TXT netcup._domainkey.bokomoko.de

; <<>> DiG 9.9.5-9+deb8u6-Debian <<>> -t TXT netcup._domainkey.bokomoko.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53950
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;netcup._domainkey.bokomoko.de. IN      TXT

;; ANSWER SECTION:
netcup._domainkey.bokomoko.de. 86400 IN TXT     "v=DKIM1\; t=y\; k=rsa\; p=" "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuQAC62jcQdiu8ypuHitL" "npwxe4MTyLbRTUai4ofkkzf+ox3J426RAKR2fiZpji2lq44DSUM1F5VNrO7Cx2Lq" "JXUDqF9BuUUIqLojuxKpIAxZ3tJkHeMWMm+rWITV4MICd4c8fV5YG9BcKQ52IKUj" "FndV939BYjW2VnNu5PkwYHzHCprG4lTeBgKi0eHsHR+28pVcqEhE5bLzN9GV0RTU" "Iw8nvppGV9xjmDN02zvOQk+aesDHq76JzMRHdwwppqLMyColvsE4OLFK7zRqpEWq" "0IhHhZRk2A0EMpOWidS7ZzXN8QNiCL3rMfy/pfF4b1XWfeLADkumBcg3raFRqonN" "jQIDAQAB"

;; Query time: 178 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Sat Jun 11 17:43:41 CEST 2016
;; MSG SIZE  rcvd: 482

rd@home:~$


* Since the key is longer, I cannot enter it, therefore you cannot see it. *
Reply Quote
Posted By rainer
6/11/2016 08:47
Sorry, please ignore (and delete if you want) my previous post, it went to the wrong thread.
Reply Quote
6/23/2016 16:28
That's okay :)
Reply Quote