Why doesn't my SPF record validate?

Return to top
Have more questions? Submit a request

8 Comments

  • Soheil

    Good day Ryan.
    My dnd records set properly. SPF however not verified yet. I have no doubt spf txt record created & tested properly ( through examining the record ) . yet I See same issue :

    SPF does not include Zendesk Support See details

     

    Query your DNS records to check that the SPF records for Zendesk are present for outbound emails.

    This will soon be replaced by the DNS records. During the transition period you should set up both sets of records.

    1
  • Brett Bowser
    Zendesk Community Team

    Hey Soheil,

    I'm going to create a ticket on your behalf so our Customer Advocacy team can take a look at your account and point you in the right direction. You'll receive a follow-up email shortly stating your ticket has been created.

    Cheers!

    0
  • Aaron S

    Hello, I am having the same issues as above, can you please create a ticket for your customer advocacy team to look into? 

     

    0
  • Devan - Community Manager
    Zendesk Community Team

    Hey Aaron,

    I'm going to create a ticket on your behalf so our Customer Advocacy team can take a look at your account and point you in the right direction. You'll receive a follow-up email shortly stating your ticket has been created.

    Best Regards.

    0
  • Anthony A

    Hi Everyone,

    I have exactly the same issue, and have difficulties in getting it resolved.

    I have added all the necessary details for support@ourdomain.com address on AWS Route53, and verified the SPF is valid on two services. I have also added redirection in GSuite between support@ourdomain.com and support@ourdomain.zendesk.com. The email sending to and from support@ourdomain.com works, i.e mail sent to support@ourdomain.com comes in to Zendesk & replies seem to be sent back via support@ourdomain.com just as intended -- but I still keep seeing "SPF does not include Zendesk Support" in Channels > Email > support@ourdomain.com??
     
    I have seen on a few ZenDesk support pages that it is advised to open a support ticket to look into this, hence this request. Could you please advise how to proceed?

     

    0
  • Devan - Community Manager
    Zendesk Community Team

    Hello Anthony A,

    I've opened up a ticket on your behalf so one of our trained specialists can look into this issue for you. You should expect an email soon followed by a response from our Advocacy team.

    Best regards. 

    0
  • Andrew McClure

    We have recently moved to DMARC and have been modifying our SPF records accordingly.  We recently moved to SPF and DKIM for Zendesk, however, we were getting SPF lookup failures.  I figured out that our main TXT record that uses the "redirect" modifier to point to our SPFA/B/C was the issue.  When I took the SPF contents of SPFA and stuck them in the main TXT record and then did an include to SPFB and SPFC it worked.  This seems like a bug as the "redirect" modifier is valid and the other domains we have that we trust to forward emails on our behalf were unaffected.  It's only when we checked the box for SPF and DKIM that we discovered the issue.  Why can't I have a redirect in my main domain TXT record that points to another SPF record?

    0
  • Kay
    Community Moderator

    Andrew McClure I am pretty sure you can use subdomains to split your SPF records and it works too with Zendesk and DKIM.

    Could you share a screenshot of  the checkbox you are referring to?
    "It's only when we checked the box for SPF and DKIM that we discovered the issue"

    If you are getting lookup failures, it's probably the amount of lookups in your SPF, even with the subdomains it still amounts to 10 lookups maximum. The reason why it works when you move it to the highest SPF records, is because of the order of the lookup. And probably another system that also requires SPF will then have the lookup issue. This is an ever growing issue with more systems running in the cloud and requiring SPF. 

    There are two solutions for it; DNS CName Flattening or using subdomains for email addresses.

    0

Please sign in to leave a comment.

Powered by Zendesk