With the upgrade to WSP 2.1 they broke the Instant Alias functionality and it was a known issue. We are still having the same issue with SolidCP. Is this on the roadmap to fix?
Ok, it appears to be the exact same issue. SolidCP is not creating the A entry in Microsoft DNS for the Instant Alias.
did you have the DNS Record in IIS services with:
[host_name] and value [ip] ?
that should make your instant alias work once you enable it.
Yes its creating everything needed except the main A record, It creates an A record for mail. but not one for (same as parent). This was an issue that first appeared with Microsoft DNS in WSP 2.1, it worked fine in WSP 2.0. As I know SolidCP borrowed much of the code from WSP, it appears this was a bug that carried over.
We did the clean method install, so we know there is no old WSP code causing the issue directly on our server.
WSP 2.1 changed alot with the instant aliases, which is why it works on 2.0 but not 2.1
I did just verify that it creates an record just a wrong one on DNS 2012+ provider which should be relatively easy to fix. (i will add it to the bug tracker)
As far as SolidCP codes go: We actually continued the WebsitePanel project after the project got hijacked by the project leader so most of our base is still WebsitePanel (just with alot of bug fixes, new features and enhancements).
