Skip to main content

CNAME Records Not Resolving since server migration

Comments

5 comments

  • acenetgeorge
    Hello Ben, There should be three CNAME records needed for signing DKIM for a domain using Amazon SES. My first guess is that they might be missing. I found am article on how to set up the CNAMES here: [url=http://docs.aws.amazon.com/ses/latest/DeveloperGuide/easy-dkim-dns-records.html]Creating DNS Records for DKIM Signing in Amazon SES - Amazon Simple Email Service In the search box, look for edit dns, and edit the zone file for that domain. See if the three CNAME records exist. If they do not, create the, according to that link I posted. Hope that helps. George Yedinak Systems Administrator Acenet Inc.
    0
  • cPanelMichael
    Hello :) In regards to your other issue, with "mail.domain.com" not responding, check to make sure that subdomain resolves to the correct IP address. It seems odd that it would stop working if the name servers were updated at the registrar to the new server's name servers. Thank you.
    0
  • cafben123
    Thank you George for the response. All 3 are there. They were on the old server and they show up under the new server when I go to edit the dns. Really strange. Amazon just removed DKIM signing this morning despite the fact that I can see the CNAME records. Really strange I think.
    0
  • cafben123
    Thank you. mail.domain.com appears to be working now - 4 days after switching from 1and1 namesevers to the name servers on my server (which uses whm/cpanel). Assuming that this had something to do with DNS propagation. I am still having the CNAME issue that Amazon does not recognize that they are there despite the fact that I can see them when I go to edit the zone. We have triple checked and they are all correct. Also - I tried using MXToolBox to see any cname records for the domain and MXToolBox also says no records exist.
    0
  • cPanelMichael
    Feel free to open a support ticket so we can review the actual domain name in question and determine why the MX records are not propagating. You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0

Please sign in to leave a comment.