• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Reverse DNS question

B

BillThyCat

Guest
I have a partial subnet x.x.x.64 - x.x.x.127 its a 255.255.255.192 subnet.

I have the DNS server on that subnet listed as my reverse DNS server with my upstream ISP.

How do I get Plesk to create the correct in.arpa file for a partial subnet?

Will Plesk even do this?

Thanks,

Tim Schafer
 
No tricks will help but manually add in.arpa entries in named.conf and creating zone file (BIND) or create it manually through mmc console (MS DNS)
Don't forget to remove ptr entrie from domain template in Server-DNS

John S.G.
 
Re: Re: Reverse DNS question

So if I add the zone info to the header file in named.conf (the file that contains static content), and then remove all PTR records from Plesk?

I don't use MS DNS, just bind. I think what I said above may work, I already have a created file, and since the static part should never change (I don't host any web servers on the partial subnet) it should never need to be changed. It just might work.

I'll try in the morning and see how it works.

Thanks,

Tim Schafer


Originally posted by JackL
No tricks will help but manually add in.arpa entries in named.conf and creating zone file (BIND) or create it manually through mmc console (MS DNS)
Don't forget to remove ptr entrie from domain template in Server-DNS

John S.G.
 
Back
Top