• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Resolved Slave DNS Manager 1.8

Stein Hoyba

New Pleskian
Hello
We have two plesk servers, and 3 slave dns servers.
They have local ip's that are nat'ed.
It all worked fine until dns manager updated to 1.8. Now they are all red With error 'status rndc: bind socket: address not available.
It looks like it tries to use the Public address to Connect to the slave.

Any way to work around this? I cannot Select anything but the Public ip if I try to remove/add slave.
 
Hello
We have two plesk servers, and 3 slave dns servers.
They have local ip's that are nat'ed.
It all worked fine until dns manager updated to 1.8. Now they are all red With error 'status rndc: bind socket: address not available.
It looks like it tries to use the Public address to Connect to the slave.

Any way to work around this? I cannot Select anything but the Public ip if I try to remove/add slave.

Hi, I have the same problem.
What exactly did you do?

Thank you for answer
 
Back
Top