• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Reverse DNS records in /var/named/chroot/var in-addr.arpa files

Miguel_Tellería

Basic Pleskian
Platform: Plesk 12.0.18, CentOS 6, historically migrated from a Plesk 11 version.

Dear all,

When I do a dig -x <IP_address> from the server I get several outdated results due to PTR bind files (nnn-nnn-nnn.in-addr.arpa) that sit on the /var/named/chroot/var directory and are referenced from the /var/named/chroot/etc/named.conf file.

Looking in the psa database, I only find the PTR record for the FQDN of the machine in the table dns_rec. The other records do not appear even when editing the DNS zones that they reference to in the panel.

I would like to know how can I remove those records:
- Can I just remove them from the named.conf file and erase the files?
- is there a CLI tool to repair this?

Thank you n advance for your suggestions.
 
Look at dns utility:

# plesk bin dns --help

You can try to restore the default resource records for a domain's zone based on the Plesk server DNS zone template with --reset option. After that you can modify zone as it is required.
 
Thanks Igor for your suggestion, but at the end I removed the files and removed the in-addr.arpa zones in named.conf ignoring the warnings of "DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED"

I left the zone with the FQDN though since it appears in the database and it seems to be low-level hardcoded into Plesk.

So far Plesk has respected my modifications by no adding those removed zones again.

I tried later your approach (resetting the zone) but it didn't do any change. It restored the template alright but the PTR addresses didn't come up (fortunately).

So I will stay like this for the moment.
 
Back
Top