11 replies to this topic

[b0redtodeath]

I understand one of the benefits of having private nameservers is for reselling. How does a person go about getting/setting up private nameservers? Oh and here's a dumb question, am I right in assuming that having two nameservers has something to do with redundancy?    

[Mitch-old]

Once you sign up for the reseller package I would assume that TIm will give you the two IP addresses for the server, then in your domain control panel you will set up your domain to have its own nameservers. You would add these to your domain host summary section in godaddy or your domain registrar's control panel, and then you could change your nameservers in your nameserver summary OR just add the new ones.

I hope this doesn't sound confusing.
Mitch

[Seth Kinast]

Basically, when you're setting your own custom nameservers, you're just using a "mask" to hide the true identity of our nameservers. For example, my nameservers ns1.idiosyncrasy.org and ns2.idiosyncrasy.org are directly linked to beta's nameservers. Any requests to those custom servers are immediately forwarded onto beta's nameservers.

[b0redtodeath]

Hummm - I think I get the idea. At this moment in time I only have the one domain (my own) pointing to 2 of the ASO nameservers. If I was to resell and wanted to have custom nameservers, would I have to change the nameservers from the ASO ones in my domain CP to the customised ones pointing to the ASO NS IP's?
The CP that I have for managing my NS's only has boxes for 2 nameservers in which to point that domain to - for a reseller's client, would the NS forwarding be done from their own domain CP?

Sorry, I think Ive confused myself now lol    

[Lee-old]

Let me see if I can answer your questions-
You have parent_domain01 which will be the reseller. When you set up NS1.parent.com and NS2.parent.com, you WILL NOT have to change parent.com's nameservers from ns1/2.asmallorange.com to ns1/2.parent.com. You could, but it's not necessary (although it might look better).
After you set up ns1.parent.com and ns2.parent.com, you (or your clients) can register child1.com, child2.com, child3.com, or whatever. The children domains could point to either NS1/2.asmallorange.com or ns1/2.parent.com. Resellers use this to look more professional- If you have a client sign up at TotalRipoffHosting.com and you tell them "Point your domain to NS1.CheaperHosting.com and NS2.CheaperHosting.com"... well, that just looks bad (not to incinuate anything about your hosting, heh).
Whatever happens, ns1/2.parent.com and ns1/2.asmallorange.com will still be pointed at Beta (our nameserver), which will then properly point the site around based on the DNS entries that are made in the reseller account.
Hope that helps.

[Seth Kinast]

Lee is correct. Really all you're setting up is that mask... I point www.idiosyncrasy.org at ns1.idiosyncrasy.org and ns2.

[ben_b]

Wow... I totally get name servers now!  

[Lee-old]

If you're interested in really learning about the backworkings of it all, and how these things work, google for "Men and Mice DNS FAQ"... that should bring you to an FAQ page which taught me everything I know

[b0redtodeath]

Brilliant responses! and thanks for the Google tip too


Edit: DNS Glossary <<< I think this looks like the one.

[Lee-old]

Exactly.
It's not too informative for a beginner, but if you just follow around links a bit, and learn what everything does, it'll broaden your understanding of terminology.

[ben_b]

So could just anyone set up ns1.theirdomain.com and ns2.theirdomain.com and point them at ns1.asmallorange.com and ns2.asmallorange.com, then use ns1.theirdomain.com and ns2.theirdomain.com as there name servers?

[Lee-old]

Well, yeah, anyone on ASmallOrange could do that. I do.
Only Reseller accounts have access to editing DNS entries, I believe, though, so anyone else would have to ask Tim.
And if you're not a reseller, it doesn't particularly matter.

It would only work for ASO customers, because our nameservers have to recognize your domain to know what to do with it. Whenever you add a domain to your account (via add-on domains, or parking, or what have you), it creates instructions for Beta's nameservers to "Direct all requests for domain X.com to folder /home/XsUserName/www", or whatever. If joeschmoe put in ASO for his nameservers, and we didn't host him, Beta wouldn't point the domain to his site. The same goes for personal nameservers that redirect to Beta.