Setting up DKIM - successfully?

Max Classic
#1

Has anyone been able to successfully set-up the DKIM record using AWS DNS?

I am finding conflicting information between what is shown in the Help Centre Video (m 18:18)
https://help.infusionsoft.com/mastermind/dkim-spf-open-qa

and what shows in the email authentication window.
For example the email authentication for my account it reads that I should create the CNAME “host” as (from step 1):
49aa89a9b-84fd-47e7-9a94-7b9034da032c._domainkey

yet the video show it should be entered as:
49aa89a9b-84fd-47e7-9a94-7b9034da032c._domainkey.mydomainname.com

** I have changed the values for security and not provided my domain name.

On step 2.

The video also shows that the DNS should resolve to: infusionmail.com , however the instructions that it should resolve to “dkim.infusionmail.com”

Which one is correct?

Thank you.

#2

I was about to remove the dkim from the message until I read further lol

The part that says .mydomainname.com is created by your server to make it specific to your domain name in question. This is necessary to differentiate between other possible domain name assignments on the same server and is automatically done by your server.

I’m not sure about the with and without dkim. before infusionsomail.com but I ‘think’ it’s different based on the DNS service. If IS staff could check on that I’m sure that’s something we’d all find useful to have verified. Our instructions in our app said to use dkim.infusionmail.com.

#3

Thank you, John.
The reason that I asked the question is that the video supplied by IS (https://help.infusionsoft.com/mastermind/dkim-spf-open-qa) has the user entering the mydomain.com part in the “host” name vs. automatically entered by the DNS server.
Video has some subtle differences than the written instructions…
B

#4

I can certainly understand that confusion and I wish I could say I haven’t seen that before but it does seem to happen sometimes. I’ve always just entered the selector (without the domain part) and the server has always tacked that on for me. I’ve seen this behavior on a wide variety of dns providers and it seems to be consistent. The way to tell, of course, is try creating it without the domain part and once saved, go back and look at what the server does with it.

#5

Thank you for your feedback. Got it to work. B

1 Like