• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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