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

BIND is binding to the wrong IP address

mgreen

New Pleskian
Hello,
We are using this server as the DNS master/SOA. We are using BIND. The server is behind a firewall that is doing NAT. I expected BIND to use the address the Plesk server uses -10.10.1.20 lets say - as its primary. BIND does not use that address. It uses 10.10.1.15 which is also assigned to the same server NIC but was added later. If I remove the 10.10.1.15 address from the NIC then BIND uses the next highest IP address in the list i.e. 10.10.1.16 assigned to the NIC.

I don't know if this is as a result of a Windows server problem with IP address sourcing and binding when more that one IP address is assigned to a NIC, or if Plesk is just not assigning or using the expected IP address to configure the BIND service.

Panel Version - 11.5.30 Update #51
Microsoft Windows Server 2012
 
Back
Top