Reverse DNS lookup (rDNS)
What is rDNS for?
First of all, it is simply necessary to set up sending corporate mail from your own server. If the server's IP address does not have an entry in rDNS, then all mail servers will refuse to accept messages from you at the beginning of the session. As a result, you will get errors related to this problem, for example,
550 Your IP has no PTR Record.
<aside> 💡 If you're using Office 365 to manage your DNS records note that PTR record creation and management isn't supported by the Office 365 interface, in which case you'll have to change your DNS management to a DNS host outside Office 365. Refer to this article for instructions on how to do this: Change how DNS records are managed with Office 365
</aside>
550 is the standard code of the SMTP mail server, which reports a critical error in the mail session. The text that follows the error number explains to the administrator in more detail the reason for the error.
Setting up rDNS for an IP address is mostly handled by the hosting provider that owns the corresponding block of IP addresses. Therefore, to configure a reverse DNS query, contact technical support.
It is important to remember that the name of the IP address of the mail server, and especially the corporate mail server, should be given carefully. A good name for a mail server can be a name like: mail.domain.ua, mxt.domain.ua, mx.domain.ua, and others. For example, the name *host-27.990-454.domain.ua* will not be suitable and convenient. And most likely such a name will fall under the spam filter of the client.
Using a reverse DNS lookup greatly reduces spam, as messages from non-rDNS IP addresses are simply rejected by the mail server. In fact, this is the most effective and least expensive way to protect users from spam. So you should configure reverse DNS lookup to send your mail so that mailers do not consider it spam.
Depending on the type of mail server, the presence of rDNS is checked in different ways, for example: