1
I have been asked to set up several XOOPS 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.
Now my VPS is controlled by Plesk. So 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.
Quote:
DNS for 'holidays.com'
german A 192.169.***.***
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 now have full domain controls - file manager, traffic reports, web-stats etc.
So where's the catch? It all seems a little 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!
A thread is for life. Not just for Christmas.