I have a basic VPS (full root access), with WHM/cPanel, and am learning the ropes. I'm trying to create a new account for an existing domain (mysite.com), and so far WHM won't let me - it either wants a sub-domain or fake domain, but won't allow two accounts for one domain.
In the beginning, there was only the root account, and it wouldn't let me login to cPanel - a quick chat with tech support, and I am informed that I need to create a second account, which I did. So now I have an account, call it ns1me, for domain mysite.com.
Now I want to create a django account. I go through the same process, but WHM won't allow me to use mysite.com as the domain for django. The docs recommend a sub-domain, so I fill the box in with django.mysite.com. I then realize that has actually created a sub-domain - going to django.mysite.com shows me its home directory, along with helpful information about what version of Apache, Python, and other mods its running (thanks, Apache).
I really don't want a sub-domain, so that's out. Another chat with tech support, and they recommend a fake domain name, as it won't create anything. Sure enough, using a domain of djangomysite.com works, and WHM allows me to create a django account. But of course, I can't send email to django@djangomysite.com (where I could to django@django.mysite.com).
What I want, is to be able to create a second account, associated with mysite.com (so I can run cPanel logged in as django, send email to django@mysite.com, etc) - without creating a whole new sub-domain, or fake domain.
ns1me_database. Whereas I'd like to call itdjango_dbor something. I may just be lacking a basic understanding of cPanel. I thought it was an interface - I don't understand why it's 1:1 with users. – Cyclops Jun 5 '11 at 19:37