Question

NO reverse RTR detected?

When I test my domain dns in intodns.com (after adding spf record) I found the following error in the “Reverse MX A records (PTR)” section

Reverse MX A records (PTR) ERROR: No reverse DNS (PTR) entries. The problem MX records are: 158.146.241.192.in-addr.arpa -> no reverse (PTR) detected . You should contact your ISP and ask him to add a PTR record for your ips

What is the solution for this?

Thanks for help in advance.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

No, wait until the PTR record propagates and run that intodns.com check again.

I have renamed the droplet to as7.domainname.com , now do I have to change the A records in DNS? <br> <br>Thanks

Your droplet’s hostname is ‘as7’. You have to rename to as7.domainname.com using our control panel.