sitecreations
asked on
301 Redirects on Parallels Plesk Control Panels?
I am using Parallels Plesk Control Panel 8.6. This system allows you to set up domain aliases or new domain with hosting, http forwarding, or frame forwarding. None of these are 301 redirects, so all have SEO problems.
domain.com (website)
WANTED:
domain.net -> domain.com (301, with no physical hosting)
domain.org -> domain.com (301, with no physical hosting)
I can set up a new domain, with physical hosting and install .htaccess in that hosting folder that will do proper 301 redirects, but this seems like huge overhead to just forward a domain.
I have full control over the server including DNS for all domains if CNAME or A Records are a possibility.
So, is there an alternative on Parallels Plesk Control Panel 8.6 that I can use to forward my domains using a 301 redirect WITHOUT creating a new hosting account for each domain?
domain.com (website)
WANTED:
domain.net -> domain.com (301, with no physical hosting)
domain.org -> domain.com (301, with no physical hosting)
I can set up a new domain, with physical hosting and install .htaccess in that hosting folder that will do proper 301 redirects, but this seems like huge overhead to just forward a domain.
I have full control over the server including DNS for all domains if CNAME or A Records are a possibility.
So, is there an alternative on Parallels Plesk Control Panel 8.6 that I can use to forward my domains using a 301 redirect WITHOUT creating a new hosting account for each domain?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Adam_Eterno, I use cPanel and not Plesk, so I can't be sure but adding the domains via Plesk will effectively host them, which the OP is trying to avoid. It isn't a hardship, but I think he wants the elegance of not needing to host just a .htaccess file.
You would buy the spare domains and point the A record to the IP address of the canonical domain. You don't touch Plesk (again I don't have it, but am trying to imagine it like cPanel). If you bought the domain at GoDaddy, then you can set the A record there. Or if you have a dedicated server at a host like like Planet, you get an interface that lets you add a domain and change its A record.
You would buy the spare domains and point the A record to the IP address of the canonical domain. You don't touch Plesk (again I don't have it, but am trying to imagine it like cPanel). If you bought the domain at GoDaddy, then you can set the A record there. Or if you have a dedicated server at a host like like Planet, you get an interface that lets you add a domain and change its A record.
Thanks for the response crm911. I understand the A record changes for my child domains but once the A records are changed would I update the httpd.conf on the parent server as you outline?
(My server uses a shared IP for 20 domains of which the parent domain is just one so I would need tell plesk about these child domains in some way.)
Thanks again.
(My server uses a shared IP for 20 domains of which the parent domain is just one so I would need tell plesk about these child domains in some way.)
Thanks again.
ASKER
it is difficult to justify new IP addresses for this purpose with our host. Plesk should provide a method for dealing with 301s.
Are the .net and .org domains added to plesk as normal but without physical hosting? Or do I add them with physical hosting and then create the .htaccess files for each? (It was my understanding that sitecreations wanted to avoid this).
I think you are proposing that once the A record of the "child" domains point to the .com IP address it is enough to update the httpd.conf as outlined. Am I right?
I'd appreciate any detail you could provide for the solution you are proposing crm911 or even if sitecreations could verify if this worked.
Many thanks.