- Cli Commands
- Paid Plugins are now FREE
- Vesta 2.0: Coming Soon
- API description & examples
- How to install Vesta Control panel
- How to unistall Vesta Control panel
- Template description
- Config and log locations on a RHEL and CentOS
- Config and log locations on a Debian and Ubuntu
- How to install ClamAV and SpamAssassin on a RHEL or CentOS
- How to install ClamAV and SpamAssassin on a Debian or Ubuntu
- How to install WHMCS module
- How to configure FTP backup
- How to translate Vesta interface
- How to enable WSGI support on a RHEL or CentOS
- How to enable WSGI support on a Debian or Ubuntu
- How to enable PHP-FCGI support on a RHEL or CentOS
- How to enable PHP-FCGI support on a Debian or Ubuntu
- How to force https/SSL on a domain
- How to configure temporary links for new domains
- How to set up own Name Servers (vanity/private/child nameservers)
- How to set up master-slave DNS cluster
- How to enable AXFR (Zone Transfer) in Bind
- How to migrate user to the new server
- How to add remote MySQL database server
- How to set up PostgreSQL on a RHEL or CentOS
- How to set up PostgreSQL on a Debian or Ubuntu
- How to replace vsftpd with ProFTPD on a RHEL or CentOS
- How to replace vsftpd with ProFTPD on a Debian or Ubuntu
- How to remove Nginx on a RHEL or CentOS
- How to remove Nginx on a Debian or Ubuntu
- How to properly set up a Mail Server
- How to properly set up a Mail Client
- How to install Fail2Ban on RHEL or CentOS
- How to install Fail2Ban on Debian or Ubuntu
- How to configure Service (SRV) Records
- How to replace MySQL with Percona Server on RHEL or CentOS
- How to replace MySQL with Percona Server Debian or Ubuntu
- How to redirect HTTP to HTTPS using htaccess
- How to redirect subdomain to folder using htaccess
How to configure temporary links for new domains
If you are running hosting company most likely you would want to provide your customers temporary link to access their site before actual domain propagation. This is especially useful when customer is moving site from another host and want to check if everything works as expected.
For instance, you have 2 IP addresses on a server, 192.168.3.57 and 192.168.3.58. Let's say your site is tophost.ltd. Then you need to set up 2 wildcards for each ip address. Go to the DNS menu. Click on a "add record" under the tophost.ltd domain and enter following
Record: *.alpha
Type: A
IP: 192.168.3.57
Press Add button and add second record
Record: *.beta
Type: A
IP: 192.168.3.58
The DNS part is complete. Let's assign those domains to corresponding ip addresses. Go to the IP menu. Select 192.168.3.57. Click on edit button opposite and add alpha.tophost.ltd in the "Assigned Domain" text field. Save and repeat accordingly for the 192.168.3.58 address and beta.tophost.ltd domain.
Now when your user add new domain it will automatically get tophost alias. If he added bbc.com on a 192.168.3.57 then he will be able to see his domain by opening http://bbc-com.alpha.tophost.ltd As you can see dots in original domain has been replaced with dashes.