• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Plesk continues to write deleted slave DNS server in /var/named/chroot/etc/named.conf

mr-wolf

Silver Pleskian
Plesk Guru
I have a Plesk server which I use as authoritative server for all my clients. On my other Plesk servers I have not installed the DNS-option of Plesk.
The advantage of this is that I have all DNS in one place which also allows me to do some creative things.

On that server, ns6.<mydomain>, I have installed the "slave DNS manager" in which I configured ns5.<mydomain> as a slave server.
On ns5.<mydomain> I have installed bind and configured it as a slave DNS-server for ns6.<mydomain>.
This bind is therefore independent of Plesk.

This is all working fine.
2 years ago I decided to add a 2nd slave DNS-server on ns4.<mydomain> and configured this in my extension.
But because I didn't want to change all the nameservers in the Internet-registry I abandoned the idea.
I deleted the IP (81.14.147.34) of the ns4.<mydomain> in Plesk's "slave DNS manager" and thought it was ok.

Only recently did I find out that Plesk is still writing the IP (81.14.147.34) of ns4.<mydomain> in the section "allow-transfer" of /var/named/chroot/etc/named.conf

I can use sed to correct this by issuing
Bash:
sed -i '/81.14.147.34;/d'  /var/named/chroot/etc/named.conf
killall -HUP named

Each modification of DNS will add the IP of ns4.<mydomain> in allow-transfer.
Where does it get that data????

So entries in /var/named/chroot/etc/named.conf should look like this:

Code:
zone "client.com" {
        type master;
        file "client.com";
        allow-transfer {
                84.203.11.86;
                common-allow-transfer;
        };
};

But recently modified domains look like this and named will try to push the zone to a DNS-server which I haven't configured for this anymore.

Code:
zone "client.com" {
        type master;
        file "client.com";
        allow-transfer {
                81.14.147.34;
                84.203.11.86;
                common-allow-transfer;
        };
};

In the folder /usr/local/psa/var/modules/slave-dns-manager there is only 1 file and that's slave_84.203.11.86.conf

Which code is still pushing 81.14.147.34 into the allow-transfer sections?
Where can I alter a file or database entry to stop this??
 
Last edited:
Back
Top