• 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.

Plesk CP -> IP Address Screen Inaccurate

G

gckorn

Guest
Our 9.2.3 Plesk IP Address screen (Home -> IP Addresses) has become inaccurate. Specifically:

1. While 400 domains share 1 IP address, the IP Addresses screen is showing that 321 domains are on one IP while the remainder are on another IP. This is inaccurate. However, when checking domain by domain, each specific domain is accurate.

2. On an exclusive IP address, the IP Addresses screen is showing that many domains are on the same IP, even though there is only one. However, if you go to the next screen, "Domains using exclusive IP address xx.xx.xx.xx," then it shows the full 100+ domains using it, though the true and only domain using that IP is darker and apparently set as "default." Again, only 1 domain should be showing. Again, when checking domain by domain, each specific domain shows the correct IP address.

3. The other day, on the IP Address screen, one IP address (which had been exclusive) required "Repair," (and in fact the domain using it was blocked until the repair happened). The Repair function did work, but it then converted the IP to shared.

Any thought on this? And how to correct it? SoftLayer has rebooted the server (to no avail) and now wants to run Plesk Reconfigurator, without knowing whether that will work. My concern with running Reconfigurator is that it could well cause other setting issues (i.e., resetting things to a default status, thereby upending the desired setting).

Thx,
Gary
 
Repair Option Unsuccessful

FYI - The repair option specified here - http://forum.parallels.com/showthread.php?t=68624 - was attempted but did not work.

So the bottom line is that, while all IP address resolve properly and are properly stated when viewed domain by domain, the information on Plesk Control Panel -> Home -> IP Addresses Management screen (and deeper screens within that) is wrong.

Gary
 
Yes, it is old bug and it was fixed for both Win and Lin Plesk versions. There was incorrect sql request for counting and it was corrected. I can suggest you enable mysql logging and try to find selects in mysql log for counting domains for IPs. Maybe it will help to find a reason why it is incorrectly counted. As I know correct selects should be something like:

SELECT h.ip_address_id as id, COUNT(h.dom_id) AS hostings FROM hosting h GROUP BY h.ip_address_id;
SELECT f.ip_address_id as id, COUNT(f.dom_id) AS hostings FROM forwarding f GROUP BY f.ip_address_id;

But note that it is just common selects and in your case it can not be exactly the same.
 
any change in IP Address Manager display parameters?

Has any change been made in how domains get listed under IP Address Manager on Plesk CP?

It has been stated to me by tech folks that even though a domain is exclusive to IP 1.1.1.1, if other domains have NS records pointing to that IP, then they too will be listed under the same exclusive IP address on IP Address Manager.

Also, though the registrars for all domains point to the same NS records for all domains hosted on the server, I'm now seeing at least 3 different combinations of NS records showing on the Plesk control panel DNS settings for these various domains. I'm seeing:

ns1.nameserver.com
ns2.nameserver.com (correct)

ns1.1.1.1.1.com (an exclusive ip address)
ns2.1.2.3.4.com (a different exclusive ip address)

ns1.1.2.3.4.com (an exclusive ip address)
ns1.15.6.7.8.com (ditto)

Gary
 
Back
Top