2 hostnames, 2 websites, same domain, not possible?

[Jayn]

Hi, I've setup a domain in Plesk 9.2.2 we'll call example.com. The plesk server is also the primary DNS server. example.com and www.example.com both land the user at /var/www/vhosts/example.com/httpdocs as expected.

Now, I want to have a new site: secondary.example.com. If I add this to the DNS for example.com, I can't create a domain of the same name and/or vice versa.

If I try to create the domain before the DNS it insists on creating a subdomain.

Is there a more straightforward way to do this?

 

[Andrey Kucherov]

Hello,

Please clarify what is the purpose of the secondary.example.com - does this should be a subdomain or a separate domain with its own DNS records.

 

[Jayn]

The purpose is to have a website at secondary.example.com that is different from the website at [www].example.com.

If I wasn't using plesk, I'd simply add an A record for secondary.example.com in the example.com zone and I'd configure a new virtual host under apache.

Unfortunately, it's not that simple in Plesk. I don't understand the difference between a subdomain or a separate domain as they both seem to create additional NS records for secondary.example.com under example.com and then creating another zone file, which I seemingly have to setup under my secondary DNS server as well. It seems extremely convoluted. Is this a limitation of using Plesk?

What is the recommended Plesk approach to this task?

 

[atomicturtle]

You'd want to use a subdomain for your configuration, basically that is going to automatically add the A record to the existing example.com TLD and set up a separate httpdocs for secondary.example.com under /var/www/vhosts/example.com/subdomains/secondary/httpdocs/

 

[jaydisc]

Hi, that works much more as expected. Thank you.

For the parent domain, the admin user has an sftp(chrooted) shell as I only like giving users SFTP access (I've disabled FTP). For this subdomain, I can define a user to go with it, but it seems to be limited to FTP. Is this just a limitation of the GUI? Can I go into the back end MySQL or config files to make that user a chrooted SFTP user?

Alternatively, can I create an ADDITIONAL SFTP user at the parent domain and limit it to the subdomain directory?

Thanks again.

 

[atomicturtle]

Thats just a limitation of the GUI, you can still go into the users home dir to manage keys, permissions, etc and all that the normal way. Personally I use the "scponly" shell, which has its own internal logging and chroot functionality so I end up doing all that manually anyway.

 

[jaydisc]

Sweet. Thanks again.