Hot answers tagged

2

When cPanel adds a subdomain, it's a subdomain of the domain listed on the account. So, if account B has a primary domain of sub1.example.com, then it could only add domains like sub2.sub1.example.com. Somehow, you would want to be either making it into its own cPanel account, or adding it to the account with the primary domain example.com. If you tried ...


1

You cannot redirect via DNS. That is not what DNS does. You would have to define www.domain.com on your new server and potentially point the site directory to www1.domain.com to make what you are doing work. BUT STOP! Don't do it! In order for a web server to handle requests, the site must exist on the server. You cannot just point stuff here or there. ...


1

You don't have to create a subdomain in OVH. You onle have to create the "A record" in the 1and1 subdomain, pointing to the VPS IP. That should be enough


1

If you are concerned about the blog getting compromised you can set up another account on another hosting provider. If you host your DNS with your main provider, which I am assuming you do, then you will need to set up an A record using the Advanced Zone Editor.Point the A record to the new account IP address and start blogging. I would suggest hosting the ...


1

All a CNAME record does is handle address resolution. In otherwords if client.bigmultisite.com has an A record of 1.1.1.1 if you then CNAME www.clientsite.com to client.bigmultisite.com the users browser will be given the IP of 1.1.1.1 to go to with the domain name of www.clientsitecom. What you would need to do it either have it running as the only site on ...


1

You can do this without using .htaccess at all. What you need to do is define a wildcard DNS record directing all queries on the subdomains to your application server. The using whatever language you are developing in you would check the host header (fully qualified domain name) to identify the user being requested. Then as part of your application code if ...


1

This is not possible unfortunately. Cookies are attached at the domain level. The way many sites, including the entire stack exchange network, deal with this is by having static content stored on a completely separate domain name, ie: something.stackexchange.com has all the static content stored on cdn.sstatic.net. As you can see it is not simply in a ...



Only top voted, non community-wiki answers of a minimum length are eligible