These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Sub-server like a Top-level server on the new forum.
Web Hosting and Cloud Computing Control Panels
I believe what you want is basically a completely separate site, but the NAME is a sub site of the main site, like "friend.mysite.com" so he can treat it as if it was a new site, with it's own public_html, etc.
That is easy. Just create it as a new site, but use "friend.mysite.com" as the name.
It will use one license count from your license, if you are using the pro version, because it is actually an independent site within Virtualmin.
It has everything, new password, new user (if you set a new user), email, etc.
<b>Joe wrote:</b>
<div class='quote'>I'm not sure what you mean by "proper working to the basic file test.com"?</div>
Ok. If we create a Top-level domain eg. joe.test.com, Virtualmin create a new zone file for this domain. If my thinking is good, the browser after receiving such a query from a user, ask my server, dns, and my server will check the file zone - test.com, not joe.test.com. In the absence of relevant entries, respond that there is no such address. If my thinking is good. If my thinking is wrong, that every user who has access to area file, can create a subdomain on my domain test.com. In my opinion the area file should be in some way (eg by instruction "include") attached to the main zone test.com.
Thanks
RafaÅ
<b>Joe wrote:</b>
<div class='quote'>I'm not sure what you mean by "proper working to the basic file test.com"?</div>
Ok. If we create a Top-level domain eg. joe.test.com, Virtualmin create a new zone file for this domain. If my thinking is good, the browser after receiving such a query from a user, ask my server, dns, and my server will check the file zone - test.com, not joe.test.com. In the absence of relevant entries, respond that there is no such address. If my thinking is good. If my thinking is wrong, that every user who has access to area file, can create a subdomain on my domain test.com. In my opinion the area file should be in some way (eg by instruction "include") attached to the main zone test.com.
Thanks
RafaÅ
Joe,
In setting up a "sub-server" which is really a "sub-domain" of an existing domain, I'd like to have the zone files combined.
Ex.
mydomain.com => mydomain.com.hosts
subdomain.mydomain.com => mydomain.com.hosts
It seems this behavior is configurable ONLY when setting up a "sub-domain" type record.
However, I like the separation used when setting up "sub-servers" (new sub-server is added to "~username/domains/subdomain.mydomain.com" directory) as opposed to the way "sub-domains" work (new sub-domain is added to "~username/public_html/subdomain")
Any help in this area would be appreciated. (a workaround, or a solution respectively)
--
Best Regards,
Peter
Best Regards,Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
*** Just to Clarify: I do realize that sub-servers can be totally different domains. In this case, a new zone file would be appropriate. My question is focusing on those domains which are sub-domains of an existing domain. Thanks ***
Best Regards,Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
<div class='quote'>If I create a subdomain, I can't give them home directory (which would have access to it,and only for it), its own database etc</div>
I assume (hope) you mean sub-server (sub-domain account types are deprecated, and were never a good idea...we added them to make a few cPanel users more comfortable, but it confused everybody else). But, yes, that's the way sub-servers work. A sub-server is designed to allow one user to have many sites--no matter what they're named.
<div class='quote'>if I create top-level domain, dns entries migrates to another file (eg friend.test.com) but should, for the proper working to the basic file test.com.</div>
I'm not sure what you mean by "proper working to the basic file test.com"?
If delegation isn't being setup properly when you create new subdomain named virtual servers, that'd be a bug (I use this all the time, though, so I really doubt there are any issues with this, assuming you've got your glue records at your registrar configured correctly). But, as with pretty much everything in Virtualmin, this behavior is configurable.
If you really don't want a new zone for each virtual server, just configure Virtualmin to put them all in the parent zone. Edit the Server Template(s) you use, and in the "BIND DNS Domain" section, set "Add sub-domain DNS records to parent domain?" to Yes.
--
Check out the forum guidelines!
You're thinking is all wrong. DNS doesn't work the way you think it does. ;-)
--
Check out the forum guidelines!