• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Sub domains as fully hosted domains?

P

Peekay@

Guest
I have been asked to set up several sites as sub-domains. For example, say the registered domain name is 'holidays.com' (sadly it isn't). The client wants separate sites accessible as 'spanish.holidays.com', 'german.holidays.com' etc.

I followed the procedure for setting up a sub domain for 'holidays.com' (e.g. 'german') and then added the sub-domain name to the DNS as an 'A' record and pointed it at the server IP address, e.g.

Code:
DNS for 'holidays.com'

german   A    192.168.***.***

This works fine, but I have no admin controls for the sub-domain in Plesk, e.g. no stats, traffic reports etc.

So... I tried creating a fully hosted domain in Plesk as 'german.holidays.com' and once again added 'german' to the 'holidays.com' DNS as an 'A' record entry. I was pleasantly surprised to find that this works too... plus I have full domain controls - file manager, traffic reports, web-stats etc.

So where's the catch? It all seems TOO easy. ;)

I have a number of sites to set up, so if anyone experienced with sub-domains can spot a pitfall of doing it this way I would certainly welcome a heads-up!
 
It is that easy. It all depends on whether you need/want to have the full CP access or not. I think part of the intention of 'subdomains' was to setup small, not full production sites 'under' and existing site. But as you discovered you can call a full site anything you want; it doesn't have to be just the DOMAIN, www.DOMAIN.

thanks,
mikeS+
 
Many thx for confirming that Gorgon. :) Having a full set of controls for each sub-domain is better for my particular requirements. I'm glad it works!.
 
Back
Top