j_balaji01
01-28-2003, 04:27 PM
Hi friends,
I am planning to get a domain name, let us say colors.com
In order to avoid misspell, I would like to get the domains colours.com, kolor.com etc.
Do I have to buy 3 domain names or will it be charged 1 domain name + 2 addons?
How do the webhosting companies treat these names? Do they consider them as 1 domain name since they all point to a single resource or they treat as multiple domain names?
Thanks,
Balaji
Coach
01-28-2003, 04:36 PM
You'll have to actually purchase all three domain names, but most hosts won't actually charge you for all three. What you are looking for is domain aliasing, so when someone mistypes the domain you have (and you have the misspelled domain registered in your name) it will go to the correct address.
UH-Matt
01-28-2003, 05:14 PM
Addon domains for hosting means you can use more domains with your account. You will still need to pay and get these addon domains registered ready for use.
eddy2099
01-28-2003, 07:15 PM
You might want to check to see if they support Domain Pointing or Domain Aliasing. With that service you could just have all the three domain names pointing to the same site.
Rochen
01-28-2003, 07:34 PM
It depends on the company, however we would regard it as 1 domain and 2 pointers providing they were all going to the same site :)
j_balaji01
01-29-2003, 12:12 AM
Thanks for all your replies. It is really useful to me.
Here's what I did.
1. I registered two domain names at registerfly.com: "color.com" and "colour.com."
2. At registerfly.com, I pointed "color.com" to the webhosts's nameservers for the website color.com.
3. At registerfly.com, I used URL redirection to redirect colour.com to http://www.color.com.
4. At registerfly.com, I used email redirection to forward all email addressed to anything@colour.com to somename@color.com.
Thus, the webhost wasn't even involved with colour.com.
Anyone punching up www.colour.com finds themselves at www.color.com.
Anyone sending email to sam@colour.com has their email wind up with somename@color.com.
I could also have "cloaked" ("framed" (invisibly)) the redirection so that anyone punching up www.colour.com would see www.colour.com when arriving at www.color.com, but I deliberately chose not to do that in this particular case.
m0nkeyhost
01-29-2003, 10:24 PM
pretty good.
That's one advantage so so many registrars allowing people to manage their own DNS. Many times you don't even need to involve the Host for pointers.
j_balaji01
01-30-2003, 05:35 AM
Cove, that was really neat.
Thanks for your time.
Regards,
Balaji
zoobie
01-30-2003, 05:43 AM
But are search engines going to follow all that redirection and framing?
Where's a good tut on invisible framing?
Originally posted by zoobie
But are search engines going to follow all that redirection and framing? In my example, I am simply redirecting users who type colour.com to the place where I want them: color.com. I have no need for search engines to follow colour.com, since color.com is indexed, anyway. I don't know what the search engines will do with colour.com.
Originally posted by zoobie
Where's a good tut on invisible framing? Had I chosen invisible framing at registerfly.com, it would have been accomplished automatically, without any tagging on my part.
Incidentally, there's nothing special about registerfly.com. Many registrars offer similar services. But I mistakenly assumed that they *all* offer similar services, which turned out not to be the case with one registrar that I used. I was unhappy about that. I used zoneedit.com (http://www.zoneedit.com) in conjunction with that registrar to get the redirection I needed.
About a tutorial, I guess it depends on what you want to accomplish with the invisible frames. I'm not familiar with any of them, so I can't give you a personal recommendation. Perhaps another member can help you out in this regard.