What the hell came over you in changing subdomains?

[Chris_O]

As the name says subdomains are sub the main domain.

With the new handling for subdomains the DNS is abused and against all RFC.

Setting up a domain is getting worser than ever. As you have to use 2 nameserver you will have to create slave zones for subdomains. As this can't be done via CP for each subdomain a customer creates an admin has to do something.

Ever considered domains with 100+ subdomains????

Point is you are fixing things that are not broken and keep things broken which should be fixed.
I updated to 10.4.4 yesterday on 3 servers.
Server 1 no problems
Server 2 had to use bootstrap -repair
Server 3 Plesk is broken -> tried repair -> no chance -> tried uninstall by script -> reinstall hangs same place -> no entry in logfiles.

Module userdir already enabled
Module dav already enabled
Considering dependency dav for dav_fs:
Module dav already enabled
Module dav_fs already enabled
Module auth_digest already enabled
Module authz_user already enabled
Module dav_lock already enabled

this stays for ages and no progress.

So fix the broken things and bring back normal subdomain handling.

quite pissed

Chris

 

[Chris_O]

Did I expect an answer from parallels? Not really ...

 

[IgorG]

Subdomain's behaviour can be switched from New behaviour (own zones) to Old behaviour (А record for subdomain in zone of parent domain). Read article http://kb.parallels.com/en/112966

 

[Chris_O]

what should I say?
server 1 option found not tested yet
server 3 still not working
server 2

/usr/local/psa/bin/server_pref -u -subdomain-dns-zone parent Unrecognized option: '-subdomain-dns-zone'

checked psa misc -> no entry
added manually

mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa -e 'select * from misc where param = "subdomain_own_zones"'
+---------------------+------+
| param | val |
+---------------------+------+
| subdomain_own_zones | true |
+---------------------+------+

tried to change now-> Unrecognized option
changed manually:

+---------------------+-------+
| param | val |
+---------------------+-------+
| subdomain_own_zones | false |
+---------------------+-------+

behavior still new.

Again my question, why fix something which is not broken???

 

[IgorG]

What version of Plesk and MU you have? Check it with

# cat /root/.autoinstaller/microupdates.xml

On my test server:

# cat /root/.autoinstaller/microupdates.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<patches>
<product id="plesk" version="10.4.4" installed-at="20111110T011622">
<patch version="25" timestamp="" installed-at="20120410T053641" />
</product>
</patches>

# rpm -qf /usr/local/psa/bin/server_pref
plesk-core-10.13.4-cos5.build1013111102.18

# /usr/local/psa/bin/server_pref -u -subdomain-dns-zone parent
SUCCESS: Server preferences are successfully updated

 

[Chris_O]

I have the same values.

It didn't work 10h ago.
Now it seems to work, I changed nothing.

Still does not explain why this has been launched.
Are there no QA or QS @ parallels to avoid such "features"?
Is there any situation where this is needed?

Any hints about the server3 problem, another KB entry which I should know?