Dusting up
- Thread starter theone48
- Start date
frankfriend
Member
- Messages
- 410
- Reaction score
- 2
- Points
- 18
If I understand you correctly, then it is straightforward.
The domain is the URL or registered name you want to use, for example www.yoursitename.com.
The site is the set of pages, their design and pictures, the forum pages or whatever you want to put on your site.
You can of course develop your site before you register a domain name, as you would usually do that on your computer at your home or office. When you have it ready and want people to see it, then you need to 'upload' it to your hosting company [x10 hosting is guess], and get a domain name. The domain name is either provided by your hosting company, or you register one with another registrar [but do be sure you pay a reasonable low price, or better still get it free. Some people try to charge large amounts for domain names, and high prices just are not necessary] . Keep it simple as you start off.
How do you plan to develop your 'site'? You can do so with some simple tools, look around on this Community for ideas. Look at the Tutorials section for help
Best wishes
---------- Post added at 08:58 PM ---------- Previous post was at 08:52 PM ----------
Hi,
I've pasted this from the footer - source of help for you perhaps
Don't forget that x10hosting has an irc server as well. Come and join the fun
server: irc.x10hosting.com, main channel: #x10hosting
There's a lot helpful users there if need help building your site
The domain is the URL or registered name you want to use, for example www.yoursitename.com.
The site is the set of pages, their design and pictures, the forum pages or whatever you want to put on your site.
You can of course develop your site before you register a domain name, as you would usually do that on your computer at your home or office. When you have it ready and want people to see it, then you need to 'upload' it to your hosting company [x10 hosting is guess], and get a domain name. The domain name is either provided by your hosting company, or you register one with another registrar [but do be sure you pay a reasonable low price, or better still get it free. Some people try to charge large amounts for domain names, and high prices just are not necessary] . Keep it simple as you start off.
How do you plan to develop your 'site'? You can do so with some simple tools, look around on this Community for ideas. Look at the Tutorials section for help
Best wishes
---------- Post added at 08:58 PM ---------- Previous post was at 08:52 PM ----------
Hi,
I've pasted this from the footer - source of help for you perhaps
Don't forget that x10hosting has an irc server as well. Come and join the fun
server: irc.x10hosting.com, main channel: #x10hosting
There's a lot helpful users there if need help building your site
theone48
New Member
- Messages
- 237
- Reaction score
- 7
- Points
- 0
frankfriend,
I'm new to this and was wondering why I've heard it suggested that you subscribe to the domain before you've made your site. I've several other questions too, if you browse my other posts, you'll see the one where I've got some tough questions about developing. Thanks for your input.
Regards,
TO48
I'm new to this and was wondering why I've heard it suggested that you subscribe to the domain before you've made your site. I've several other questions too, if you browse my other posts, you'll see the one where I've got some tough questions about developing. Thanks for your input.
Regards,
TO48
Last edited:
- Messages
- 3,534
- Reaction score
- 196
- Points
- 63
Before you can have a site you need a domain - when you received you new account from x10hosting it had a domain
in the short of it...
as you make your Web page(s) you use your current domain name to tell the user browser where to get things it needs from the server
when you change the domain name you need to change the coding of your Web page(s) with the new name - which can be a lot of work
Now if you start with the domain the site will use - there is no need to change any coding
that is a very short why of it
you should read and understand this ==> http://x10hosting.com/wiki/How_to_Use_Your_Own_Domain
- Messages
- 3,295
- Reaction score
- 227
- Points
- 63
Yes, you need some sort of "handle" for anyone to access your site (and a domain is easier to use than an IP address for most people), but the issue isn't a technical one. Links within your site (or, at least, within the same subdomain) should never be absolute, so coding shouldn't be a problem.
(That is a bit of an oversimplification. Links in user-generated content are almost always absolute and may need a clean-up after a domain change, but that clean-up is scriptable, and a domain change after a public gold release is a drastic measure.)
The problem is really one of branding. Except for tiny personal sites that nobody really cares about (except you and your grandmother), your site either talks about a product or is a product. Your domain is a part of the branding for that product, and there should be a straightforward, easy-to-see connection between the domain and the product. If your site name, application or product is called "ZippityDoo!", nobody's going to find it if it lives at "www-12.bobsbuggyemporium667.info"; and if they do find it by accident, how are they going to tell anybody about the great new "ZippityDoo!" site without writing it down (and having their computer handy so they can copy your URL from a bookmark)?
Let's go a bit further down that road. What if you wanted to call your site/product "ZippityDoo!", but zippitydoo.com, zippitydoo.net, zippitydoo.in, zippitydoo.info, zippitydoo.org, zippitydoo.tv and zippitydoo.org are all taken? You try something else, and find that dibbitydab.com (and .net, .info, .org, etc.) are all available. "DibbityDab!" is just as good a name for the product as "ZippityDoo!" (it has the same basic gut association with what your product provides), so you register that domain. But your site is complete, and everything in it—all of the graphics, logos, and copy are based on your original name. You have to go back and change everything, or hope that people can figure out that if they want "ZippityDoo!" they have to go looking for "DibbityDab!".
Your domain name, taken as a part of the brand, can affect every aspect of your site. It will determine what sort of users will be attracted to the site as "early adopters" and drive their expectations of content, features and functionality. A hipster name for a bankers' site won't work, nor will the reverse. With a domain name in hand, you can plan around user expectations. It's really difficult to get users interested if there's a lot of dissonance between your site content and the expectations they have going in. Even if it's something they need, they won't stick around long enough to find out.
(That is a bit of an oversimplification. Links in user-generated content are almost always absolute and may need a clean-up after a domain change, but that clean-up is scriptable, and a domain change after a public gold release is a drastic measure.)
The problem is really one of branding. Except for tiny personal sites that nobody really cares about (except you and your grandmother), your site either talks about a product or is a product. Your domain is a part of the branding for that product, and there should be a straightforward, easy-to-see connection between the domain and the product. If your site name, application or product is called "ZippityDoo!", nobody's going to find it if it lives at "www-12.bobsbuggyemporium667.info"; and if they do find it by accident, how are they going to tell anybody about the great new "ZippityDoo!" site without writing it down (and having their computer handy so they can copy your URL from a bookmark)?
Let's go a bit further down that road. What if you wanted to call your site/product "ZippityDoo!", but zippitydoo.com, zippitydoo.net, zippitydoo.in, zippitydoo.info, zippitydoo.org, zippitydoo.tv and zippitydoo.org are all taken? You try something else, and find that dibbitydab.com (and .net, .info, .org, etc.) are all available. "DibbityDab!" is just as good a name for the product as "ZippityDoo!" (it has the same basic gut association with what your product provides), so you register that domain. But your site is complete, and everything in it—all of the graphics, logos, and copy are based on your original name. You have to go back and change everything, or hope that people can figure out that if they want "ZippityDoo!" they have to go looking for "DibbityDab!".
Your domain name, taken as a part of the brand, can affect every aspect of your site. It will determine what sort of users will be attracted to the site as "early adopters" and drive their expectations of content, features and functionality. A hipster name for a bankers' site won't work, nor will the reverse. With a domain name in hand, you can plan around user expectations. It's really difficult to get users interested if there's a lot of dissonance between your site content and the expectations they have going in. Even if it's something they need, they won't stick around long enough to find out.
- Messages
- 3,534
- Reaction score
- 196
- Points
- 63
@essellar did a very nice job of saying who-what-when about domains
I did not do a good job to explain my point (now as I re-read it)
my point is this - if you do not need to change your main domain - don't do it
why ?
when you do a search on 'domain' in x10free-hosting forum - you will get a long list
of post from users that have had issues with changing main domains
so how do I use my new 'bigtime.com' domain ?
park it
A parked domain will show the exact same site as your main domain. The key difference is that the email accounts are separate from your main domain unless you added the email account as a catch-all email and have fewer issues
I did not do a good job to explain my point (now as I re-read it)
my point is this - if you do not need to change your main domain - don't do it
why ?
when you do a search on 'domain' in x10free-hosting forum - you will get a long list
of post from users that have had issues with changing main domains
so how do I use my new 'bigtime.com' domain ?
park it
A parked domain will show the exact same site as your main domain. The key difference is that the email accounts are separate from your main domain unless you added the email account as a catch-all email and have fewer issues
dturton40
New Member
- Messages
- 28
- Reaction score
- 0
- Points
- 0
Personally I probably did it all the wrong way round and learning from my experience I would get the domain name first (that gives you the idea for creating your brand / site), then think about who you want to host it with - you will need to do a domain name transfer if you hosting company is different from your domain name company - this can take some time to completely flush through (I found during the domain name server change, the site was available, then disappeared, then available again, this kept going like that for a couple of days)
In saying that though there is no harm in doing any way round, but it does seem more logical get the name first then the hosting. I imagine the last thing you would want to do is to create a site, get visitors then have to change the name afterwards.
You can create your website at any point really, then upload it when you feel you have enough content.
In saying that though there is no harm in doing any way round, but it does seem more logical get the name first then the hosting. I imagine the last thing you would want to do is to create a site, get visitors then have to change the name afterwards.
You can create your website at any point really, then upload it when you feel you have enough content.
theone48
New Member
- Messages
- 237
- Reaction score
- 7
- Points
- 0
dturton40,
Good thinking! That domain name transfer sounds difficult though, conjures up images of iv's and infusions. I'm wondering, say I get domain name x.com from the provider xyz.com, what is the procedure for that transfer to my site of x.x10.mx?
Good thinking! That domain name transfer sounds difficult though, conjures up images of iv's and infusions. I'm wondering, say I get domain name x.com from the provider xyz.com, what is the procedure for that transfer to my site of x.x10.mx?
- Messages
- 3,295
- Reaction score
- 227
- Points
- 63
That depends on the provider. Some of them will have provisions in their service agreements that make them the holders of the domain; all you get out of the deal is their permission to use the domain for your site, and that's often only while you host the site on their hosting service. (This kind of agreement often masquerades as "free whois protection". If "whois" isn't you, the domain may be registered as belonging to somebody else, and you're stuck without recourse unless the transfer terms are spelled out in the service agreement.)
Some subset of the members of that class will allow you to purchase the domain from them (usually for an additional fee), and either transfer the domain to another registrar or point the domain to your current service/hosting location. Others are a little more vindictive; all you can do is wait for the domain registry to expire, then register with another registrar. That's one of the reasons why it's a good idea to separate your domain provider from your hosting provider -- you may have problems with your hosting provider, your site may reach a point where you have to move on (due to a technology change or scalability requirements, etc.), and you'll want to bring your users from your old deployment to your new deployment as seamlessly and painlessly as possible.
If all you're doing is registering a domain (that is, it's not a part of a hosting package, or you've "liberated" your domain from a hosting package), then the procedures are usually a lot more straightforward. Domain transfers to a different registrar are usually spelled out clearly, should you decide to change domain providers. Pointing your domain to your server may be done using the server's IP address (this is normal if you are maintaining the server locally) on your domain account, or by pointing to your provider's domain name servers and adding your purchased domain to the list of domain identifiers associated with your hosting account (the norm for shared hosting, as here at x10Hosting).
The procedure will be generally similar to this:
1) Register your domain. At this point, anyone going to your new domain will see the registrar's default "yes, this is taken, but it's not a website yet" page. You may be able to create a static landing page with a "coming soon" message at no additional cost, depending on your domain provider. You can leave the domain in this state until you are ready to launch, knowing that you have the domain in hand -- provided that you've paid for the domain. A lot of "free domain" providers have an exploding time limit -- but, then, a lot of free domain providers will get you banned from Google searches and automatically included in spam blacklists and browser malware/phishing blockers as well, so it's best to pay if you can.
2) Add your new domain to your hosting account. It's a good idea to add it as a "parked domain" in this hosting environment.
3) Go back to your domain account, and add the x10Hosting name servers, ns1.x10hosting.com and ns2.x10hosting.com (or the IP addresses of those servers, if that's what your domain provider requires -- you can get the current IP address by pinging the servers). That will hook up your domain account to your hosting account. Don't do this until you're ready to launch -- you don't want people associating your domain with something half-finished and full of error messages.
Allow some time to pass. It can take a little while before the world sees the changes, what with the chain of DNS servers (and the caches they use) that people have to go through to connect your domain name to an actual location on a physical server. I usually tell my clients it'll be at least 48 hours before everything has shaken out. That's usually an overestimate, but it can, on the odd occasion, take longer for some users to see the change. If you are changing providers, leave a month's service overlap if you can, just to make sure that your site is always available, even if you have to disable new input on your old server. If it's a new site, delay your "launch" until you're sure the DNS change has rippled through the system. If you've added your new domain as a "parked domain", your site will still be accessible using foo.x10.mx in the meantime.
Some subset of the members of that class will allow you to purchase the domain from them (usually for an additional fee), and either transfer the domain to another registrar or point the domain to your current service/hosting location. Others are a little more vindictive; all you can do is wait for the domain registry to expire, then register with another registrar. That's one of the reasons why it's a good idea to separate your domain provider from your hosting provider -- you may have problems with your hosting provider, your site may reach a point where you have to move on (due to a technology change or scalability requirements, etc.), and you'll want to bring your users from your old deployment to your new deployment as seamlessly and painlessly as possible.
If all you're doing is registering a domain (that is, it's not a part of a hosting package, or you've "liberated" your domain from a hosting package), then the procedures are usually a lot more straightforward. Domain transfers to a different registrar are usually spelled out clearly, should you decide to change domain providers. Pointing your domain to your server may be done using the server's IP address (this is normal if you are maintaining the server locally) on your domain account, or by pointing to your provider's domain name servers and adding your purchased domain to the list of domain identifiers associated with your hosting account (the norm for shared hosting, as here at x10Hosting).
The procedure will be generally similar to this:
1) Register your domain. At this point, anyone going to your new domain will see the registrar's default "yes, this is taken, but it's not a website yet" page. You may be able to create a static landing page with a "coming soon" message at no additional cost, depending on your domain provider. You can leave the domain in this state until you are ready to launch, knowing that you have the domain in hand -- provided that you've paid for the domain. A lot of "free domain" providers have an exploding time limit -- but, then, a lot of free domain providers will get you banned from Google searches and automatically included in spam blacklists and browser malware/phishing blockers as well, so it's best to pay if you can.
2) Add your new domain to your hosting account. It's a good idea to add it as a "parked domain" in this hosting environment.
3) Go back to your domain account, and add the x10Hosting name servers, ns1.x10hosting.com and ns2.x10hosting.com (or the IP addresses of those servers, if that's what your domain provider requires -- you can get the current IP address by pinging the servers). That will hook up your domain account to your hosting account. Don't do this until you're ready to launch -- you don't want people associating your domain with something half-finished and full of error messages.
Allow some time to pass. It can take a little while before the world sees the changes, what with the chain of DNS servers (and the caches they use) that people have to go through to connect your domain name to an actual location on a physical server. I usually tell my clients it'll be at least 48 hours before everything has shaken out. That's usually an overestimate, but it can, on the odd occasion, take longer for some users to see the change. If you are changing providers, leave a month's service overlap if you can, just to make sure that your site is always available, even if you have to disable new input on your old server. If it's a new site, delay your "launch" until you're sure the DNS change has rippled through the system. If you've added your new domain as a "parked domain", your site will still be accessible using foo.x10.mx in the meantime.