• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Setup Reverse DNS

D

Daemoncat

Guest
Hi There

I am having trouble configuring the server to respond to reverse DNS request. My ISP has delegated control of reverse DNS to my server, and I have several PTR records for different domains with the ip address in them. Doing an NSLOOKUP against my server shows the PTR records there, but doing a reverse DNS lookup from www.dnsstuff.com and I get the message "Reports that no PTR records exist ".

I'm probably missing something simple. Any ideas?
 
I'm not sure that's the right way to go about it. Normally the provider of the IPs *HAS* to put the reverse dns records in place. It isn't just about PTRs in the DNS of the domain itself.

I'm sure someone will correct me if I'm wrong.


Faris.
 
Back
Top