• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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