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

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