• 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.

Creating test sub-domain prior to site going live with full domain

S

stevenjohn

Guest
Hi there,

I hope someone can give me some advice on a problem I have.

When we setup a site, we would setup:

www.clientsite.com

in plesk. However, more often than not we will want to develop the site using a subdomain on a sandbox url we use:

clientsite.oursandbox.com

Once the client is ready to go live we would make changes to their domain dns so that their usual domain works.

But the problem is I cant see how to setup one of our test subdomains to point to the same webspace, using forwarding wont work as it wants to forward to a url (which currently points to the clients site we are re-developing).

I can see some helpful info in the posting http://forum.swsoft.com/showthread.php?threadid=27533&highlight=named.conf+add+domain
but I cant see quite how to get this working, what changes I should make to named.conf and how to test it?

Any input would be gratefully received.

Regards. Steve
 
Back
Top