• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

Issue DNS multiple entries for 0.0.127.in-addr.arpa

sirstone24

New Pleskian
Server operating system version
Ubuntu 24.04.1 LTS
Plesk version and microupdate number
8.0.66
Hello, I have encountered an issue where the /etc/named.conf contains multiple entries for the DNS zone 0.0.127.in-addr.arpa. Plesk automatically overwrites the configuration, so deleting the entry is only a temporary solution.

I am encountering a recurring issue with Plesk. The platform repeatedly adds multiple entries for the DNS zone 0.0.127.in-addr.arpa in the BIND configuration file. This results in BIND failing to start due to the detection of duplicate zone definitions.
 
Why do you have a config for local host? Plus /etc/named.conf should be a symbolic link to /etc/named/run-root/etc/named.conf so make sure that one is correct which would have the following entry:

Code:
zone "0.0.127.IN-ADDR.ARPA" {
        type master;
        file "localhost.rev";

But you should not have a 0.0.127.in-addr.arpa in /var/named/run-root/var and if you do check your IP address settings in plesk to make sure that 127.0.01 (or any of that variety) isn't in there.
 
For your Information.

/etc/named.conf:

Code:
// $Id: named.conf,v 1.1.1.1 2001/10/15 07:44:36 kap Exp $

// -- THE FOLLOWING LINES WERE GENERATED BY PLESK. IF YOU MODIFY THEM, THEY WILL BE OVERWRITTEN WHEN THESE SETTINGS ARE MANAGED IN PLESK UI. --
options {
        allow-recursion {
                localnets;
        };
        include "/etc/named-user-options.conf";
        directory "/var";
        pid-file "/var/run/named/named.pid";
};

key "rndc-key" {
        algorithm hmac-md5;
        secret "G3g7ptzWItVIe9pbtauqu66qfpa2DPtSzphNX1zpTAY=";
};

controls {
        inet 127.0.0.1 port 953
        allow { 127.0.0.1; } keys { "rndc-key"; };
};

zone "." {
        type hint;
        file "named.root";
};

zone "0.0.127.IN-ADDR.ARPA" {
        type master;
        file "localhost.rev";
};
// -- END OF LINES GENERATED BY PLESK. --


// -- PLEASE ADD YOUR CUSTOM DIRECTIVES BELOW THIS LINE. --
// ...
// -- END OF YOUR CUSTOM DIRECTIVES. --
// -- ALL LINES BELOW WERE GENERATED BY PLESK. IF YOU MODIFY THEM, THEY WILL BE OVERWRITTEN WHEN THESE SETTINGS ARE MANAGED IN PLESK UI. --

zone "XXX.ip6.arpa" {
        type master;
        file "XXX.ip6.arpa";
        allow-transfer {
                common-allow-transfer;
        };
};
zone "XXX.ip6.arpa" {
        type master;
        file "XXX.ip6.arpa";
        allow-transfer {
                common-allow-transfer;
        };
};
zone "XXX.ip6.arpa" {
        type master;
        file "XXX.ip6.arpa";
        allow-transfer {
                common-allow-transfer;
        };
};

Following by the zones of the Domains.
And it is exactly here in the domain zones that Plesk keeps adding this. Accordingly, I have, of course, checked if 127.0.0.1 is entered in Plesk for this, but this is not the case. Indeed, there was yet a problem after the update to the latest version of Plesk.
 
OK but did you checked if you have 0.0.127.in-addr.arpa in /var/named/run-root/var by chance? And if you do did you tried deleting or renaming (to something like 0.0.127.in-addr.arpa.bak) that file and see what happens?
 
There is actually an entry there. Deleting did not help. The renaming was not successfully (It didn't help) (0.0.127.in-addr.arpa.bak).
However, it was not created again under 0.0.127.in-addr.arpa in /var/named/run-root/var.

bind status displayed the following:
Code:
/etc/named.conf:229: zone '0.0.127.in-addr.arpa': already exists previous definition: /etc/named.conf:28
Jan 19 19:02:21 xxx.xxx.de named[1305061]: /etc/named.conf:248: 'auto-dnssec' option is deprecated and will be removed in BIND 9.19. Please migrate to dnssec-policy
Jan 19 19:02:21 xxx.xxx.de named[1305061]: /etc/named.conf:258: 'auto-dnssec' option is deprecated and will be removed in BIND 9.19. Please migrate to dnssec-policy
Jan 19 19:02:21 xxx.xxx.de named[1305061]: reloading configuration failed: failure
Jan 19 19:02:21 xxx.xxx.de rndc[1308269]: rndc: 'reload' failed: failure
Jan 19 19:02:21 xxx.xxx.de systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE
Jan 19 19:02:21 xxx.xxx.de systemd[1]: Reload failed for named.service - BIND Domain Name Server.



Furthermore, It is interesting that it is each time created under a different domain.

Code:
zone "0.0.127.in-addr.arpa" {
        type master;
        file "0.0.127.in-addr.arpa";
        allow-transfer {
                common-allow-transfer;
        };
};

After deleting the entry in /etc/named.conf and restarting bind:

Code:
sudo systemctl status named
● named.service - BIND Domain Name Server
     Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/named.service.d
             └─plesk.conf
     Active: active (running) since Sun 2025-01-19 19:08:02 UTC; 3min 7s ago
       Docs: man:named(8)
   Main PID: 1309157 (named)
      Tasks: 8 (limit: 28742)
     Memory: 6.6M (peak: 7.2M)
        CPU: 44ms
     CGroup: /system.slice/named.service
             └─1309157 /usr/sbin/named -f -t /var/named/run-root -c /etc/named.conf -u bind -n 2
 
Back
Top