We are usign both of SolidCP and mspcontrol

SolidCP has issue with Instant Alias

Instant Alias with mspcontrol worked fine

both of control panels based on WebsitePanel

hope this issue fixed. It is not a big issue

I am getting this bug also.

Work-around: Set up wildcard DNS record for *.server-name.your-domain.com and use that for the Instant Alias. (I always thought this was the reason for having a separate Instant Alias specification for each server, by design.)

I will say that on my server settings page, the form isn't displaying correctly to enter the instant alias.

By the way, I have seen unexpected behavior in "hostnames" that may involve the same code as the instant alias issue above. For example, with hostnames enabled, if I set up a website as hostname.domain.com, the system wants to add DNS for www.domain.com instead. So hostname.domain.com won't resolve properly unless there is a wildcard record.

(Another unexpected behavior, off-topic for this thread but on-topic for hostnames: When setting up a new domain + website, I think the system ignores the extra "hostname" that can be specified for the website. I don't know if that field serves any purpose, and it's not clear to me or customers how it's supposed to work, so it would be okay with me if it's simply removed from the context of setting up a new domain.)

Hello,

Thanks for sharing the instant alias work around.

I did fix the design of the instant alias field a few commits back (and will be part of the new stable release that will be out shortly).

It's odd how instant alias and hostnames behaves this weird, and is within our bug tracker (just hard to find the time to fix all issues, but we will get there 🙂 )

The hostname field i personally prefer to leave it disabled for my own environments, as you indicated it's confusing for customers (i totally agree). To leave it disabled you can simply uncheck it from the hosting plan and it won't show up.

Regards,

Marco