Related

Tool DOCTL: DigitalOcean CLI Tool
Why are snapshots so slow Question Question
my site i down please see http://www.cheri3a.com/ Question Question

Question

AMAZON SES > DigitalOcean CNAME not working

Posted April 13, 2017 4.1k views
UbuntuDigitalOceanAPIConfiguration ManagementControl Panels

Hello EVeryone,

This is my website http://workwatch.co.nz

I have the domain registered through Discount domains. But I’m using DigitalOcean to handle all the DNS records.

Everything is sweet, But I cannot seem to setup the AMAZON SES DKIM records with the DigitalOCean control panel.

I entered the CNAME values as given to me, but the verifications on AWS control panel fails continuously. Any help with this would be really appreciated.

Sahan.

Add a comment
timesheetapp007
By:
timesheetapp007

Related

Tool DOCTL: DigitalOcean CLI Tool
Why are snapshots so slow Question Question
my site i down please see http://www.cheri3a.com/ Question Question
Add a comment
1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
mrcbrown April 13, 2017

Forgive me if I’m wrong, but usually, DKIM/SPF are TXT records, usually also used for verifications,not CNAME’s - have may want to confirm (https://docs.aws.amazon.com/ses/latest/DeveloperGuide/dns-txt-records.html) as SES says it confirms with TXT records and if you are putting them in as CNAME’s that may be the issue at hand.

Reply Report
  • timesheetapp007 April 13, 2017

    @mrcbrown thanks for the answer, but if you see here, AWS gives me this
    http://i.imgur.com/eAdHBOi.png

    Reply Report
    • mrcbrown April 13, 2017

      @timesheetapp007 few followup questions:

      • Do you get any sort of error on the DO side when trying to put these CNAME’s in?
      • Are they live and in place now?
      • Have you tried to query these CNAMES both locally and from say https://dnschecker.org/?

      Don’t work for DO but have had issues with DNS and Amazon (not specifically SES) but sometimes if it catches it wrong, it can be 72 hours before like it notes, but definitely confirming it externally (DNS Checker is great) might bring up something to fix/adjust or open a ticket with DO specifically if something isn’t rendering correctly.

      Reply Report
    • exozetech April 3, 2019

      Have you managed to solve this? I am also having the same problem, this is so frustrating, I’m also using Namecheap, it can add CNAME just fine, it only takes 5 seconds. But this Digital Ocean made is so hard.

      Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help