Skip to main content

DNS ERRORS OCCURRED

Comments

11 comments

  • plumdesign
    this appears good: ===== SPF record is good v=spf1 +mx +a +ip4:51.68.33.16 ~all ==== DMARC missing
    0
  • cPRex Jurassic Moderator
    Hey there! I don't see anything obviously wrong with the DNS on my end when I check things just now, and a report at IntoDNS.com is also very clean. You're always welcome to submit a ticket to our team so we can take a look at this directly and get you more details.
    0
  • akramalsaidi9
    How can i sort this issue please i have vos from digitalocean as well ?
    0
  • cPRex Jurassic Moderator
    You would need to contact Digital Ocean to have them create the reverse DNS record for you, as that is something that isn't handled on your server.
    0
  • akramalsaidi9
    You would need to contact Digital Ocean to have them create the reverse DNS record for you, as that is something that isn't handled on your server.

    how i can solve this issue please ? I,ve attached image for my proplem when i sent mail
    0
  • cPRex Jurassic Moderator
    Are you not able to send to any domain? If so, it's possible your hosting provider doesn't allow outbound connections over port 25. You can test this by running the following command from the server: telnet gmail-smtp-in.l.google.com 25 and seeing if that lets you connect normally.
    0
  • akramalsaidi9
    how i can solve this issue please ? I,ve attached image for my proplem when i sent mail

    i,ve a new issue when i sued a new mail service with Google Workspace as a Smarthost i,ve added * smtp-relay.gmail.com::587 via Smarthost support
    0
  • cPRex Jurassic Moderator
    That does seem like the correct format according to our guide here:
    0
  • akramalsaidi9
    That does seem like the correct format according to our guide here: SMTP relay service error messages - Google Workspace Admin Help c60-20020a509fc2000000b0050b79c70b9bsm972383edf.22 - gsmtp
    0
  • cPRex Jurassic Moderator
    Thanks for the additional details. That message is pretty clear about needing to register the IP address with Google before that smarthost configuration will work properly. If you have already done that, you'll have to reach out to Google support directly to see why that issue is happening, as that isn't something you'll be able to fix on the server side.
    0
  • mtindor
    Port 587 is a TLS submission port that requires authentication. Any mail sent to port 587 must be authenticated with a Google email address/password. Sounds like you have no authentication in place.
    0

Please sign in to leave a comment.