• 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.

PTR record im DNS skeleton

F

flupke

Guest
is it necessary to have that PTR record for each domain? it leads to confusion when reversing the IP address, as example in a received email header:

Received: from i02m-87-89-226-64.d4.club-internet.fr (87.89.226.64)
by XXXXXXXXXXXXXxx with SMTP; 10 Feb 2008 15:48:27 -0500


The XXXXXX being ONE of the domain hosted on my plesk server. The XXXXX changes everytime (BIND probably round rubbing)

I want only my hostname to be returned

I want to remove the PTR record from the DNS skeleton, could this lead to other side effects?

Thks!

Flupke
 
You must log in or register to reply here.

Similar threads

falconsi
Resolved PTR Record resolved, what to do for various domains?
Replies
7
Views
22K
EmperorFPI
E
Y
Question Proper rDNS records for multiple domains under same IP
Replies
6
Views
18K
weltonw
W
S
Resolved PTR DNS record and email going in to SPAM (can't wrap my head around it)
Replies
2
Views
5K
seqoi
S
C
Issue Bad DNS PTR resource record
Replies
0
Views
4K
CupTea
C
Dukemaster
Resolved DNS PTR Problem, Could not find reverse address for IP
Replies
4
Views
6K
Dukemaster
Dukemaster
Back
Top