New answers tagged

2

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

If must control DNS yourself, set up an A record for the subdomain pointing to the IP address of the godaddy server that is all you need assuming you have set up that subdomain at godaddy. But more to the point, why even bother doing that? Move the content, change the nameservers for www.domain.com (or the IP address if you are using your own child ...


0

You have a few fundamental problems with your last line. RewriteRule ^/?$ "http\:\/\/10\.10\.10\.10\:8080" [R=301,L] Change it to: RewriteRule .* http://10.10.10.10:8080 [R=301,L] Of course, I assume that the IP address 10.10.10.10 in your example is just an example and that you are not trying to redirect to a private IP address that is not routable. ...


0

Based on your comments I am making the assumption that you will be defining a catch all dns record for your domain, eg: *.example.com IN A 1.1.1.1 so that all sub domains of example.com that are not specifically mentioned will be routed to the web server. In this instance this would be handled by your server code. All you would do is detect the domain name, ...


0

Your host is correct that the users would need to accept the security certificate to get the redirect. However, the redirect would prevent Google from indexing the content there. So while there are problems with the redirect, it is still a good idea. The other solution would be to use meta link rel canonical tags to tell Google the preferred URL for each ...


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 ...


0

The issue here will be the ServerAlias directive. Duplicating vhost files from other sites can be an issue as you don't need to have all those directives. The bare bones vhost file you need is... <VirtualHost xx.xxx.xxx:80> ServerName test.example.com DocumentRoot /home/example/public_html/test </VirtualHost> Everything else in the ...


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 ...


0

The first step would be to setup your web server, using Apache as an example you would load your application to the default web root which would mean that all connections to the web server regardless of domain name would be handled by your application. The next step would be to configure your software to get the domain name from Apache (which depends on 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 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

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 ...


0

What you are searching for is known as a CNAME record. With Windows Azure you will be given a public URL for the service usually under a domain associated with Azure. From there you change the current A record to a CNAME record with the same sub domain name and simply add the public domain for the Azure service. What will happen then is when a user tries to ...


0

Google will consider both example.com and newproduct.example.com to be separate properties all together So though both will continue to exist separately and index differently, both will surely affect each other. As new product continue to be a part of main site, it would be better to make it a new directory and promote that: Example make example.com/...



Top 50 recent answers are included