I'm trying to understand more the Pro's and Con's for having an Addon Domain vs Separate domain.
Here's my use for it. Site1.com holds all the files, Site2.com holds all the video and images. When it comes time to add a second server (end of this year) I could move Site2.com to a second server and nfs mount it. Thats of the site is separate. PROBLEM: separate site means permission problems, when write code ie.php you can unlink / move files without permission which means setting up special groups.
Addon domain doesn't have the permission problem from what I can see, since the domain gets the group access of the Mainsite. so no extra configuration required. now the problem would be how do I get that addon domain to a second server to offload some of the resources.
What sort of things make you avoid a company? Personally, it's when they either start their introduction with "Unlike other company's..." and/or they won't be open about who they are.
Lets say I have abcd.com as the main domain on cpanel. abcd.com has 10 subdomains.
Basically what I want to do is when I do an addon domain or parked domain I want the subdomains to basically point to abcd.com automatically. Let's say the addon/parked
domain is 1234.com For example I have sub.abcd.com as the main subdomain
so when I type in sub.1234.com I want it pointed to sub.abcd.com internally meaning the script/files from there however in the browser show as if it were sub.1234.com
I have 2 wordpress blogs, and I'd like a few different domains to be shared on each of them.
Using some exemples, suppose I have domains from domainA.com to domainE.com. domainA.com is my main domain and the others are addon domains.
Today Blog1 is using blog.domainA.com, and domainB.com and domainC.com use WebRedirect to blog.domainA.com. And Blog2 uses domainD.com with WebRedirect on domainE.com too.
To access a post like /2008/02/02/this-is-a-nice-post, it is available only at blog.domainA.com, and not by domains B and C. I'd like they 3 to be able to access all posts directly, without redirecting to domain A.
To do that, I suppose I'd need to do some config on cPanel. And also on wordpress, even if I replicate it over other domains it insists to redirect to its configured domain.
I was thinking on the possibility of using symbolic link (ln -s) on their folders to blog.domainA.com folder, but I don't have access to shell on SSH so I'd like to know if it would work before trying.
In a real exemple of what I want, these domains all share the same phpBB forum: forumpcs.com.br, extremepc.com.br, forumdohardware.com.br.
Do u know if symbolic link would work to share the same wordpress? And how to make wordpress stop redirecting to blog.domainA.com?
Been browsing the site and would value your opinions.
Addon domains are supplied by some webhosts and not others, one of the hosts who does not supply any addon domains puts across a good argument that they can overload a server if they get out of control.
How do others apparently manage these with no problems?
When I try to addon a domain, i always got this error message.
Error from park wrapper: Using nameservers with the following IPs: 76.74.137.77,76.74.137.135 Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameser always getting this error when I try to addon a domain to a main account
The domain is correctly pointing to my ip's as well..
I have a main domain "main.com" and when I make a new addon domain "new.com", it creates a new DNS Zone for "new.com" but also adds a subdomain DNS entry to main.com "new.main.com".
I know that is very typical way that cpanel works, and I know there are ways to work around this by using .htaccess.
What I am trying to discover is if removing the "new" subdomain DNS entry under main.com could cause any problems. Are there side effects? Will this break anything within my VPS?
I am not a reseller, but I currently use a reseller account to manage several separate sites of mine. I know that it is possible under a standard cPanel account to have addon domains, where the html files go in a subfolder of the main domain. If you do this:
- is it possible for people to access the addon site files using www.maindomain/addondomain, and if so can you stop this?
- do you still get separate email addresses and spamassassin settings for the addon domain?
- do you get separate web server logs for each domain, for stats?
- is there any other reason why it might still be better to pay more for a reseller account so that each site can be managed completely separately?
I have read about addon domains but I have still one doubt regarding same. Suppose I have buy two domains which have no any relationship with each other like one is of my family (viralshah3112andfamily.com) and one is for my uncle's business site (xyz.com) . Now if I host them in one account as addon domain, both will have different identity? Means both will have different URL like xyz.com and viralshah3112andfamily.com. Is it so?
Unlimited addon domain. Unlimited Mysql databases. No setup fees. About 600Mb webspase About 2000-3000 trafic Cheap as posible If posible (but not necesary) multiple IP's. Payment from PayPal but if it's necesarry then it's Moneybookers ok to. Prefer monthly payments.
Before I went to register with GoDaddy, I looked back at some web hosts I was considering. Some real good ones include free domains. What are advantages to bundling a domain with the hosting package? Is setup usually quicker? What if, at the end of a yearly contract, I decide I want to host my site with a different company? I certainly hope domain names are transferrable around the expiration period.
How can it be determined that multiple domains are "affiliated" with each other? For example, at the link below, on the left side of the page it says that yahoo.com, yahoo.net, and yahooligans.com are owned together. Does this mechanism use WHOIS records, or does it use the IP addresses to which each address resolves (which would only get sites that use named-based virtual hosting to the same IP address, right?)
[url]
If people run multiple sites, say personal and business, and they don't want them to be affiliated, how can they make sure they can’t be linked with each other through such mechanisms?
Lets call the domain1.com and the addons are domain2.com and domain3.com
I transfered the sites from one server to my server and know if I try to goto domain2.com or domain3.com they are not found.
If I goto domain1.com/domain2 (or 3) it works just fine though.
I tried to do the addon domain in cpanel but it is coming up with the following errors.
Bind reloading on server using rndc zone: [domain1.com] The subdomain, domain2.domain1.com has been added.
Error from park wrapper: domain2.com is already configured.
Removed domain2.domain1.com Server at line: 1244. Removed Entry from httpd.conf Bind reloading on server using rndc zone: [domain1.com] The subdomain, domain2.domain1.com has been removed.
domain2.com could not be setup. The subdomain domain2.domain1.com was not setup either.
How can I fix this?
I did try to make domain2 its own account after that, but the script did not work for some reason even though it does if I goto domain1.com/domain2.
I know it must be something simple I am missing, but for the life of me I am drawing a blank.
Also, I moved the site by doing a complete backup in Cpanel and uploaded that to the new server and restored it from the WHM backup screen.
I currently have an established domain, mainsite.com, which is running PHP-Nuke on the directory /home, with a redirect accordingly.
Now, I've created an addon domain, 2ndsite.com, for which I've installed Wordpress at the top-level.
The trouble is, 2ndsite.com defaults to mainsite.com/home - unless I redirect 2ndsite.com to mainsite.com/2ndsite. If I do that, I can then see my WordPress installation.
I'd obviously like to have 2ndsite.com be viewed from that address, as opposed to a subdir under mainsite.com - that is why I got the domain in the first place.