Parking A Subdomain On My Domain

[CodeSlinger]

I spent a couple of hours looking through the piles of subdomain questions, but I think mine is actually new.

 

I have another website, me.com. I set up a website on a subdomain for a friend, bob.me.com. Sadly, he's eating me out of disk and bandwidth. What I want to do is set up a website for him at TCH (bob.com), move his current website there and then park the subdomain on it. The goal would be to have bob.me.com and bob.com be interchangeable to ease the transition (he's got a lot of incoming links I don't want to break).

 

My reading of everything said here is that this is possible and in line with acceptable use policies (it should make no difference to TCH whether I point a domain or a subdomain at my TCH hosted domain).

 

So my questions are:

 

1) Am I correct about the acceptable use policy?

 

2) What would I need to do to park the subdomain? Just put in the IP address of the TCH server?

 

P.S. For those confused on why this is different, it is because the website would be hosted at the toplevel domain, not at a subdomain. There would be only one website hosted on a single TCH account, it would just be accessible via both a domain and a subdomain.

[TCH-Rob]

Point a sub to a TLD? Sure, why not do a 301 redirect? If you need it parked you can open a ticket and see if it is possible to park it that way.

[CodeSlinger]

There are three problems with a 301 Redirect

 

1) I don't have that level of control of the webserver. It's another hosting company so I doubt filing a help ticket here would be useful. It's the new site that's hosted at TCH.

 

2) It's not transparent to users (the W3 spec requires a browser to confirm the redirect with the user).

 

3) It's critical for deep links to work and there are too many to put a 301 in for all of them. E.g., http://bob.me.com/Q/T/F needs to go to http://bob.com/Q/T/F.

 

I've checked and the other side will put in a DNS CNAME for me, which should do what I want, i.e. have browsers rewrite http://bob.me.com/~~~ to http://bob.com/~~~ .

 

So, unless something goes horribly wrong, it looks like this will actually work.