Facebook
TwitterHi everyone,
This is just a fyi on the auto update that ran for me on Jan 20th.
Centos 5.7 64bit
php 5.2.x
mysql 5.x
Checking up on customer complaints I found many domains loading default plesk pages. After generating a support ticket I tried various options including what was recommended by support, where I was told I had modified some DNS records that did not update and I should run.
/usr/local/psa/admin/bin/dnsmng --update <domain>
usr/local/psa/admin/bin/httpdmng --reconfigure-domain <domain>
Unfortunately it did not correct the problem. What I found was the default hosting ip address for a domain had changed and its dns was updated by adding new records. However, I made no changes to any dns records prior to the failure. In the end, since I have less than 120 domains on the server, I just went through each one individually with my browser testing who fails. Looking at the DNS on failed I see original zone records and new ones. I changed the hosting ip back to what it was and removed the new zone records and the domain instantly resolved.
I probably could have just removed a set of zone records and dnsmng and httpdmng the domain, but this worked.
Also, I started to get quota rejections on email as new limits of 500mb were suddenly enforced on some domains with mailboxes larger than 1GB. It would appear the hosting service changed?
My worry now is with the minor updates. I requested clarification on how this could happen and I was told minor updates would not cause this problem. Do most people have this option enabled, or disabled?
Regards,
This is just a fyi on the auto update that ran for me on Jan 20th.
Centos 5.7 64bit
php 5.2.x
mysql 5.x
Checking up on customer complaints I found many domains loading default plesk pages. After generating a support ticket I tried various options including what was recommended by support, where I was told I had modified some DNS records that did not update and I should run.
/usr/local/psa/admin/bin/dnsmng --update <domain>
usr/local/psa/admin/bin/httpdmng --reconfigure-domain <domain>
Unfortunately it did not correct the problem. What I found was the default hosting ip address for a domain had changed and its dns was updated by adding new records. However, I made no changes to any dns records prior to the failure. In the end, since I have less than 120 domains on the server, I just went through each one individually with my browser testing who fails. Looking at the DNS on failed I see original zone records and new ones. I changed the hosting ip back to what it was and removed the new zone records and the domain instantly resolved.
I probably could have just removed a set of zone records and dnsmng and httpdmng the domain, but this worked.
Also, I started to get quota rejections on email as new limits of 500mb were suddenly enforced on some domains with mailboxes larger than 1GB. It would appear the hosting service changed?
My worry now is with the minor updates. I requested clarification on how this could happen and I was told minor updates would not cause this problem. Do most people have this option enabled, or disabled?
Regards,
