James

TO FIX:
1) login to psa database in Plesk:
Server -> Database Servers -> Local MySQL Server -> Databases tab -> DB WebAdmin

2) load the “psa” database in the database drop down on the left.

3) collect a list of domains by running the following SQL query
SELECT ‘name’ FROM ‘domains’ WHERE 1

You will get something like:

domain1.com
domain2.com

4) recreate each zone for each domain listed in step 3:

INSERT INTO dns_zone (name, displayName) VALUES (‘domain1.com’,'domain1.com’) ;

INSERT INTO dns_zone (name, displayName) VALUES (‘domain2.com’,'domain2.com’) ;

5) collect a list of the “id” numbers for newly created dns_zone, you can run the following SQL query:

SELECT id,name FROM ‘dns_zone’ WHERE 1 ;

you’ll get something like:
7 domain1.com
8 domain2.com

6) update dns_recs table with new id numbers you just collected, set “dns_zone_id” in the following SQL queries to the coinciding id number from step 5

UPDATE dns_recs SET time_stamp = now() , dns_zone_id = ’7′ WHERE dns_zone_id=0 AND (host LIKE “%domain1.com%” OR val LIKE “%domain1.com%”) LIMIT 20;

UPDATE dns_recs SET time_stamp = now() , dns_zone_id = ’8′ WHERE dns_zone_id=0 AND (host LIKE “%domain2.com%” OR val LIKE “%domain2.com%”) LIMIT 20;

7) update the domain records to link the new DNS zones and their associated DNS records to the domains themselves.

UPDATE domains SET dns_zone_id = ’7′ WHERE name = “domain1.com” LIMIT 1 ;
UPDATE domains SET dns_zone_id = ’8′ WHERE name = “domain2.com” LIMIT 1 ;

the www. sub domain will probably not work. we need to fix this.

in plesk “Domains” -> domain.com -> “Domain Administrator”,
uncheck the “WWW” box at the very top of the page, and click OK to save. Then go back and recheck it and save again.

NOTE: you have to do this step for every domain otherwise apache wont restart successfully.

9) restart apache and bind: “Server” -> “Service Management”, and then restart Apache and the DNS service.

Just to warn you, a lot of virtual dedicated server hosts will offer similar support because of the cost of supporting specific configurations of a VPS. Many shared hosts will only upgrade for “critical” updates in the first place, namely because they don’t want to break anything! Anyway, you might be interested to know that GoDaddy has changed their VPS offering and is now giving Plesk 8.0 by default, on Fedora Core 4 systems running MySQL 4 and PHP 5. I’m much more impressed with their current offering. I actually am in the process of using a new GoDaddy VPS to transition content from my old VPS, and use the newer solution for performance and security reasons. However, one thing I would *not* recommend is using GoDaddy VPS for their PostgreSQL support when buying the Plesk Power Pack at $9.99 per month. The PostgreSQL PHP module wasn’t installed when the server was provisioned, and I didn’t have the time to figure out how to install it (and worse, I couldn’t find directions on the Postgres PHP module). But to make things more strange, the Plesk panel itself ran a custom web server that used phpPgAdmin to administer the database server. So somehow, the PHP PostgreSQL module was on the system, except it was only in the control panel’s installation of PHP. I was bummed, and confused. Anyway, despite this experience I’d say GoDaddy’s service is still competitive, so don’t give up hope.