• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

rDNS and Plesk

omexlu12

Basic Pleskian
Hello,

Because GMX and WEB block generic rDNS like XXXXXXX.yourvserver.net i want to change the rDNS now that the mails to GMX and WEB can get submitted.

Now my question:
I have a A-Record (mail.domain.tld > SERVERIP), is it now enought to change the rDNS on my provider panel or i need also to change some configs in plesk panel oder config files?

What exactly must i do now?

Thanks in advance.
 
Hello,

Changed the hostname from a generic hostname to 'fully qualified domain name' and set the rDNS to the same domain ex. server.domain.tld

After that i set the DNS correctly and gmx and web accept again the emails :D
 
Hello,

Changed the hostname from a generic hostname to 'fully qualified domain name' and set the rDNS to the same domain ex. server.domain.tld

My Hoster is Strato, so i have only to change the DNS-Reserve in my Controlpanel from xxxxxx.stratoserver.net to mydomain.de?
 
You need the following:
- A-RECORD (example: mail.domain.tld) pointed to your serverip
- change the hostname in plesk panel under settings
- Change the DNS-Reverse to this domain (mail.domain.tld)
- ajust if needed some DNS settings

After that wait a bit (max. 24-48 hours, maybe earlier) and the mails gets accepted by GMX and WEB :D

PS. Sry for my bad english, i hope you understand :D
 
@omexlu12,

In essence a "golden oldie", i.e. an old and known solution.

However, in the whole process, there has been some error in the line of reasoning: it is not about a correlation between rDNS and mail (in general) or mail.domain.tld (in specific).

In essence, all that you have to do is the following:

- use a domain that is owned, registered and manageable by you,
- create a subdomain, with an A Record pointing to the IP, assigned to the server,
- use Plesk Panel to change the hostname to the (full) name of the subdomain (note: the use of the Plesk panel is convenient, since it will make the hostname persistent across reboots)

and this way, one realises a solution (similar to your solution), that is "fairly clean".

Reverse lookups by means of PTR records are then handled by the servers of the hosting provider, while the A Record is allowing mail servers to do a "normal" association of IP and the sending mail server, as required.

Finally, note that you wouldn´t have this problem if the hosting provider would have configured the routes of mail traffic properly.

Regards....
 
Back
Top