• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Forward-confirmed reverse DNS failed tnmpmscs

Mark R

New Pleskian
Hi, Can anybody help please

Email rejection error message 'Forward-confirmed reverse DNS failed tnmpmscs'

Plesk is installed on an Ionos VPS
Cloudflare is hosting DNS

Plesk Full Hostname is server.myplesk.com
Ionos Reverse DNS is server.myplesk.com

I have two websites running on Plesk both of which have emails rejected with error 'Forward-confirmed reverse DNS failed tnmpmscs'

Mail-tester.com results.
1) -1.274 RDS_NONE, Delivered to internal network by a host with no rDNS
2) Your server *.*.*.196 ( Plesk IP address) is successfully associated with server.myplesk.com, This may indicate you do not have a rDNS configured for your hostname or the rDNS does not match your sending IP

PTR has been set to the main Plesk IP address of the server, is this correct?
Is this a PTR issue?

Any help would be appreciated
 
Hi,
Typo should read

1) -1.274 RDS_NONE, Delivered to internal network by a host with no rDNS. This may indicate you do not have a rDNS configured for your hostname or the rDNS does not match your sending IP

2) Your server *.*.*.196 ( Plesk IP address) is successfully associated with server.myplesk.com
 
Hi,

server.myplesk.com is not proxied

the entry looks like this
server.myplesk.com.myfirstwebsite.co.uk

All DNS in cloudflare reference my main Plesk IP
 
Hi,

My IP resolves to server.myplesk.com:)

server.myplesk.com resolves to 2 x IP'S both of which are showing as Cloudflare :(

*****

I apologies now fixed...

You asked me to check to see if server.myplesk.com was proxied in Cloudflare but I only checked this in my websites for which I was sending emails from, not the main domain DNS for the server (mypleskserver.com)

mypleskserver.com WAS proxied (now not proxied has fixed the problem)

websiteone.co.uk not proxied
websitetwo.co.uk not proxied

Even though working now, I'm a little confused do I need to put server.myplesk.com in my websiteone.co.uk/websitetwo.co.uk DNS records?

the entry looks like this
server.myplesk.com.websiteone.co.uk


Thanks for your help!
 
Glad to hear you've got it sorted.

Even though working now, I'm a little confused do I need to put server.myplesk.com in my websiteone.co.uk/websitetwo.co.uk DNS records?

the entry looks like this
server.myplesk.com.websiteone.co.uk
No, no need to reference the host name of the server in the DNS zone of your websites. You can safely remove those records.
 
Back
Top