|How to have a separate Registrar and Webhost|
I've tried and tried, but they keep wanting to bundle things together...
(I searched WebmasterWorld before posting but couldn't find an exact answer to this point...)
After some bad experiences with a previous website where the hosting company messed up administering my domain name, I decided to try and register a new domain myself and get a separate hosting company to host the actual site.
Unfortunately it seems like every hosting company I look at wants me to transfer the domain into their control, with all the billing and technical administration for it done through them.
Am I correct in thinking that technically all a web hosting company needs to provide is an IP address which I can point the domain name at?
I don't want to rent a server all to myself, the site doesn't need anything like that much bandwidth, but I also don't want to let the hosting company run my domain for me.
What do I do? Where do I look?
Should be quite doable. I do it all the time. I've used DD and GD [names abbreviated, but probably guessable] for my domains, and usually use IPW for my hosting.
My hosting provider has a facility to "transfer" my domain to my hosting, but it isn't really a transfer. They simply assign their servers as SOA for the domain, and give me back a couple of NameServers to enter into my domain registrar's account.
Everybody wants to wring every penny they can from you. There are definite advantages to having an atomic registrar and hosting provider, but I have generally found that I'd rather have a domain registrar specialist for my domains, and a hosting specialist for my hosting. Lots of people use a single provider, and do fine. Nowadays, it's basically a matter of preference. When my hosting provider first started doing domains, they screwed things up pretty badly, but I think they have all that worked out now.
Basically, your hosting provider should provide the nameservers for your domains. They may (or may not) charge for the service, but giving them control of the NS SOA is a good idea, because they can do things like CNAME hosts and add subdomains. They will usually have a mail service, so you want them to have control of your MX records.
"giving them control of the NS SOA is a good idea, because they can do things like CNAME hosts and add subdomains. They will usually have a mail service, so you want them to have control of your MX records."
How does this work in practice? Do I just update the records to be whatever the hosting company suggests, or do I have to give them some kind of access to my registrar account?
You don't need to give them access to your registrar account. The only thing the registrar does is say that your hosting company is SOA (Start Of Authority). This means that they are saying "Ask them about where everything is in the domain." You tell the registrar to do that. The hosting company then has pretty much complete control of the domain from there on.
If you ever stop using the hosting company, you tell the registrar to change their SOA to the next hosting company.
I've never had the same folks as both registrar and host company. Things were already separate when I first arrived at the campsite.
I've never seen anything to suggest any strong benefit to changing things up and putting everything into one tent. So, as things sit today, I've had the same registrar the whole time and I'm now on my 4th, and quite possibly last, host (as I'm quite happy with the folks I use now.)
Never had anyone give me a hassle over it, wouldn't have listened very much, or remained a customer, if they had tried.
Just use a third party dns like ZoneEdit its free for the first 5 domains. Change the DNS at the registrar to ZoneEdit, At ZoneEdit setup your email and enter the ip of the hosting company, tell your hosting company to configure your server with your domain name.
I agree with what everyone else has said. Sometimes it's just a matter of terminology when the webhost is asking you to "transfer" the domain to them. They don't actually mean to physically transfer the registration, but only you point ("transfer") the domain to their servers. Any webhost should be able to do that. In fact, I'd stay well clear of any webhost who asked me to transfer my domain registration to them because either a) they haven't a clue, or b) they want control of my registration for the purpose of having some leverage over me.
Be careful of scams!
It isn't as big a deal now, but domain names used to be the Internet equivalent of gold nuggets, and there have been some elaborate scams to try to get you to part with your domain name.
To this day, the Domain Registry of America still sends those fraudulent "bills" to just about every domain owner in the US. I believe that they are the ones that were banned from operating in Europe. I am constantly explaining to people that no, they SHOULD SHRED THAT BILL, and wait for their real domain registrar to contact them about their domains.
I remember falling for a scam in which a registrar contracted "threshers" find people willing to purchase open domain names. They would contact us as if they owned the domain, and, if we expressed interest, would immediately buy the domain and charge us several times its worth. To add insult to injury, they had to be threatened with legal mayhem to get them to release the "true owner" to you (there are a couple of "ownership" levels of domains, and if you don't have both of them, then you are really "leasing" your domain, and could lose it).
Basically, it just meant I paid about $75 more for my domain than it was worth, and I spent a lot of time exchanging increasingly nasty emails with the registrar until they let go of the Owner of Record to me.
I suspect that there are fewer scams these days, but I could be wrong.