DNS record created during transfer from google/squarespace to wordpress

  • Unknown's avatar
    craigathomas · Member ·

    modlook

    I transferred 2 domains from google/squarespace to wordpress yesterday, 5-oct-2023. On inspection of the DNS records there were some differences that may or may not be important.

    This post is about the domain name musicbeat.org, which is associated with a google workspace starter environment.

    On inspection of the DNS records in wordpress after the transfer, I see a significant number of TXT records that were not present in the google/squarespace DNS.

    I’m no expert on DNS records, and have no idea whether these records are the result of intended behavior in the transfer process.

    But if they are not needed for my domain to function correctly, it would certainly be easier to maintain DNS entries if superfluous entries were not complicating the picture.

    Here are the three TXT entries that were present in the google/squarespace DNS prior to transfer:

    musicbeat.org TXT 2 hours
    “v=spf1 include:_spf.google.com ~all”
    “keybase-site-verification=5V0pmBR2c8qY_YEKF59yVgc61sWreTjBrQFOJ3CLlOQ”
    “google-site-verification=Rb__bAitqpqcvNteH96-BLmshXVOlvSkT62PaH8ctio”

    *.musicbeat.org TXT 2 hours
    “v=spf1 include:_spf.google.com ~all”

    google._domainkey.musicbeat.org TXT 2 hours
    “v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQChsCpShtpwvGk9BgHeABGx3U38s5gv60bG8WHCNIM5Ce69CZqHZVH1RfwnTjIwAB5ub43EiF/8VSns0my8eeT9wNWtqpGREo/r9uI6hoXz5GrVntvPyO+d2P9E7SOgw9nbTvqlrFAY+WglJ6vBjfzQ4OxuA6+Qk4BFEErRNakFWwIDAQAB”

    Here are the TXT records that are present post-transfer in the wordpress DNS, which were not present in the google/squarespace DNS:

    TXT
    admin
    v=spf1 include:_spf.google.com ~all

    TXT
    asuid
    v=spf1 include:_spf.google.com ~all

    TXT
    default._bimi
    v=spf1 include:_spf.google.com ~all

    TXT
    dtravel_verification
    v=spf1 include:_spf.google.com ~all

    TXT
    email
    v=spf1 include:_spf.google.com ~all

    TXT
    entri
    v=spf1 include:_spf.google.com ~all

    TXT
    facebook
    v=spf1 include:_spf.google.com ~all

    TXT
    google
    v=spf1 include:_spf.google.com ~all

    TXT
    googlesearchconsole
    v=spf1 include:_spf.google.com ~all

    TXT
    info
    v=spf1 include:_spf.google.com ~all

    TXT
    mailo._domainkey.mg
    v=spf1 include:_spf.google.com ~all

    TXT
    mg
    v=spf1 include:_spf.google.com ~all

    TXT
    @
    v=spf1 include:_spf.google.com ~all

    TXT
    ovhcontrol
    v=spf1 include:_spf.google.com ~all

    TXT
    pic._domainkey.mg
    v=spf1 include:_spf.google.com ~all

    TXT
    pinterest
    v=spf1 include:_spf.google.com ~all

    TXT
    shopify_verification
    v=spf1 include:_spf.google.com ~all

    TXT
    smtp._domainkey.mg
    v=spf1 include:_spf.google.com ~all

    TXT
    smtpapi
    v=spf1 include:_spf.google.com ~all

    TXT
    trustifi
    v=spf1 include:_spf.google.com ~all

    TXT
    zendeskverification
    v=spf1 include:_spf.google.com ~all

    TXT
    zendeskverification.support
    v=spf1 include:_spf.google.com ~all

    TXT
    _acme-challenge
    v=spf1 include:_spf.google.com ~all

    TXT
    _amazonses
    v=spf1 include:_spf.google.com ~all

    TXT
    _atproto
    v=spf1 include:_spf.google.com ~all

    TXT
    _bareconnect
    v=spf1 include:_spf.google.com ~all

    TXT
    _caldav._tcp
    v=spf1 include:_spf.google.com ~all

    TXT
    _caldavs._tcp
    v=spf1 include:_spf.google.com ~all

    TXT
    _canva-domain-verify
    v=spf1 include:_spf.google.com ~all

    TXT
    _carddav._tcp
    v=spf1 include:_spf.google.com ~all

    TXT
    _carddavs._tcp
    v=spf1 include:_spf.google.com ~all

    TXT
    _cf-custom-hostname
    v=spf1 include:_spf.google.com ~all

    TXT
    _coda
    v=spf1 include:_spf.google.com ~all

    TXT
    _crisp
    v=spf1 include:_spf.google.com ~all

    TXT
    _dmarc
    v=spf1 include:_spf.google.com ~all

    TXT
    _dmarc.support
    v=spf1 include:_spf.google.com ~all

    TXT
    _dv
    v=spf1 include:_spf.google.com ~all

    TXT
    _mailpoet
    v=spf1 include:_spf.google.com ~all

    TXT
    _mypaymail
    v=spf1 include:_spf.google.com ~all

    TXT
    _openid
    v=spf1 include:_spf.google.com ~all

    TXT
    _outlook
    v=spf1 include:_spf.google.com ~all

    TXT
    _portfolio
    v=spf1 include:_spf.google.com ~all

    Please let me know if you need additional information.

    Thanks for your time and attention.

    The blog I need help with is: (visible only to logged in users)

  • staff-totoro · Staff ·

    Hi there,

    As with your other post, If your records were over 255 characters is may be necessary to ask Google to provide a shorter record that will work instead. It seems that Google enables DKIM by default (which is where these records for domainkeys and keybase-site-verification come from) so you can choose the 1024bit option they recommend here, which will provide records that will work with our service. https://support.google.com/a/answer/10684623?hl=en

    Also you can turn off DKIM, it may be more than you need unless you are sending a lot of outgoing mail and having trouble getting through people’s spam filters. For light use, they are not typically needed.

    Regarding the other TXT records you have mentioned above, it’s not clear to me what those represent, though they seem to be domain verification records for 3rd party services like outlook, mypaymail, mailpoet, etc. We do not use SPF records or add them for any reason so it seems they are related to your previous configuration. You menitoned that you did not see these records on Google Domains when it was managed through them but they had to have been set there previously, perhaps as hidden settings of some kind?

    It’s likely that you don’t need these so you can safely delete them. However, they do no harm so it’s just as easy to leave them as they are.

    Hope that helps. Please let us know if you have any more questions.

  • The topic ‘DNS record created during transfer from google/squarespace to wordpress’ is closed to new replies.