IT_Architect said:
- Admin to reseller I have down I think.
- Reseller requires a fake domain since he may be reseller on more than one server. It would be impossible for him to use a legitimate domain because you wouldn't be able to e-mail him since the server would find the domain locally and never go external to resolve.
Reseller can have a real domain; lots of us have multiple domain names.
You should never host a domain on multiple servers unless you know what you're doing and why, since as you point out there can be unintended consequences. That said, DA allows you to host email on a different server; you can change the MX record using the
MX Records page at the user-level, and uncheck the
Use this server to handle my emails box.
I don't want to raise any more cans of worms in this thread, but personally I prefer allowing a reseller setup without a domain. But I didn't design DA; I just support it
.
- You give IP addresses to resellers from the admin level. You cannot take the address from one reseller/admin and give it to another. You must first delete it from one, and then give it to another.
I think you understand it better than I do
.
- Resellers create users. Resellers can give IP addresses to users, not domains.
That's correct.
- A user creates a domain, and it automatically uses the assigned address on the domain created. Subsequent domains use the same address, so if you want to have a user manage multiple domains, they must either all share that address or there must be different users, or.... you must assign that user another IP address...or can you assign the user the shared and he can also use that?
A user can only use one address, shared or owned. If your user needs multiple IP#s he must be a reseller at this time. Personally I don't mind that limitation because I don't give out IP#s without justification, but the difference could be important to you.
I don't see a place where he can choose which IP for which domain.
Because he can't have more than one.
- And admin cannot perform reseller functions unless he logs in as the reseller. You can do that automatically by listing resellers, then clicking on the reseller, then clicking on modify reseller, then clicking on login as reseller.
Yes. Actually a lot of platforms do it that way including the Cobalt RaQs and Plesk PSA, though they do it transparently. Note that you can only login without passwords one level deeper than where you start. If you start as Admin, then click to login as reseller, then click again to login as user you'll be asked for a pasword. If you don't know the password you can login this way:
User: admin|username
Password <admin-password>
- A reseller cannot modify user information. He must login as the user. This can be done a little differently than the admin to reseller by clicking on list users then click on the user, then click on login as user.
Yes.
- Once in as the user, you click on one of the domains that the user created. You can ensure which one you are on by referencing the menu on the right hand side.
That's actually skin dependent.
If you want to change domains, you click on the home button, and select another one.
That's also skin-dependent. In most skins you click on
Domain Administration or
Domain Setup.
- You do not have rights granted to you at lower levels that were not previously granted from the level above even if you started out admin?
The only
right I can think of that you don't have is the right to go back to being the previous user. To do that you have to logout, and you'll automatically be at the previous user level (probably reseller in your example).
- You can only go down from admin to reseller to user, and never back?
You can go down one level, and up one level. To go down one level, you login as you've already pointed out. To go up one level you logout of the level you're in.
Note that if you go from Admin to reseller, and then to user (using the password trick I've noted above) then a logout will take you back to admin, not to user.
- Use the back button, but don't backup too far or you will get "page not found" or you don't have rights errors. If you get messed up, click the home button.
Yes. See my points above.
- MySQL databases are created at the domain level and you can have as many as the user is allowed. However, each database can only have one database user, so that would mean the user must have dba privileges?
Database users have dba privileges. They have nothing to do with any other users.
- If someone is an admin, and you don't create a reseller, then the admin since he is also a user, can easily traverse and setup his own domains because each login is implicitly a user. However, once you have out-of-house hosters, then you must have at least one reseller so that you can create users under him.
Not if I understand you correctly. Any admin is also a reseller and a site user. Any reseller is also a site user.
- The navigational issues of travelling to lower levels is not encountered by users, only by resellers and admins.
That's correct.
I would appreciate any pointers that you might have to correct or simplify my thinking.
I hope I've made things a bit clearer, and not the opposite
. If I may quote Harry Belafonte out of context (from his "Man Piaba" song):
"It was clear as mud, but it covered the ground, and the confusion made my brain go round."
Jeff
