• 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 Unexpected IP in allow-transfer in /var/named/chroot/etc/named.conf

mr-wolf

Silver Pleskian
Plesk Guru
Several years I created a script to check the domains for which I'm running authoritative DNS.
This includes checking the IP's in "allow-transfer" for each domain to see if they can successfully resolve the A-record.
It's been a while that I ran this script.

I have 1 Plesk-server dedicated to DNS. I like Plesk's DNS panel, but I don't like having each Plesk server to run DNS and let it control the domains that are running on it.

I know both the advantages and disadvantages of doing so.

Only the primary DNS-server is running Bind controlled by Plesk.
I have configured a slave DNS with "bind" on another Plesk server, but that DNS-server is not controlled by Plesk.

On the Primary server I'm running the extension: "Slave DNS Manager 1.9.1.0" where I have configured that Slave DNS-server.

Primary DNS server's IP: 12.12.12.10
Secondary DNS server's IP: 40.40.40.10

Only the IP 40.40.40.10 is configured in "Slave DNS Manager"

However....
In /var/named/chroot/etc/named.conf I have 2 entries in allow-transfer for each and every domain. It should only contain 40.40.40.10, but it also has another IP of a Plesk server.

allow-transfer {
20.20.20.20;
40.40.40.10;

This IP 20.20.20.20 is another Plesk server of mine, but I have no idea why it is listed in named.conf
It is not even running DNS
It is however a server of mine, so it's not really making it up.
What I did notice is that this 20.20.20.20 is configured as the standard A-record in the template I'm using.
But I don't understand why it is adding that IP to allow-transfer. Most of my domains don't have anything to do with the Plesk server on 20.20.20.20 and are running on other Plesk servers of mine.

The 20.20.20.20 wasn't on all records, but after I did a 'plesk bin repair --dns -y -v' all the domains are filled now with "allow-transfer { 20.20.20.20; 40.40.40.10;}"

Why?????

 
Back
Top