Change Alternative URL

@Nuxwin and what do you think about possibility to change vuXXXX.myhost.org to some friendly name like nuxwin.myhost.org ?

@theqkash

This will be done in v2.0.0 or maybe in 1.4.x if we have time

Quote from kess

I dont agree with you, at least not totally.It works correctly if you have 1 single server.

Example:
Server 1 : server1.mydomain.tld
Server 2 : server2.mydomain.tld

At present I have a record in the registrar DNS that tells:
*.server1.mydomain.tld A 1.2.3.4
*.server2.mydomain.tld A 2.3.4.5
So it works without intervention because every vuxxxx.serverX.mydomain.tld are transparently "created" or better, automatically resolved.

But if you remove the subdomain alias from the panel address:
First Problem: If you want to act like the Change Request, you have to setup each vuxxxx.mydomain.tld individually in your registrar DNS (at least for my case)
Second Problem: Who grants that vuxxxx can't be on both systems ?

Do you see what happens ?

Display More

I'd like to reply to the comment of kess, with servers that have multiple IP's, this might bring troubles.

Imagine this:
server1 has 1.2.3.4 and 1.3.2.4
server2 has 2.3.4.5 and 2.3.5.4

Now you use the same DNS records as mentioned:
*.server1.mydomain.tld A 1.2.3.4
*.server2.mydomain.tld A 2.3.4.5

Domains that are configured for 1.3.2.4 and 2.3.5.4 will now no longer load, because apache is configured for requests to a specific IP.

An option to overcome this problem would be to use specific IP-related DNS records, for ex:

*.ip1.server1.mydomain.tld in A 1.2.3.4
*.ip2.server1.mydomain.tld in A 1.2.4.3
*.ip1.server2.mydomain.tld etc etc

Another possible solution is the idea of @theqkash, even though he might not have meant it this way.
It could be testdomain.com.server1.mydomain.tld.
You could allow alias domains and subdomains this way as well.

Anyone else any ideas?

Quote from theemstra

Domains that are configured for 1.3.2.4 and 2.3.5.4 will now no longer load, because apache is configured for requests to a specific IP.

Since i-MSCP 1.3.1, DNS records for alternative URLs are always set with the base server ip in the DNS zone file. That IP is always added to the Apache vhosts. For instance, if the customer IP is not same as the base server vhost, both IPs will be added. This change is related to: https://youtrack.i-mscp.net/issue/IP-1588

Nice, that solves my issue

@timpim
What you can do is to set the panel to srv01.mydomain.net and then have the alternativve URLs reachable via vuXXXX.srv01.mydomain.net
For that just set the panel url to the same value as the server hostname