For non mail servers rDNS or PTR records aren't important.
Historically, PTR records prevented outbound SMTP servers from being blocked by spam filters. However, more modern DNS records "SPF, DKIM, and DMARC" provide better verifications of domain ownership. PTR records specify the allowed hosts for a given IP address. They are the opposite of A records and used for reverse DNS lookups.
How to set up only if you are using your server as mail server. You don't need to set up reverse DNS is
To set a reverse DNS (rDNS or PTR) entry for a cloud server, you first need to log into Cloud panel and click Server Tab and then click Networking sub tab. Once you're there, select your IP4 or IP6, you can edit the rDNS entry. You should not use the naked domain name, but a subdomain of your domain name. Otherwise you'll run into a host of other problems. Don't forget to create a CNAME for the subdomain like server.example.com. You should have A record for your naked domain name like example.com.
The A record for 'server.example.com' should point to the IP of your server, and the PTR record for this IP address should match the hostname.
server.example.com. A 82.197.45.124
124.45.197.82.in-addr.arpa. PTR server.example.com
Important Note for Sellcloud users:
For Reverse DNS you do not need to do anything or edit if you are using Mail services (such as SendGrid, MailChimp or others) or Email providers (such as Zoho Mail, Gmail, Hotmail, et cetera)
RDNS is helpful if you are setting up your own mail servers which we do not support as it has many risk involved. For more info on RDNS, check our knowledgebase IPV4 RDNS or IPV6 RDNS
Alert: For Control Panel Help & Tutorials, click here: Panel Tutorials
