Creating new account with subdomain of another account

Hi all,
One of my customers with a domain on a Windows-plan wants to create a new account with me on a Unix-plan.
They want to use a subdomain on their Windows-plan-account as the domainname of the new Unix-plan account.

They signed up, but when I click on create (in moderation menus) it says “Failed to add account xxx Zone xxx.yyy.zz has been taken”

My question is can I create a new account using a 3rdlevel domain of my service-account, and ask support to add the subdomain of my customer manually to the Unix-plan as an alias?

Or does this give major problems?

Thanks for your tips/help/suggestions!

you will have to add it using 3rd level of service domain, because 3rd level of client doesn’t work. another option without our input would be dedicated IP and in the windows plan, custom A record for subdomain to the IP.

Hi Stephen,
Thanks for the reply.
I created now an account using 3rdlevel domain of service-account. Dedicated IP in Windows plan is not needed by me, so i prefer to keep it shared.

I created an external DNS for the customer-domain, and hope that helps.

Can jodo add a ‘Server Alias’ to a unix account? (probably directly in configfile?)
See example below.

Thanks for replies!
Kind regards, Jan-Pieter

[FONT=“Courier New”][SIZE=“1”]
<VirtualHost 64.71.235.49:80>
ServerAdmin [email protected]
DocumentRoot /hsphere/local/home/account4/unixaccount.servicedomain.com
ServerName unixaccount.servicedomain.com

ServerAlias subdomain.windowsdomain.com
[/SIZE][/FONT]

I don’t think it will help as webserver won’t respond with correct site, unless there is a host header match.

Any changes we do manually on webserver side won’t help, as Hsphere reposts entire config on every change (only for Linux side).

So what’s the solution then to this problem? Or is the only solution hosting this subdomain elsewhere?
Regards, Jan-Pieter

Yes, the subdomain has to be hosted outside Hsphere, if it can’t be hosted on Windows.

That’s very very sad to hear. Changing the configfile and put it to readonly (or change ownership so that hSphere cannot overwrite it) is not a bypass you can use?

No, the only way to make it work within Hsphere will be dedicated IP.