Registration of a PTR record smtp.reatra.com is necessary for the ip address 81.171.225.123. Although 'A' records are present and functioning, the smtp server can't send emails as other mail servers (mail.ru) reject them due to the absence of a PTR record, implying the possibility of spamming.

The user added a DNS server entry that reads:

123.125.171.81.reatra.com.        IN    PTR    smtp.reatra.com.

However, the ptr check fails, stating that there are no records of a PTR at 81.171.225.123. The general consensus suggests that the PTR record should be made by the hosting provider of the allocated IP address rather than the domain name registrar. If the user has personally assigned VDS on the IP, should the hosting provider oblige to make the PTR record, or can they refuse? Unfortunately, the answer to this question is currently unknown.

The whois database shows that the ip address 81.171.225.123 belongs to the range of addresses delegated to Eweka Internet Services B.V. organization. Therefore, they should be contacted regarding the ptr record.

However, in practice, a third-party organization such as a provider is likely the one that connected the machine to the network. Contacting this organization is necessary, and they will redirect the request accordingly.

It is commonly advised that the hosting provider who owns the IP address create the PTR record rather than the registrar of the domain name; this is accurate with some minor exceptions. The provider will most likely redirect the request to the organization which manages the IP address range. In any case, it is important to get in touch with the provider who connected the computer to the internet.

The PTR record is established on the NS server responsible for your domain. If you are using ns3-l2.nic.com, it's done through NIC.com. Is the configuration done using a text file or website forms? Is there a single command to create a reverse domain record?

Here's an example of a proper PTR record:

123.125.171.81.in-addr.arpa.    IN    PTR    smtp.reatra.com.

It is usually the responsibility of the provider to specify the PTR record; however, they have the right to decline it.

In the case presented, the user is encountering difficulty with setting up a PTR record for the IP address 81.171.225.123, which is essential for email delivery due to the rejection of emails by other mail servers like mail.ru. The absence of a PTR record raises concerns about potential spamming activities and impacts the ability of the SMTP server to send emails effectively.

The user's attempt to add a PTR record through a DNS server entry has resulted in failure, as the check indicates the absence of records at the specified IP address. This situation highlights the importance of understanding the hierarchy of control and responsibility in managing PTR records.

Typically, the entity responsible for IP address allocation, such as the hosting provider or ISP, is tasked with creating and managing PTR records. If the user has personally assigned a Virtual Dedicated Server (VDS) on the IP, the hosting provider may still have the obligation to manage PTR records, especially if they have control over the IP address space. However, there are cases where hosting providers may refuse to create PTR records due to technical limitations, policy restrictions, or other valid reasons.

It's crucial for the user to engage in detailed discussions with the hosting provider to clarify the specific responsibilities and arrangements regarding PTR records. Understanding the provider's stance on PTR record management and any potential alternatives is essential to resolving the issue effectively.

In the event that the hosting provider refuses to create the PTR record, the user may need to consider alternative solutions. This could involve exploring the possibility of obtaining a different IP address with PTR record support or leveraging third-party email relay services that can mitigate the impact of PTR-related issues.

However, the practical reality is that the machine's IP is assigned by a downstream provider or ISP who handles PTR changes. Contacting the hosting provider that assigned the IP is the fastest route, they'll either update the PTR or escalate internally.

Domain registrars cannot modify PTR records since those are linked to IP address blocks, not domain names. In short, the correct workflow is to engage the network operator managing the IP allocation, not the domain registrar.