Portal Home > Knowledgebase > Articles Database > Is this a possible reseller set-up?
Is this a possible reseller set-up?
| Posted by cfraider, 08-26-2005, 08:09 AM |
| I was thinking of getting two reseller accounts from two different hosts (so as not to put all my eggs in one basket) and was thinking if this would work: I have domain.com. I'll buy a reseller account from resellerhost1.com and use the subdomain first.domain.com for that account and second.domain.com for reselleraccount2.com. Next, I'll be alloting ns1.domain.com and ns2.domain.com for as my personalized nameservers in my first.domain.com account; likewise, ns3.domain.com and ns4.domain.com shall be for the second.domain.com account.
Will this set-up be feasible? If so, how?!
I have heard of some resellers here doing exactly what I want to achieve: not putting all the eggs in one basket. How do you do them? Do you get separate domains for every reseller accounts you have in different hosts?
Any feedback and comments would be appreciated.
|
| Posted by Lubby, 08-26-2005, 09:44 AM |
| I imagine there is a way that it is possible. Another option we see quite often is to get the .net version of the same domain, then you don't have to worry about subdomains and such.
Just something we've seen, hope it helps.
|
| Posted by VanHost, 08-26-2005, 10:43 PM |
| The best / most common way to do this, is to buy 1 domain that you will use for all of your nameservers. If you are registering with a cPanel / WHM host, your setup will be very easy.
Basically this is how it will work:
Host 1
Will setup an account with the username "myreseller"
Will setup nameservers: ns1.domain.com; ns2.domain.com
You will register the name server IP's with your domain registrar
Host 2
Will setup an account with the username "myreseller"
Will setup nameservers: ns2.domain.com; ns4.domain.com
You will register the name server IP's with your domain registrar
Any account you setup on Host 1, you will tell the client to use name servers NS1 and NS2. And any account setup on Host 2 will use NS3 and NS4.
It is VERY easy to setup. If any host tells you otherwise, I'd find another host.
|
| Posted by cfraider, 08-27-2005, 01:03 AM |
| So I'll just be choosing which reseller host to use the domain.com. How about the second host, should I just use another domain (as Lubby said, a .net version)? Or is there a way to use perhaps a subdomain of domain.com for the second reseller host?
|
| Posted by VanHost, 08-27-2005, 01:24 AM |
| I assume you are referring to your actual site that you want to host? You can use either reseller account. Simply point the DNS name servers to the appropriate account.
Some people get confused with name server pointing and registering name servers. You can register as many name servers (NS1, NS2, etc.) to a domain as you want. You also don't have to host it anywhere, but can, simply by pointing the name servers to where you want it hosted.
I'm tired, so I may have just talked you into a circle, but the general idea is there
|
| Posted by cfraider, 08-27-2005, 02:30 AM |
| Yeah, thanks VanHost, I got it.
But what I was referring to was the primary domain for each of the reseller accounts. When you register for a reseller account, sign up forms usually ask for a domain name to use (primary domain). I was thinking of a way to fill out that area without using two different domain names (one for each reseller account on different hosts).
It just occured to me: is it not prohibited to leave the primary domain for a reseller account not pointing to the account (eg. I signed up for reseller account on hostx using primary domain domain.com but domain.com [DNS-ically speaking] is not pointing to that account); sort of IP only account (actually, it's really just an IP-only account!).
|
| Posted by VanHost, 08-27-2005, 03:07 AM |
| The best thing to do is simply let your future hosts know what you are doing. In WHM, an account can be created with any domain name. For example, we have clients with reseller accounts and their domain name is "clientname.reseller" and then every account they host is under that domain name. Exactly for the reasons mentioned in this thread.
As for your question about prohibited domain pointing, it is host-specific. Most hosts will not/should not have a problem with it. However, there are a few that believe this is a sign of spam/fraud.
|
| Posted by cfraider, 08-27-2005, 05:06 AM |
| hey, thanks for all the help!
|
| Posted by VanHost, 08-27-2005, 11:20 AM |
| Not a problem, good luck with your new setup.
|
| Posted by sprint, 08-27-2005, 12:14 PM |
| hi vanhost
THANK YOU (all caps - enough? (just kidding))
i havent even started but this is a yummy good tip.!!
bye
sprint
|
| Posted by The Stealthy One, 08-28-2005, 05:54 PM |
| Hi cfraider,
Another idea would be to have two or more completely separate brands. This is the strategy we follow, as we resell for two different hosting companies.
|
| Posted by cfraider, 09-04-2005, 02:49 AM |
| VanHost,
Sorry but I have to resurrect this thread
First-off: I'm not familiar with DNS. I am about to use the set-up you suggested above (ns1/ns2.domain.com for host1 and ns3/ns4.domain.com for host2) and stumbled on a few problems. What I'll be doing is using two different domain names (not domain.com) for the two reseller accounts' main domain. Does that mean that I still need to host domain.com on one of the accounts as I need to set-up the A records for the nameservers?
|
| Posted by swflnetworks, 09-04-2005, 03:32 AM |
| The situation VanHost gave you is an opportunity to do it WITHOUT buying a seperate domain name.
If you're going through with purchasing another domain name to use on the Host2, then don't worry about it and just use:
Host 1:
ns1.yourdomain.com
ns2.yourdomain.com
Host 2:
ns1.your2nddomain.com
ns2.your2nddomain.com
|
| Posted by cfraider, 09-04-2005, 05:42 AM |
| ScreamingEaglePC,
It's actually a last resort for me to have that set-up but as much as possible, I wish to only use domain.com as the nameserver domains for organizational purposes. Nothing technical to the reason, just a personal preference
|
| Posted by dazmanultra, 09-04-2005, 06:35 AM |
| A better idea perhaps would be to run two VDSs from two companies so as you could then have your nameservers physically seperated on difference class C's, and you can also have backup MX.
|
| Posted by VanHost, 09-07-2005, 01:23 AM |
| Hi cfraider,
Sorry for the delayed reply, I was away for the weekend. To answer your question, you do NOT have to host any of your domains that you use for name servers.
For example, assume that the following are your hosting setups:
Host 1
Nameservers: NS1/NS2.DOMAIN.COM
Domain Name Hosted: nonexistant.net
Host 2
Nameservers: NS3/NS4.DOMAIN.COM
Domain Name Hosted: myhost.org
You'll note, that not one of the accounts is hosting DOMAIN.COM but still using its DNS to host the other two domains.
Hope this helps...if not, feel free to ask any questions you need to in order to clarify things.
|
| Posted by cfraider, 09-07-2005, 05:54 AM |
| No prob
But the thing is, if domain.com is not hosted, there won't be DNS info for the domain, especially A records for the nameservers. Or am I missing something?
|
| Posted by VanHost, 09-07-2005, 11:55 AM |
| A domain name does not need to be hosted to have a DNS record on a server. Thus my suggestion to contact your new hosts to let them know what you're doing. They'll be able to add the DNS zones for the new name servers and setup your account appropriately.
|
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
