Why is Enkompass to buggy?

[SoftDux]

May I ask why Enkompass is so buggy? Surely if you released a public version, it should have been done properly?

• Google Chrome isn't supported.
• Whenever I visit the DNS Tools it listed some randome domains like google.com, mozilla.com, etc.
• There's no short URL for clients to login, they need to use the port numbers
• I can't install a server-wise SSL certificate
• There's no /webmail shortcut for a webmail interface, client need to goto http://{IP}/webmail
• Whenever I create a domain, it get's an NS record with the full server name, and not the actual nameservers - which is a HUGE problem for us. Domain registrations with Uniforum (our local domain registrar) will fail on every damn domain registration
• The layout is a mess. Many things are done in places I would NEVER expect them to be
• What's the point of "Create Account Wizard" and "Create a New Account" exactly? Why have two features doing the same thing?????

to name but a few things. So it looks like I just wasted my money on something that I thought would be better than Plesk and DotNetPanel. Seems I was wrong. How dissapointing.

[cPanelThrash]

Additional browser support is planned. Everything was tested in Firefox and IE which are the most used browsers.

I've looked at a lot of servers and have not seen the google/mozilla references. Please open a ticket
so we can investigate.

cPanelJenn posted something the other day on replacing SSL for WSO.
http://forums.cpanel.net/f205/ssl-ce...so-193452.html

IP/webmail isn't mandatory. The link in WSO is generated based on what is in the External Name of
each mail server in Server Manager. This could be a FQDN for the server. For MailEnable a forward
can be created for an end user's domain that points back to FQDN/mewebmail but SmarterMail
requires a port number that the validator presently doesn't allow. This is resolved in an upcoming release.

This isn't a bug, this is Active Directory. The full server name is the NS record for Active Directory.
This can be controlled by selecting server and AD name. I've seen several cases where the server
is named NS# and the AD domain is somehost.tld (where somehost.tld is not going to be hosted on
Enkompass) giving ns3.somehost.tld. then NS4.____ could then be setup while NS1 and NS2 are for
another aspect of the hosting. If somehost.tld has to be hosted on the same Enkompass cluster
then the AD domain must be something different. Naming the server NS3 and AD Enk would
then allow NS3.enk.somehost.tld and somehost.tld could be hosted in Enkompass.