Do addon domains simply serve as redirects?

[Scouzer]

I'm thinking about making another website with my existing hosting package (unlimited addon domains).

However...does say www.thisismynewsite.com simply redirect to www.thedailycute.com/thisismynewsite or does it still show up as the former in the browser? In other words, it'd be no different than a regular domain name.

Thanks.

 

[wetcat007]

I would think that they'd let you set the domain up however you would like. I would ask the hosting company though.

 

[AgaBoogaBoo]

Addon Domains: Hosting another site, within 1 shared hosting account. The new account will not receive access to a control panel just for that site. Data for the site will be stored in a directory specified by the user, but still within their directory.

Example: You own business.com and purchased a shared hosting account for it. You now have business2.com and want to host it. You go to business.com's control panel, make this an addon domain, and create a folder business2 at the root of your account's directory. (/home/business/business2; /home/business is the highest you can go; to put things in perspective, /home/business/public_html would be the files for your current site that are viewable by the internet)

Business2.com now has its own website seperate from business.com's content.

Parked Domains: You have business.com, and now purchase business.net, and want it to just display the content from business.com. You go to your control panel, click on parked domains, follow the form and submit business.net to the form. Now, when a user goes to business.net, they will see the same content as business.com.

In both cases, it goes without saying that you have to change the nameservers for the respective domain. Hopefully this was clear, but if it wasn't, let me know, and I'll clarify whatever doesn't make sense.

 

[Scouzer]

I need two bits of clarification:

First: I'm pretty sure this is correct...I place the new folder in ROOT, not in the existing public html? Then, would I have to make root/business2/public_html ?
Second: Even though it's an addon domain, it'd be an entirely separate site? What I'm trying to ask here is there'd be no easy way for a visitor to know that the sites are correlated. I do use private WHOIS. It's important they do not know they are related as their content...is quite different.

 

[Goosemaster]

Originally posted by: Scouzer
I need two bits of clarification:

First: I'm pretty sure this is correct...I place the new folder in ROOT, not in the existing public html? Then, would I have to make root/business2/public_html ?
Second: Even though it's an addon domain, it'd be an entirely separate site? What I'm trying to ask here is there'd be no easy way for a visitor to know that the sites are correlated. I do use private WHOIS. It's important they do not know they are related as their content...is quite different.

yeah...in the root.


If it is shared hosting it is on the same IP, and there is many a site out there that can search a shared host for other accounts....

VPS + multiple IPs is your best bet (what I do). Sure they both have simialr IPs, but those sites won't show anything, and each client would have to know what to look for to find the other

 

[Scouzer]

If IP is the only way to tell, that's ok. It doesn't need to be secret, but I'd definitely like it to be not obvious.

Thanks