• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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