Link to home
Start Free TrialLog in
Avatar of Mandy Blyss
Mandy BlyssFlag for Australia

asked on

Domain Forwarding vs DNS Redirection

Hi EEs,

My client has purchased a secondary domain name which is supposed to capture more traffic based on the very name of the domain. I know how to do both Domain Forwarding and changing the DNS to point to the primary hosting servers. However, my quandary is what is best for the search engines and the users to ensure they don't think the site has been hijacked.

So, is it better to enable domain forwarding or point DNS servers to primary hosting servers?

I'd really appreciate some expert insight on the best method forward to capture as much leads as possible for my client.

Regards,
Mandy
ASKER CERTIFIED SOLUTION
Avatar of skullnobrains
skullnobrains

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
1) My client has purchased a secondary domain name which is supposed to capture more traffic based on the very name of the domain. I know how to do both Domain Forwarding and changing the DNS to point to the primary hosting servers. However, my quandary is what is best for the search engines and the users to ensure they don't think the site has been hijacked.

If you do a 302 (never a 301, as this blocks any change ever of the target link), search engines will understand your intent.

This will be treated as a redirect, rather than a domain hijack... whatever that might mean...

It's unclear why you might think search engines might treat this as a hijack.

If you have additional information about why you think this might be treated as a hijack, provide this information for additional answers.

2) So, is it better to enable domain forwarding or point DNS servers to primary hosting servers?

Unsure what you mean by DNS domain forwarding, as there is no such thing.

There is HTTP/HTTPS forwarding, accomplished using 30X Web server redirect requests.

To accomplish a "redirect", you'll use an HTTP/HTTPS 30X redirect.

3) Some Registrars use fake/hokey/broken redirects they call domain redirects.

You should never use these as they are always (at least to date) done via HTTP not HTTPS requests. This means when browsers eventually move to treating all HTTP content as suspect, all these broken HTTP redirect (no SSL cert to upgrade the connection to HTTPS) will all show a malicious site message.

So if 100% traffic is important, the correct way to do this is to wrap the original site in HTTPS (using a cert, like a free LetsEncrypt cert), then forward to some other HTTPS site (likely also using a cert).
Avatar of skullnobrains
skullnobrains

if you need help regarding the SSL setup, feel free to ask inline here. you either need SNI so your web server can issue different certificates based on what the client asked, or multiple external IPs. make it external ips if you do have more than a single IP available as this is both easier to setup and compatible with older clients.
Avatar of Mandy Blyss

ASKER

Great information - thank you.

The client already has a SSL on the primary domain name.
I have a good hosting provider that can assist with multiple SSL.
But I will definitely ask more questions if they cannot assist me.

Thank you :)