Skip to main content

Comments

13 comments

Date Votes
  • quietFinn

    your screenshot link does not work.

     

    0
  • Ahmed Hamdy
    • Edited

    quietFinn I updated the URL in the post, kindly recheck it.

    https://ibb.co/42dkC4z

    0
  • cPRex Jurassic Moderator

    I do not see that there is any reverse DNS configured for the hostname at this time.  Did you have your hosting provider add those records?

    0
  • Ahmed Hamdy

    Yes, the Reverse DNS is added properly as you can see here: https://mxtoolbox.com/SuperTool.aspx?action=ptr%3a142.171.234.170&run=toolpage

    0
  • mtindor

    rDNS is added and functioning.   Just relax and check the cPanel interface for that domain tomorrow.   It is very likely that the resolvers you have listed in /etc/resolv.conf simply have cached your previous lookups and you have to wait til the DNS cache expires before the server will show that rDNS is in place.

     

     

    0
  • cPRex Jurassic Moderator

    I also see it working on my end now, so I would agree with mtindor

    0
  • Ahmed Hamdy

    Thanks mtindor and cPRex for your lookup.

    But please note that my server is not new to wait 1 more day, I established it 1 month ago

    0
  • cPRex Jurassic Moderator

    Is WHM still giving you an error about that reverse DNS configuration?

    0
  • Ahmed Hamdy

    cPRex Yes, this error exists since I created the server 1 month ago till now.

    0
  • cPRex Jurassic Moderator

    I'm wondering if this an issue with the local resolvers on the server.  Just as a test, you could run this command from the server itself to see if that returns the correct value:

    dig -x 1.2.3.4

    where "1.2.3.4" is the IP address of your server.

    If that works well, you may want to try adjusting the resolvers on your server to use the Google public resolver as a test to see if that improves the information in WHM >> Email Deliverability.  You can do this by editing /etc/resolv.conf on the server and add the following line:

    nameserver 8.8.8.8

    If that does get things working, you'll want to contact your host to let them know there is an issue with the resolvers.

    0
  • Ahmed Hamdy

    I'm already using Google DNS (8.8.8.8) and (8.8.4.4). Check this screenshot: https://ibb.co/4FTJLK7

    I used this command 

    dig -x 142.171.234.170

    and this is the output: https://ibb.co/D7kh6x7

    I already contacted my server provider, and they confirmed that PTR is resolving properly and regarding the error in WHM, I need to contact cPanel support.

    0
  • cPRex Jurassic Moderator

    Are you able to submit a ticket to our support team?

    0
  • Ahmed Hamdy

    Ok I will. thank you

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post