Is it right that I can buy hosting from X and then add the domain from a cheap domain-seller? (Without any 30X redirects, framesets, etc!)
Is that what most of you do? I'd like to understand the way people here on the forum do it and what the experiences are- running a midsized website.
Any further recommendations welcome!
[edited by: Webwork at 1:59 pm (utc) on Mar. 20, 2007]
[edit reason] Charter [webmasterworld.com] [/edit]
I pay a little more than that for my hosting, but basically, yes.
FInd a registrar you like and pay them $10ish per year for the domain hosting.
Then find someone else who hosts websites and pay them $XX for hosting.
You can take it a step further and find yet another third party to handle your DNS, if you really want to take it to an extreme (and I really need to organise that for my domains)
It removes your reliance on one party while complicating your billing, but only slightly :) You're on the right track here.
Should I buy the domain or the hosting first?
BTW: What is the sense in using someone else for DNS?
<snip>
Thanks!
<Per the Charter it is very rare that we allow threads to delve into service provider recommendations.>
[edited by: Webwork at 5:14 pm (utc) on Mar. 20, 2007]
[edit reason] Charter [webmasterworld.com] [/edit]
While you are working on that, be thinking about domain names. If you have a good idea, check and if it is available - grab it immediately! Right that second, no delay. Don't even stop to muse if its any good - you should have done that before checking. If you check availability, you buy it.
Why? Theres nothing worse than thinking up a good one and finding it gone on the second check.
Similarly, at the same time, be researching hosts, to find one you like (PM me for an affiliate link ;) (Kidding, webwork! Kidding!)) - but don't pay until you are ready to go live, because they normally start the account immediately and you are not yet ready to go.
Once you have your first draft of your website (and remember, you can take forever to make it perfect - you have to publish something!) then buy your hosting, point the domain name, install the markup & code, test all the pages work (no, really - test them, and preferably from a different machine. The number of sites I see with c: references...) and wait for the dns to propagate.
... and you have a website! :)
(Now for the hard work of improving it...)
(still: what's the point in using a DNS service as third building block?)
what's the point in using a DNS service as third building block?
Potentially: quicker access to your site by users, and greater reliability. Definately: some protection and options in the case of the failure of your registrar and/or failure or dispute with your web host.
Back to original topic:
I am currently in the process of registering domains and found out they offer "url forwarding" for an extra fee? Why would I need this?
Actually I want/expected a clean domain/webspace package without any 30x redirects etc. As I understand this, this works by providing DNS/ IP-address to the registrar....
Can I enter this information once the registration is complete (which I stopped there), and is this company I am registering with just offering "url forwarding" as an add-on
OR is "url-forwarding" the normal procedure when I register a domain for a live website and not just want to "park" it? (meaning the domain is effectively about $10 plus $6 if I want to point it anywhere?)
I think you had it right with your other comment - you will provide IPs to your registrar once you have gotten the details from your host :)
