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

Left over domain.com in named.conf

Lloyd_mcse

Silver Pleskian
Plesk Guru
Hi guys,
I've been trying to resolve an issue on one of my servers running Ubuntu 12.04.5 LTS, i originally installed Plesk 11.5.30 and upgraded to Plesk 12 a couple of weeks ago.
Long story short I notice there are some left over zones in named.conf...

Code:
zone "domain.com" {
    type slave;
    file "s/domain.com.bak";
    masters {
        192.168.1.1;
    };
};

zone "0.168.192.in-addr.arpa" {
    type slave;
    file "s/0.168.192.in-addr.arpa.bak";
    masters {
        192.168.1.1;
    };
};

And no that is not sanitised, that's exactly how it is in the named.conf file.
Obviously I don't have a domain called domain.com and 192.168.1.1 has never been our internal network or router IP.

Looking in /var/named/run-root/etc/named.conf.default it contains the same zones.

I have just removed the zones from named.conf, and restarted bind.

I assume it's a bug, so thought I should post the info.
Regards

Lloyd
 
Back
Top