Skip to main content

cPanel transfer tool doesn't update SPF and DKIM records

Comments

8 comments

  • cPRex Jurassic Moderator
    Hey there! Our documentation at Transfer Tool | cPanel & WHM Documentation says this: "The Transfer Tool feature replaces the source server"s files with the target server"s zone files when the following conditions are true: The target server resides in the same Domain Name System (DNS) cluster as the source server. The source server and the DNS nodes use the Synchronized Changes DNS role." so it looks like that is the most likely scenario.
    0
  • stormy
    The target and the source server are both pushing DNS records to the same cluster using synchronized changes, yes. I've reviewed the linked document, that's useful information, thanks! However, I see two problems: One, there were custom TXT records, including DKIM, that were simply erased (used for Amazon SES). Not sure if that's expected or not. Two, the actual SPF and DKIM records were not replaced. The wrong ones from the source server were kept. That DKIM even "survived" the command to recreate it, I had to do it by hand. I don't see any mentions of TXT records in "The Transfer Process" Transfer Tool | cPanel & WHM Documentation I don't know why some survive, some are erased, etc. So maybe this can be documented? Although it seems to me I've run into a bug.
    0
  • cPRex Jurassic Moderator
    That does sound odd, and also sounds like more than what the docs cover in that link. Could you open a ticket with our team so we can do some more investigation on this?
    0
  • stormy
    Thanks, I've just opened a ticket with all the info.
    0
  • cPRex Jurassic Moderator
    Could you post the number here so I can follow along?
    0
  • stormy
    Thanks! #94320081 I've just realized that the subdomains A records were wiped too! I didn't realize that when I did the transfer.
    0
  • cPRex Jurassic Moderator
    Thanks for that - I'm following along with that ticket now so I'll make sure this thread stays updated.
    0
  • cPRex Jurassic Moderator
    After some pretty extensive testing, we weren't able to replicate this behavior on our end. Thanks for much for the access you provided and your willingness to test different scenarios in that ticket.
    0

Please sign in to leave a comment.